Setup Wizard: Delete Entity Field

[sleidig]

As an admin user I want to delete fields from an Entity Type via the Admin UI so that I can keep the data structures simple and clean over longer time.

Currently the AdminEntityDetails components allow to add new fields to an Entity Type but do not let the user delete a field. They can only hide fields by dragging them to the side bar or pressing the "x" icon.

• [ ] Users should be able to delete a field completely:
  • add a button to the "Configure Field" dialog window that allows to "Delete" the field fully
  • As this may lead to data loss for existing records, appropriate warnings have to be shown.
• [ ] Ensure config is still valid after deletion:
  • scan all config parts that could reference this field (EntityList, RelatedEntities, EntityDetails, ...)
  • remove the delete field key there if it is still used
  • make sure to only delete the config relating to this entity type (there may be the same field key on a different entity type also, e.g. "name" of child and "name" of school)
• [ ] Remove any existing data of the deleted field
  • We need to scan existing data records and re-save them, removing the data of the deleted field, to ensure data security. Otherwise, when later adding a new field with the same ID again, old data may suddenly reappear.
  • :exclamation: to discuss: the current user might not have access to every record of the entity type due to permissions. Do we need to handle this on the server or locally double check on each client when it receives the config change via sync?

[sleidig]

@tomwwinter , what are your thoughts regarding the data cleansing aspect here (i.e. updating existing entities and removing the values of the deleted field)?

the current user might not have access to every record of the entity type due to permissions. Also, in certain systems this could cause document conflicts because a lot of entities are changed.

Do we need to handle this on the server (which would require a completely new architecture ...) or locally double check on each client when it receives the config change via sync? or ...?