Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
Hi, In need of some help!
We've set up coupling via table 5331 (see this post: https://community.dynamics.com/business/f/758/p/301394/870926#870926) and the records appear to be 'half-coupled'. There were no error messages when applying the package and we can get to CRM records from BC, but not the other way around.
Does anyone know what is wrong? It feels like the coupling is only 95% complete. That there is something missing in the coupling somewhere in BC which is required when we go back from CRM. We noticed in page 5341 ("ACCOUNTS - DYNAMICS 365 FOR SALES") that the records still appears as Coupled = No (even though we can open the CRM record from BC).
Thanks in advance!
For posterity, I finally found the solution to this. Referring back to the instructions on the original coupling steps (community.dynamics.com/.../870926), we found that adding the table id to the import file (eg Customer = Table ID 18) made the connection work from CRM to BC.
Business Applications communities