Dual Write Error - Query extended range failure: Syntax error near 94

The error "Query extended range failure: Syntax error near 94" was showing up when a Vendor was created in D365 FO. The setup includes Global Address Book with Vendor Concept based on Accounts.

The root cause of the issue was a typo in the Filter Condition - Left Hand Side - FO.

(((VendorPartyType == "Organization") || (VendorPartyType == "Person")) && (VendorGroupID != 'ABC'))

As described in the Filter documentation (Link), double quotes must be used for string instead of single quotes. The following query works fine.

(((VendorPartyType == "Organization") || (VendorPartyType == "Person")) && (VendorGroupID != "ABC"))

Cheers!

Dual Write Error - Write failed for entity CDS Contacts V2 with unknown exception

In my current project we had to remove the Global Address Book Solution for Dual Write from the Environment. During this process, the following error was occurring on Customer Create.

Write failed for entity CDS Contacts V2 with unknown exception - Field 'Associated party number' must be filled in.\nvalidateField failed on field 'smmContactPersonCDSV2Entity.AssociatedPartyNumber'

The problem was that the plugin "Microsoft.Dynamics.SCMExtended.Plugins.Plugins.LeadPrimaryContactPostCreate: QualifyLead of lead" was still deactivated. This Plugin is about to be disabled on install of GAB (Link) and this Error is what you are facing if you do not enable it afterwards.

Cheers

D365 CE - Failure 0x80040203 AttributeId is null

Since I have seen this failure now in my last project and also got some questions from others in the past, I just wanted to document our root cause as well here. There are already posts out there but the one I found did not really explaining the issue itself my point of view.

In our scenario, we just enabled Virtual Entities for a PoC in one of our lower test environments (not in dev due to some infra topics) and added a lookup (n:1 Relation) to this Virtual Entity. Afterwards we decided to go without the Virtual Entities due to the current limitations and created a Lookup with same name but to a regular Entity. The problem was that the PoC was not reverted before we deployed the final solution in the test environment which caused this (not really helpful) error message "0x80040203 AttributeId is null".

Cheers

Dual Write - Failed to get template prerequisite sequences

 Today we were facing a strange issue in a Dual Write setup. We just stopped a map for a testing a specific scenario in FO an afterwards, we could not reenable (Sync) the map. The Error message "[Unknown] Failed to get template prerequisite sequences. - The specified item 'xxx' does not exist in the graph" was shown instead of the Sync-Window.

To solve the issue, we just changed the map version to an older instance (e.g. v1.0.0) and afterwards back to our current version (v1.0.1).

Cheers