Closed bradfordcondon closed 5 years ago
This is an old bug that was fixed. We used the Fields Generator to create our fields and it sets the chado column
to organism_id
by default. If you forget to change it you get this bug because the ChadoField is trying to look up the organism even though there isn't one in that field. It has been fixed here which shows it's no longer set to organism_id
.
To fix it in your instance:
We used the Fields Generator to create our fields and it sets the chado column to organism_id by default.
That was definitely what i expected as I've done the same thing myself. Updating did resolve. Sorry for posting a stale issue, thank you!
No worries, I'm glad it works now!
I was unable to edit entities due to a field looking for an
organism_id
column in project. Removing thehp__phenotypic_variability
field resolves the issue.Does the field require an organism_id column on project? If so it should please add it to the schema if not present.
edit- i dont actually see where this might be occurring in the field...