Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
We have a separate database (database A) where we are storing all our Dynamics contact IDs. When a record in database A is updated, we are creating a new record in Dynamics. The creation part is working good. However, we are having some trouble passing the Dynamics Contact ID from database A to the Client lookup field in the Dynamics record. Does anyone have tips or documentation for doing this?
On a side note, it looks like the CRUD operations using Dynamics APIs are slowing down the front end for database A. For instance, when we used to update a record, it happened for our users almost instantly. Now, when we do that update and it's tied to creating the record in Dynamics, it takes 2 seconds or so for our users to see the update on their end (database A front end). How can we use the Dynamics API without out slowing anything down?
Any thoughts or comments will be appreciated. Thanks.
Business Applications communities