Personalized Community is here!
Quickly customize your community to find the content you seek.
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
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
I registered a service endpoint from dynamics on create of lead entity for sending message to Azure Service Bus Queue.
I created a logic app on a trigger when a mesaage is arrived in Queue until here everything is working fine.
But I dont know how can I extract the properties of lead entity passed from dynamics in logic apps.
Any help would be appreciated.
You need to use parse json action to extract remoteexecutioncontext object.
Thanks for your reply.
The remoteexecution context comes as a byte array.Do I have to use base64ToString() expression to convert byte array of content to string?
How can I get schema for lead entity?
See below article which has some predefined convert function related to logic apps.
Why don't you use Logic App Common Data Service(Current Environment) Connector - when record created or updated instead of sending the data first to service bus queue using service endpoint and then using service bus queue trigger?
Thanks for sharing the link.
Yes,Logic App Common Data Service(Current Environment) Connector is obviously an option in this case but by registering service endpoint we can send message to service bus in a scenario like Associate,Disassociate etc which are not available for CDS connector.This is the reason I'm exploring this option so we can extend this in future.There might be other options but at the moment I have to prove this can work.
I have tried base64toString(content) to convert byte array to string but now I'm stuck how to convert this string to readable format so I can use dynamics fields in Logic Apps.If you could help me that would be much appreciated.
Add parse json action, copy the string which you have got by converting from byte to string. Now on parse json action click use sample payload link and paste this string to generate the schema. This is one time job.
I don't think value is in json format so try using Json convert function to first convert this string to json and then use that to generate schema in parse json action.
Now when you add any action in next step you should be able to get the dynamics data from parse json action.
Thanks Bipin for your help.So I have to write an azure function to convert this converted string from byte to JSON string.
I thought there would be some out of the box logic app connector which I'm missing.
Business Applications communities