Microsoft Dynamics 365 and Power Platform Library

Scenario: There are times when you want to delete an entity from target entity list and when you do so, you face an error message which does not tell you where exactly the entity has been used.  "Entity cannot be deleted while dependent Entities for the processing group exist. Delete dependent Entities for a processing group and try again. " Solution: Browse the environment by appending this part  /?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF   at the end.  For example; if the environment URL is  https://daxture.sandbox.operations.dynamics.com then the complete URL will be https://daxture.sandbox.operations.dynamics.com/?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF Filter for Entity and it will give you the DefinitionGroup where the entity has been added or used in data management import/export projects. Get the DefinitionGroup name and search in the export/import projects under data management and either delete the whole

Scenario:   Project groups are shared across all legal entities in  D365 finance & operations app so have setup under one of the cross-company data sharing policies. You are also required to setup dual-write table map for project groups to sync from FO to CDS. However, you get following error message when you try to Run the table map "Copying pre-existing data completed with errors. For additional details, go to initial sync details tab." Follow these steps to overcome this issue as a workaround.  Steps to follow: Disable cross-company data sharing policy where ProjGroup table has been used Choose Yes at next pop up window Go to Data management > Dual write > select Project Groups table map and Run Enable cross-company data sharing policy for project groups Choose No at the next pop up window unless you want to copy data across all companies

Scenario:   The D365 finance & operations app is linked to Common Data Services through dual-write in development or sandbox environments. You are required to refresh databases in D365 FO and CDS both from another production environment (dual-write integrated (linked) environments in the scenario) Steps to follow: Before initial refresh, log on to target environment Go to Data management > Dual write and stop all jobs Refresh FO and CDS environments from the same integrated source environments Go to Data management > Dual write and Unlink environments Clean data from following tables in D365FO if data exists DualWriteProjectConfiguration - A sample URL would be like this to access tables from D365FO environment <Environemnt URL>/?mi=SysTableBrowser&prt=initial&limitednav=true&TableName=DualWriteProjectConfiguration&cmp=<CompanyId> DualWriteProjectFieldConfiguration- A sample URL would be like this to access tables from D365FO environment <Enviro