locked
CRM2011 OptionSetId Cannot be Changed when Importing Unmanaged Solution RRS feed

  • Question

  • I encountered the following error whilst trying to import an unmanaged solution to a newly created organisation:

    OptionSetId cannot be changed. EnumAttributeInfo.AttributeDescription.OptionSetId(fc59f076-91db-4c64-9def-d986072facad) != 3134c0e2-e243-e011-8f0e-0050563f34ac

    I cannot find any information on this error or on how to proceed. Interestingly, neither of the Ids given for the OptionSets seem to exist in the DB on either server (the source or destination).

    We had been moving some local optionsets to be global prior to exporting the solution so perhaps this is the issue?

    Any suggestions, links etc. very much appreciated!

    Tuesday, March 15, 2011 7:18 PM

Answers

  • I am assuming your environment is something like:

    Test:only test data with all customizations

    Production: all data and all customizations

    You made the changes in the test organization by deleting the attribute and then re-creating it with the same name.  Exported the customizations from the test organization and then tried to import into the production organization.  This would be failing because the local picklist attribute still exists in the production environment.  If you delete the local attribute from the production environment then you should be able to import the solution from the test environment.  Note that deleting the attribute from the production environment will also delete the data.  If you want to keep the data then you will have to create a new attribute with different logical name, and then probably use some code to copy the values from the local picklist attribute to the global picklist attribute.

    -Brandon

    • Marked as answer by glosrob Monday, March 21, 2011 8:19 PM
    Monday, March 21, 2011 5:38 PM

All replies

  • Hello -

    Did you hand tweak any of the customizations.xml file?  This seems like an issue with local option sets (picklists) and global option sets (option sets in the app) clashing.  How did you go about moving local option sets to global?  You can't do this unless you delete and then re-create the attribute.  The product does not support promoting local option sets to global option sets.

    -Brandon

    Wednesday, March 16, 2011 7:41 PM
  • Hi and thanks for taking the time to answer.

     

    No, no customising of the exported file. The process was as follows:

    - Originally we had a field linked to a local optionset

    - deleted the attribute on the account

    - created a global optionset

    - created a new attribute using the global optionset

    - saved, published, exported

    - On import to a new server, we experienced the error above

    In total there were around 10 optionsets we changed like this.

    Thursday, March 17, 2011 11:21 AM
  • I am assuming your environment is something like:

    Test:only test data with all customizations

    Production: all data and all customizations

    You made the changes in the test organization by deleting the attribute and then re-creating it with the same name.  Exported the customizations from the test organization and then tried to import into the production organization.  This would be failing because the local picklist attribute still exists in the production environment.  If you delete the local attribute from the production environment then you should be able to import the solution from the test environment.  Note that deleting the attribute from the production environment will also delete the data.  If you want to keep the data then you will have to create a new attribute with different logical name, and then probably use some code to copy the values from the local picklist attribute to the global picklist attribute.

    -Brandon

    • Marked as answer by glosrob Monday, March 21, 2011 8:19 PM
    Monday, March 21, 2011 5:38 PM
  • You are correct about the setup.

    That seems so obvious now!

    I won't be able to test this for a week or so (on to other things) but am happy this will solve the issue.

    Monday, March 21, 2011 8:19 PM