Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am looking for a resilient way to publish changes on D365. I have done a POC using the below methods.
1) Use logic apps to connect to D365 instance using Common Data Services connector which get triggered upon any changes to connected entity. I have tried disabling the logic app to simulate the scenario in case the logic app fails for some reason. I found out the logic app does not trigger for the updates done when enabled. Is that expected behavior? I am thinking from resiliency perspective.
2) Registered a service end point to publish the changes to service bus. I found the messages published were verbose and its tedious to work out the changes by dissecting the message.
What is the recommended way to publish the changes on the D365 entity?
I suggest choice #1
This is a trend that MS encourages the customer to use Power App/ Power Automate/ Logic App to connect to CDS using low-code development platform.
If you find any Logic apps cannot be triggered, you can submit a support request to Logic apps team for help.
based on my experience with Logic Apps, every time you reenable it (being Disabled beforehand), you're expected to trigger the trigger :).
upon enabling the logic app it does not trigger automatically. hope that helps
Business Applications communities