Should warn user when deleing a datamodel that is used for receipt

[standeren]

Description

A receipt layoutset must have a related datamodel which is required when creating the receipt. But when deleting the datamodel you get no warning and no visual clue that anything is wrong on the receipt.

Need discussion with UX how to inform the user of this.

• Disable deletion of this datamodel?
• Add warning before delete that this will also delete the receipt?
• Add validation in the custom receipt if this state occurs?

Additional Information

No response

Tasks

No response

Acceptance Criterias

No response

[nkylstad]

I guess this could apply to any data model that is used in a layout-set. F.ex:

• If the data type is used in a layoutset (regular form, subform, receipt), the delete button is disabled, and info message/tooltip explains that you must remove the connection before deleting the data model?

We should ensure that this does not mess up the flow for those who tend to delete their old data model before uploading a new one. My thoughts on that is that it should be possible to just upload a new data model with the same name without deleting, so it's probably not a problem.