The issue is that the composite data entity schema is not updated properly after a code update.

The use case is as below :

-We have DMF projects 1, 2 and 3 which are using Composite data entity A. A is using child data entities AHeader and ALine.

- We are adding a new custom field X in data entity ALine

- We are deploying the code and doing a data entity refresh

- To be able to see the new field X in A, we need to do the following :

1. Remove A from projects 1, 2 and 3

2. Do a data entity refresh

3. Re-add A to projects 1, 2 and 3

4. Do the mapping update of the new field X

- Following all the above steps are quite time-consuming and potentially dangerous during execution as there is always a risk that the middleware might trigger projects 1, 2, or 3 while we are in the midst of these steps. If this happens, the interface will inevitably fail, causing disruptions and possibly significant issues.

The request is to consider alternative approaches that would mitigate these risks and streamline the process.