Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On contributions, changing the workup type can leave some orphaned data fields #110

Open
bdeadman opened this issue May 8, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bdeadman
Copy link
Collaborator

bdeadman commented May 8, 2024

When the workup type is changed, the available sub-fields can also change. If there is data in a field which is not in the new workup type, the field is hidden from view, but the auto-validation warning shows that the field is still in the record. Warning message can help find the orphaned data field, but the messaging may not be clear enough for general users.

Need to check if the orphaned data fields are included in the .pbtxt file.

Possible solutions:

  • Erase orphaned data fields when the type is changed
  • Present a local warning when type is changed, and there is orphaned data fields
  • Show all edited data fields, even if they are not a valid sub-field for the type. Could include visible warning messages at the data field.
@bdeadman bdeadman added the enhancement New feature or request label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant