Friday 27 July 2012

CRM 2011–Managed Solution–Transport Gotchas


Today, I would like to share some gotchas of managed solution while transporting the customization changes on another organization:

1. You cannot activate/deactivate the views and transport the same status on production server via overwriting the managed solution.

2. You cannot setup default public view and transport the same status on production server via overwriting the managed solution.

3. Similarly, you cannot setup default dashboard and transport the same status on production server via overwriting the managed solution.

4. To expand or collapse tabs on forms, like you cannot expand Notes & Activities tab although you tick “Expand this tab by default” on entity form.
In a same manner, you cannot collapse the tabs like General, Notes & Activities etc. although you unchecked “Expand this tab by default”.

5. Start Auditing on any of your entities is not being transported on production server.

The above points are in my knowledge. Please feel free to append this list with your experiences as well.

1 comment:

  1. I've also found the following problems (in no particular order):

    1) Won't remove values from out-of-the-box option sets.

    2) Can't update out-of-the-box field mappings (error importing managed solution unless mapping to be updated is deleted in target first).

    3) If views are deactivated in target you can't later uninstall managed solution until all views it contains are made active in the target again.

    4) Can't remove managed solution if new form it contains has been "enabled for fallback" and this has also been disabled for the out-of-the-box form.

    5) Some things added to a managed solution and then later removed remain in target org when it is updated. Temporary use of a “holding solution” is required to remove them properly.

    6) Can’t import managed solution if it contains certain types of change originally made in the target organisation (and exported to the source organisation with an unmanaged solution). Despite the wording of the relevant error messages this happens even if the original changes were made in an unmanaged solution that uses a different publisher.

    ReplyDelete