Microsoft Dynamics 365 and Power Platform Library

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

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

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

Let's continue where we left in first post "What got changed (Technical) in D365 Finance Operations with dual-write" our journey to understand what are the technical changes being done for dual-write framework. This post we will look at what are highly used tables, entities, and classes involved for dual-write sync. I will only cover few tables, classes, and data entities but complete list of objects can be explored from AOT as shown below. Business scenario: Create or update Vendor Groups in FO and sync over to CDS and vice versa. Open Vendor groups screen - Accounts Payable > Vendors > Vendor groups Out-of-the-box dual-write template is available for vendor groups These fields are mapped between Finance and Operations apps and Common Data Service for Vendor groups dual-write template. NOTE: only data will sync between apps only for mapped fields and the integration will also only trigger when we change data for these mapped fields in either side of the integrat...