Skip to main content

Posts

D365FO: Entity cannot be deleted while dependent Entities for a processing group exist. Delete dependent Entities for a processing group and try again.

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 del...

How to run dual-write table map when underline entity table is setup under cross-company data sharing policy

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

Steps to follow when refresh dual-write integrated environments (FO and CE)

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 <En...

Dual-write connection set error: An item with the same key has already been added

If you happen to see this error message then you have duplicate records in cdm_company entity in CDS environment. Check for cdm_companycode field this is normally not allowed but have a look and delete the ones with duplicates.

Dual-write integration for Cross-Company data in D365 Finance and SCM

Dual-write does not work with  the cross company data sharing policies in  D365 FinOps  (there are so many names but I am using this name for reference 😊). Brief overview about cross company data sharing policy first to set the base for the readers, the Cross-Company data sharing lets you have your data accessible from multiple legal entities (companies in D365 FinOps). For example, if you setup a policy for vendors to be crossed-company then whenever you create a new vendor it will be created in all data sharing legal entities. https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/cross-company-data-sharing Now, What happened when you a table under cross-company data sharing (e.g. VendTable) and want to sync vendors through dual-write? Since, VendTable is one of the data sources for Vendors data entity (dual-write entity map) and we know dual-write does not work well with cross-company data sharing by design. You get following error message when...

D365FO: π™‡π˜Ύπ™Ž π™šπ™­π™₯π™€π™§π™©π™šπ™™ π™—π™–π™˜π™₯π™–π™˜ π™π™žπ™‘π™š π™˜π™€π™£π™©π™–π™žπ™£π™¨ π™˜π™€π™§π™§π™ͺπ™₯π™©π™šπ™™ 𝙙𝙖𝙩𝙖

If you experience below error message when trying to import bacpac file into tier 1  (DEV)  environment then use the suggested steps to get over this error and get your database imported. Importing to database 'AxDB_Daxture' on server '.'. SqlPackage.exe : *** Error importing database:Could not load package from 'C:\Users\Adminb1c06345af\Downloads\daxturebackup.bacpac'. At line:13 char:5 +     & $LatestSqlPackage $commandParameters "/p:CommandTimeout=0" +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (*** Error impor...backup.bacpac'.:String) [], RemoteException     + FullyQualifiedErrorId : NativeCommandError   File contains corrupted data. Based on this docs link  https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/import-database , download the .NET CORE version of SqlPackage.exe. This is the .zip fi...

Tips and Tricks on how to validate your dual-write integration field-by-field level - its easy believe me 😊

After you are done with your entity field mappings for a required entity map e.g. for Vendor Groups, we started to look at in previous post to get the payload for dual-write integration, two records get created in the following tables. 1. DualWriteProjectConfiguration 2. DualWriteProjectFieldConfiguration Records only get created when you Run the entity map and get deleted once you stopped it. DualWriteProjectConfiguration table does not hold data for Vendor groups when the entity map is stopped. DualWriteProjectFieldConfiguration table does not hold data for Vendor groups when the entity map is stopped. Run the entity map and check data in these tables,   1. Both tables link each other using Name field 2. For each entity map (e.g. Vendor groups) there are two records; one for Insert and Update and the other one is for delete which ends with _end Import information about DualWriteProjectConfiguration table: 1. External URL field holds the CDS environment's URL which is linked wit...