granularity of crm solutions?

All replies

• 

  

  0

  Sign in to vote

  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. 

  hth

  
  

  ---

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

  • Proposed as answer by Scott Durow (MVP)MVP, Editor Tuesday, August 20, 2013 6:54 AM

  Tuesday, August 20, 2013 6:53 AM

  Answerer