Common Data Service Solution Development – Best Practices


I started with series of articles about managed and unmanaged solutions from the ISV (Independent Software Vendor) perspective. You can find the first about merging forms and layering views here, and the second about missing dependencies here. I was thinking about the next topic in the managed vs. unmanaged series and decided to start over with best practices for CDS (Common Data Service) in general.

I just want to state one thing. We are ISV. We build and endorse managed solutions and these best practices are our own based on the documentation from Microsoft and implementations of customer projects.

Continue reading “Common Data Service Solution Development – Best Practices”

Missing Dependencies – managed vs unmanaged PART 2 (Microsoft Power Platform and CDS)


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)”