Power Platform Governance and Administration

Running a organization with D365 CE + Portals and Marketing. The webResourceBase and ribbonClientMetatdataBase consume more than 3 gb of data, and this is something we can't control! The CRM solution is pretty vanilla without custom ribbon and only 1 custom javascript. Tables like this should not count in our complete storage.

When deploying new solutions and creating custom roles for users it is a pain to test functionality and roles. Please add a mode for Admins to immitate as users.

We find that the search capabilities between Microsoft's different solutions are not quite the same. 

For instance, Finance & Operations has more options for more targeted searches than Customer Engagement currently has. 

When you have a list page open in F&O, you can easily search on the different column headers in F&O, making it easier to search for a specific record. Meaning that on header 1 you can do an exact search, where on header 2 you can use wildcards,...

In CE, you have the advanced search where you have to specify a correct search string in order to find the results. 

For users who have to switch between the 2 applications, this is can be quite confusing. 

In addition, in F&O you have more search options on header level such as 'is one of'. 

This allows you as a user to easily see different search results in one view. 

E.g. the customer has to be of type X and Y

In short, it would contribute to the realisation of a one ecosystem if CE's search options were aligned with those of F&O.

Current Behaviour: Once the Azure Synapse Link for Dataverse is setup, all the tables with parent child relationships are synced with the correct value of Parent Name column in Child Table. However, when the parent record primary name field is updated in Dataverse, there is no trigger in Dataverse for child table, hence the parent table gets updated in Azure Data Lake and child table doesn't get cascaded with the parent's primary name field value. Any new child record created in Dataverse then has the new parent's primary name value. This leads to a discrepancy in the parent's primary name value in the parent table with respect to an old value in Child table.

ISSUE: Now it you have a reporting based on parent's name value from child table without knowing that the value won't be update, it leads to all the reports not functioning properly.

ASK: Please help with finding a way to have this data sync appropriately based on the changes in parent name. Alternatively, please help develop a tool which should update all the child tables with the latest parent's primary field name value