I am not mentioning the Dual-Write table maps here, but we were using OOB tables maps on the Order table. In case you have updated with custom table maps, you may want to check it (in case the address is still not updating).
Hope this helps!
This Dynamics 365 CE blog is all about offering you insights and solutions on Customer Engagement, Power Automate, PowerApps, and Dataverse. Stay ahead of the curve with our actionable advice and unlock the full potential of Dynamics 365 CE for your business.
I have written couple of articles on Dual-Write lately. Mostly on issues that we've been facing lately and how we have come to fix them. These post is where I bring them all together. You can think of this blog post as a summary of all the issues and fixes until now and will continue to update the same in the future.
Also certain topics don't need a separate post. Will write about them here directly. Starting below with the posts that I have written previously.
This was because we were receiving an error
"Write failed for entity CDS sales quotation header with unknown exception - BOX API can't be used from non-interactive sessions."
Click here to read the post.
There are certain security roles and privileges required to perform initial sync of tables via dual-write.
Click here to read the post.
This happened because there were related records, and I wasn't able to delete them too.
Click here to read the post.
Unable to create an order from a quote in Dynamics 365 Sales App
Here is the precise error that I was receiving.
"Write failed for entity CDS sales order lines V2 with unknown exception - Inventory dimension Site is mandatory and must consequently be specified.\nUpdate has been canceled."
Click here to read the post.
If you're unable to open Dual-write page by selecting the Dual Write tile in the Data management workspace, most likely data integration service is probably down.
For this you would need to create a MS support ticket and request a restart of the data integration service.
Here is a note for y'all, something to keep in mind when working with workflows in Dynamics 365 Customer Engagement (D365 CE).
You can create a workflow (i.e., initiate a workflow) on the following tables:While converting a Quote into an Order in D365 CE Sales, I was receiving an error message that went like:
Dual Write core application error-Dual Write core application error-Unable to write to Finance and Operations apps due to following error(s): {"Write failed for entity CDS sales order lines V2 with unknown exception - Inventory dimension Site is mandatory and must consequently be specified.\nUpdate has been canceled."} Please rectify your data and try again. If issue persists after multiple retries, please contact your system administrator.
Since dual write is seamless integration and data synchronization across D365CE and D365FO and as the default shipping site and warehouse is required while creating the Order in F&O, we need to ensure that the value is populated prior to creating the Sakes Order.
While encountering an error can be frustrating, the good news is that there is a solution.
In this case, the remedy involves performing relationship mapping between the Quote and Order entities. Relationship mapping essentially defines how data is transferred between related entities.
Steps:
There could be many reasons and most of it could be found when you perform an online search, but none of those suggestions fixed my issue. When I was qualifying the Lead into an Opportunity, it is showing the following error:
OrganizationServiceFault
And that is it. No other details about the error. No error log, not description of the error, no error code. Nothing!
My user didn't have system administrator, but a custom role was assigned to the user. I took some help from my technical team who did a little bit of digging and came across this below message.
Entered Microsoft.Dynamics.SCMExtended.Plugins.Plugins.LeadPrimaryContactPostCreate.Execute(), Correlation Id: 021c0dc2-3e1e-46e5-81c0-b1524ae09ed2, Initiating User: e7925424-1da4-ed11-aad1-002248a13b63
Exception: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Principal user (Id=xxxx5424-xxxx-ed11-xxxx-002248a1xxxx, type=8, roleCount=4, privilegeCount=1064, accessMode=0, MetadataCachePrivilegesCount=9751, businessUnitId=0b2c4b59-0e31-ee11-bdf4-000d3aba3d29), is missing prvReadSolution privilege (Id=b64e92c8-5d2a-4052-a026-1b73eff9cebf) on OTC=7100 for entity 'solution' (LocalizedName='Solution').
I provided a Read privilege to Solution table under; relevant Security Role > Customization > Solution, and it worked.
Hope it helps!
Reason: Bad Request, Header x-ms-client-request-id 8aef8aa3-2a01-493e-a0d7-347ce560e50d, Principal team (Id=b7e1929e-xxxx-xxxx-aad0-xxxx489fxxxx, type=9, teamType=0, privilegeCount=0, MetadataCachePrivilegesCount=9751, businessUnitId=b5e1929e-xxxx-xxxx-aad0-xxxx489fxxxx), is missing prvReadmsdyn_globalproduct privilege (Id=539cf392-xxxx-xxxx-b258-xxxx719b7d93) on OTC=10835 for entity 'msdyn_globalproduct' (LocalizedName='Global Product') in Business Unit: unqxxxx (Id=b5e1929e-xxxx-xxxx-aad0-xxxx489fxxxx). context.Caller=691e1af2-xxxx-xxxx-aad1-xxxx489axxxx
Sometimes when you're excited and hurrying into the action, you miss the fine details and here are the fine details.
Security role that is required
Every user in a customer engagement organization with dual-write must be given Dual-Write Runtime User role. Without this role, users will be unable to create any rows in tables in customer engagement organization.
Company and currency exchange tables are global in nature and all dual-write users require read access to these 2 tables. To provide access, all dual-write users must be given Dual-Write App User security role. If a user does not have this security role assigned to them, they will not be able to read tables that contain Company and Currency.
Also access is required to entities (tables in dataverse) that are in scope of dual-write. However which privilege is required is not very clear. What you can do is to create a custom role and provide the relevant privilege to the tables in scope of your dual-write integration. We had provided Create, Read and Write which worked for us.
PS: I do believe Read privilege should be enough. Comment down below if you have an experience regarding the exact privilege required.
Here is the link to other considerations before performing initial sync & setup dual-write security roles and permissions.
Hope this helps!
We have enabled Dual-write in one of our environment's and we have the Quote table in running status for dual-write sync however, when we try to create a Quote in D365 Sales, for some reason it was failing and the error message was like below.
"Write failed for entity CDS sales quotation header with unknown exception - BOX API can't be used from non-interactive sessions."
To approach this, we ensured that we have followed and setup the prerequisites mentioned in Microsoft's documentation about Quote-to-cash in dual-write
Also we were using Trade Agreements pricing engine and the setup for that is mentioned here: Sync on-demand with SCM pricing engine
What we did was, we went to form "Sales and marketing parameters" in Finance and Operations to check if the field "Create opportunity for sales quotation" is set to Prompt.
If it is set to Prompt, you need change to another value based on your requirement. We changed this to No and tried creating the quote. It worked!
ClickDimenions is a marketing automation tool for Dynamics 365 Customer Engagement (CRM). Tool wouldn't be the right terminology as it is a very comprehensive application to address all your marketing needs.
While the online help and guides provided by ClickDimensions are very detailed, I thought to summarize this in below few steps to register and install the app in your environment.
One of the most common ask from our customers is, does the app block one user from accessing or making changes to a record if another user has opened the record on their screen?
While this is not quite like restraining a user from updating a record because of multiple users accessing it, this feature does allow you to see the other folks that are collaborating on the same record.
You’ll need to enable this in your environment to take advantage of this feature.
While exploring the default forms and views for Dynamics 365 Sales I understood few facts. It is strange how even after years of experience on the product there are still some things that you have never explored.
I guess the main reason is that these don't impact any implementation in a major way, hence you tend to ignore them, and only find out by accident, like I did. So here are the facts.