locked
How to default to the Unmanged soluton rather than defualt solution when customized form within the entity form RRS feed

  • Question

  • I have been reading the solution in CRM 2011.  It sound like is a good way to handle revision.  All revision should be packaged into a managed solution.   But during the development, all modification should be done within the unmanaged solution.

    Entity form can be customized while the form is opened, but it is always open against the default solution rather than unmanaged solution.  Is there any reason for that or is there a way to make all the changes default to the unmanaged solution? 

    Wednesday, March 14, 2012 7:51 PM

Answers

  • In case you want to go ahead and try managed solutions, my suggestion would be to have a thorough understanding of the managed solution properties. Also, play around with the managed solutions by creating multiple ORGs in your DEV environment.

    I had issues in one of my projects last year.

    To start with the managed solutions can be layered on top of one another. This provides a nice layered architecture, but you have to be careful how to set customizable properties. A managed solution has components inside it. The managed solution should enable the customization of its components so that other managed solution can be installed on top of it which in turn can make further changes to these components. If a managed solution doesn't enable customization of its components, then problem can arise installing other managed solutions on top of it with same components.

    The other problem comes when you want to delete the components which are part of the managed solution. You cannot directly delete. The only way to remove is to uninstall this managed solution. Then go back to your un-managed solution through which you created this managed solution. Remove the components you wanted to delete. PLEASE NOTE, REMOVE components from un-managed solution and not DELETE. Then again export this unmanaged solution as managed and import it where you previously had uninstalled it. This is a very time consuming process if you are working on a critical project. Also uninstalling a managed solution removes all the data.

    I hope this helps.  If my response answered your question, please take a minute and mark the response as an answer.


    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Thursday, March 15, 2012 9:17 AM

All replies

  • Everything in an unmanaged solution is simply a reference to the objects in the base layer - the default solution.

    So no matter which way you edit it, you are editing the same actual entity and the changes will show up in both places.

    Just make sure you are using the same publisher for both, or at least that your publishers are using the same "prefix" so that any custom things you add (new fields for example) will get a consistent naming convention.


    Hope this helps. Adam Vero, MCT

    Wednesday, March 14, 2012 10:41 PM
  • I agree with Adam. Unmanaged solution components are simply pointers to the actual components (in default solution). So if you delete an entity from an unmanaged solution, you also delete the entity from CRM.

     

    Also, what you said about packaging into a managed solution. I don't see any logic in going for managed solution unless the need can be really justified. Managed solutions are pretty tricky to deal with. In most of our requirements, even if we are deploying changes to Production, we can simply go for unmanaged solutions. Managed solutions should be used if we foresee in future, the need to, uninstall these changes as a single entity. Also managed solutions are used by companies who sell or distribute CRM 2011 add-ons at Dynamics Marketplace.


    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Thursday, March 15, 2012 3:47 AM
  • Ashish,

    When you said the Managed solutions are pretty tricky to deal with, would you elaborate a bit or give some examples.  Thanks.

    Thursday, March 15, 2012 5:40 AM
  • In case you want to go ahead and try managed solutions, my suggestion would be to have a thorough understanding of the managed solution properties. Also, play around with the managed solutions by creating multiple ORGs in your DEV environment.

    I had issues in one of my projects last year.

    To start with the managed solutions can be layered on top of one another. This provides a nice layered architecture, but you have to be careful how to set customizable properties. A managed solution has components inside it. The managed solution should enable the customization of its components so that other managed solution can be installed on top of it which in turn can make further changes to these components. If a managed solution doesn't enable customization of its components, then problem can arise installing other managed solutions on top of it with same components.

    The other problem comes when you want to delete the components which are part of the managed solution. You cannot directly delete. The only way to remove is to uninstall this managed solution. Then go back to your un-managed solution through which you created this managed solution. Remove the components you wanted to delete. PLEASE NOTE, REMOVE components from un-managed solution and not DELETE. Then again export this unmanaged solution as managed and import it where you previously had uninstalled it. This is a very time consuming process if you are working on a critical project. Also uninstalling a managed solution removes all the data.

    I hope this helps.  If my response answered your question, please take a minute and mark the response as an answer.


    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Thursday, March 15, 2012 9:17 AM
  • Thanks for taking the time to explain.  It is very helpful.
    Saturday, March 24, 2012 12:20 AM