This is the second part in my series of CDS/Dynamics solution development.
In the last article, I described why you should use managed solutions and why it’s not a great idea to use unmanaged ones. I want to support my suggested best practices in this series in the future so you have the option to make your own opinion. I’m strongly for managed solutions and I’ll tell you another reason why in this part.
Have you ever heard of “missing dependencies”? Well if you are CDS developer like me, I know you have and I know that they are pain in your ***.
Continue reading “Missing Dependencies – managed vs unmanaged PART 2 (Microsoft Power Platform and CDS)”
If you are developing Model-driven app (business application) above the Microsoft Power Platform and you want to follow the best practices, you should deliver your complete solutions (zip packages) as managed solutions to all downstream environments.
Your goal should be to deploy your Model-driven app through AppSource. To achieve that, your app should be separated in smaller packages that can work on their own. For better understanding let’s say, that your app is separated in three main groups.
Continue reading “Merging Forms and Views – managed vs unmanaged (Microsoft Power Platform and CDS)”
You may have used direct links to specific view in the past but you don’t see these sub areas now in your UUI App.
You could have achieved this by using a special URL in the sitemap sub area with the view’s parameters and Dynamics managed to detect your intent when rendering the application navigation.
This is still working but the format has changed for UUI Apps.
Continue reading “Dynamics 365 Unified User Interface: Direct View Links in SiteMap”