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.
As I said we are ISV and we are currently pushing our first product TALXIS Sales Start into the AppSource. We have this application completely in version control and we learned a lot thanks to that. We want to share this knowledge with the world, because not every partner is as experienced as us and we want the customer to be satisfied no matter how many ISVs are there. Since there’s currently no complete ‘how to’ guide on CDS, I feel that we have a lot to say!
Imagine situation where ISV called NETWORG has simple customer relationship management app and your company has field service solution. The customer wants both. There’re two possibilities, you either fight for the customer and will have to create new CRM app, or you cooperate with the other ISV and are able to deliver instantly. The best thing about it is that the customer is happy – that’s everyone’s goal.
But when you meet with other ISVs on one customer you can’t really guarantee the quality of solutions, that aren’t yours… And that’s the reason why we are making this documentation public. We want to make sure, that every solution can meet our quality standards.
You can find the CDS best practices documentation here on this GitHub Wiki. I’ll be adding pages usually once per week there. In addition, there’s always going to be very brief blogpost about the new page here on the blog.
The first page is just a small overview of solutions in general.