Sometimes it is necessary to develop a certain logic that involves parent and child elements.
For example, we want to compose the manufacturing route in the header (RoutingHeader) based on the work centers or machines in the lines (RoutingLines).
Therefore, every time you add a new operation, change it or delete it, you must update this field.
If we delete the header directly, it will trigger the deletion of the lines that causes the maintenance of the header to give an error because the element is marked for deletion. Is there any property in the header that tells us that it is being deleted so that this logic is not fired? We would need to be able to distinguish between the deletion of the header and the deletion of the lines.
Trying to find analogous elements in the system we could think that orders with their lines would have the same problem but this problem does not occur since the fields of the header that are related to the lines are FlowFields.
In our scenario we want to concatenate data so the FlowFlied field is not useful.
Any idea? Do you consider necessary to know if the element is being deleted?