You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently on the frontend representation of the datamodel, a specific field's isRequired attribute is not accounting for whether it is marked as required or not via it's associated SplocaleContainerItem (i.e., in SchemaConfig).
Only the Specify 7 field overwrites and the base field definition in the specify_datamodel.xml is being considered:
melton-jason
changed the title
Schmaconfig isRequired not being respected to field.isRequired
Schemaconfig isRequired not being respected to field.isRequired
Apr 2, 2024
For searching/future testing purposes this includes workbench not making you to add required fields to the data set. For example on lsumammals9823 the cataloger field is required for collection object data entry but workbench lets you upload a data set without cataloger being mapped.
Describe the bug
Currently on the frontend representation of the datamodel, a specific field's
isRequired
attribute is not accounting for whether it is marked as required or not via it's associated SplocaleContainerItem (i.e., in SchemaConfig).Only the Specify 7 field overwrites and the base field definition in the
specify_datamodel.xml
is being considered:specify7/specifyweb/frontend/js_src/lib/components/DataModel/specifyField.ts
Lines 134 to 139 in 968fc20
See #4703 (comment)
The text was updated successfully, but these errors were encountered: