The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
The dual-write core solution
The Common Data Service can connect to Finance and Operations apps
The Finance and Operations apps can connect to the Common Data Service
Apps in tenant
The dual-write registration and runtime plugins
"The reason for that is because the dual write technology is tightly coupled, Synchronous engine and what that means is that the data or the integration have a direct connection between the two system. So for example, FinOps when it needs to send data, it send the data to CDS using direct connection. What you need to do is to create some application users on each application side to allow those incoming connections."
1. One application user is for incoming connections from the data integrator side2. One is for incoming connection from my CDS instance