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
Implemented as a bit-wise (1 or 0) field where 1 means export and 0 means don't export.
Displays as a toggle in the plants form along with a hint which checks for a situation where TSN = TSN_Accepted and Export = 0 which suggests that the species might need to be exported as it is either a single species or species which is a default synonym (i.e. the synonym we want other species to point to).
Here's how this currently looks:
EXPORT
DO NOT EXPORT
Values are populated based on what is in tlu_PLANTS.
@johnpauls, @abrolis, @lizmatthews03 -
Does this meet the need to provide access to changing which species are exported in end of year exports and should Accepted Found be hidden or made read-only?
This looks great, I like the interface. If I understand how this works, Accepted Found will be determined based on what other data is in tlu_Plants - so it would make sense that it should be read only. For the plants form (not necessarily the underlying tlu_Plants) could there maybe be a different label for Accepted Found - I think it might be confusing to users who aren't familiar with the fields in the table. Maybe Other Accepted Name Found or something like that, so it is reminiscent of the table, but a little clearer as to what it means.
tlu_PLANTS lacks a clear field for identifying which species should be exported in annual data closeout exports.
Add an Export field and expose it in the plants form so that the field can be edited from the database.
The text was updated successfully, but these errors were encountered: