granularity of crm solutions? RRS feed

  • Question

  • Hello - Is there an online reference I can refer to regarding the recommended level of granularity for managing CRM solutions? For example, my implementation has a standalone solution for Case.

    However, if I create a standalone solution for Dashboard then it includes both Case and Task entities as well since both Case and Task entities are dependencies of Dashboard.

    Therefore, if I deploy the Dashboard solution then I'm assuming that all Case changes will be deployed with it, right?  In your experience do you find that this makes releases trickier to manage with all these dependencies?  In other words, deploying all pending changes for Dashboard in this scenario will deploy all pending changes for Case and Task as well, right?
    Monday, August 19, 2013 9:10 PM

All replies

  • The following resources from the SDK are very good at explaining this:

    Introduction to Solutions http://msdn.microsoft.com/en-us/library/gg334576.aspx

    Compartmentalize Your Solutions http://msdn.microsoft.com/en-us/library/gg334353.aspx

    If your solution has dependencies, as long as you know that they will already be on the target system, you don't have to include them in your solution. So when adding an entity, you don't have to add the related entities. So if you add a dashboard that depends on the task and case, provided they exist in the target system (with the correct views) you can ommit them from your solution.

    That said - I find that unless your solution dependencies are purely webresource based - it is far less error prone to have a single solution for your configuration customisations. 


    Scott Durow
    Blog www.develop1.net    Follow Me
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Tuesday, August 20, 2013 6:53 AM