Paola Recarey

You have OOB and customs tables that connect with each other and some of that are used for different model-driven apps. When you want to create isolated solutions for each model-driven app, the current mechanism is will prevent you and want to include dependent components.

There should be a way that allows users to import and export model-drive apps inside solution without having to include all assets of the table that the app uses, instead allowing to include only the needed components.

A possibility could be adding warning sign that informs the user of this missing dependencies but not prevent the user of performing the import or export of the solution.

Actually, to bypass this situation users, have to edit the solution.xml and deleted the missing dependency which it is not convenient.

When importing a solution into a production environment provokes the deleted of components, a window should display with information on what components will be added, removed or updated to inform the user that the action that is going to take place will cause the deletions of components, if any. It should list which components are going to be deleted and ask the user to check Confirm or Cancel, and then confirm that selection.

It would be helpful if error messages were more descriptive helping the customer understand what is causing it and making it easier on how to address them properly. Especially, when these errors are part of a changed rolled out after an update.

According to the customer:

"I would hope that this information gets passed on to the appropriate people at Microsoft so that error messages are more strongly pointed to the issue as opposed to a bunch of JSON that most no-code/low-code users wouldn’t have any idea how to decipher. For instance, “Child flows must be turned on before the parent flow can be saved.”