Personalized Community is here!
Quickly customize your community to find the content you seek.
Microsoft Customer Co-creation
Help impact how the tools and services you rely on are developed. Microsoft Customer Co-creation connects you directly with our engineers so you can provide feedback before a single line of code is written. Interested? Learn more at Microsoft Customer Co-creation
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 2 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 new UCI and the ability to have several model driven apps changed the playground a lot for us ol’ dynamics folks. It brought shiny new capabilities and flexibility but it also brought a tiny bit of more complexity to the game. Suddenly when you want to send an e-mail with a record URL you need to define which model driven app to display to record from. No longer a workflow with a simple “insert record URL”. So what’s the easiest way to get that darn app ID?
Have you also had that requirement? That old one that never seem to die where the customer wants an e-mail with a record URL in it so he/she doesn’t need to go in to the system if not absolutely necessary. Sigh. Well, it happens still, and usually I try and challenge the requirement but sometimes it actually is necessary, and I had to build a flow to solve exactly that for colleague of mine recently.
There is an entity called Model-Driven Apps (appmodules) that are not searchable among the entities in the maker portal.
Therefore it might be a bit difficult to explore, but it contains the model -driven apps in your environment and you can use it as an entity in a power automate action.
Search for the Common Data Service (current environment) connector (read why and how to use that connector here), and use the List records action.
Generally when wanting an App ID you usually only want one result – so make sure you filter your List record action. I of course use FetchXML Builder in XrmToolBox to secure my filter and my result.
That’s it. Now you have you’re app ID ready to use.
If you’d like to read a detailed blog posts with all the steps on how send a record URL with Power Automate, I would recommend you to read this post written by Linn Zaw Win. He uses environment variables to get the app ID which is another way of doing it.
Business Applications communities