none
CRM 2013 Solution Import

    Question

  • Hi

    I did an test upgrade for a customer to CRM 2013 by taking a backup of the CRM 2011 database
    and then importing the DB to CRM 2013 on a new server (UAT_MSCRM).  The import was successfull
    and the UAT users could access the new CRM 2013 UAT system (UAT_MSCRM).  I made some
    changes to the CRM 2013 solution as I merged the majority of the forms for
    Accounts/Contacts etc. and also made other cosmetic changes.  The customer 
    then decided to do go live with CRM 2013 so I took a backup of the
    UAT_MSCRM solution as this contained all of the customizations.

    I imported the live CRM 2011 database to CRM 2013 (Live_MSCRM) and this database imported
    successfully.  I then went to import the solution from UAT_MSCRM into Live_MSCRM
    and I get the following error:

    'The label 'fieldname',id:'023123-123123123-23-123-123123' already exists. Supply unique
    labelid values'

    If I remove the entity in question and try importing
    solution again I get the error on another entity with different fields.

    I think this may be something to do with merging of forms.  I don't want to merge
    the forms again manually on Live_MSCRM as this took me a long time to do in
    UAT_MSCRM and I assumed we would just be able to import the solution

    Thanks
    Sukh

    Wednesday, January 08, 2014 3:28 PM

All replies

  • I am also similar issue. And not found any solution.

    Monday, January 13, 2014 1:17 PM
  • I know it is pretty old thread but if you have got around the solution for this, please let us know.

    -r

    Tuesday, April 29, 2014 2:34 PM
  • I had hoped MS had fixed this by now but just hit it again in a CRMOnline environment. The easiest/safest way to get around this is to open up the problem form in your dev/test environment, then one by one add new tabs, sections and fields so that they are the same as the existing ones then delete the existing tabs. Re-export your solution then you should find it imports fine to the destination org.

    I believe the issue is due to the 'merge forms' button not giving each tab/section/field on the new form unique GUIDS and simply copies the old ones resulting in duplicates and hence the solution import error.


    MCTS. GAP Consulting Ltd. Microsoft Community Contributor Award 2011 & 2013

    Tuesday, May 06, 2014 1:49 PM
    Answerer
  • Rob,

    As much as I agree your suggestions will work, it introduces a significant increase in effort. What started as a 30 minute merging exercise will likely grow into a  4  to 8 hour task.

    Does anyone know if MS is aware of this issue? Are they working towards a fix?

    Cheers!

    Mark

    Friday, June 06, 2014 5:28 PM
  • Maybe an MS employee could comment on that one?

    MCTS. GAP Consulting Ltd. Microsoft Community Contributor Award 2011 & 2013

    Friday, June 06, 2014 6:22 PM
    Answerer
  • A quick update.

    Well, the good news is that the case was the only entity that gave me problems during the merge. All the other entities, account, contact, lead, opportunity merged without any issues.

    I'd still like MS to fix this.

    Cheers!

    Sunday, June 08, 2014 12:43 AM
  • Hi all,

    I have just seen and reviewed your post and would like to comment on this on the behalf of the CRM Support Team.

    First of all I am sorry to hear about that you run into this issue. We very much appreciate and listen to your feedback – it is critical for us and enable us to further improve and build best in class products and services. If you have a product or service suggestion, I would encourage you to log it at Microsoft Connect platform https://connect.microsoft.com/ and provide insight to the Microsoft development community about it. Thank you very much in advance.

    In regards to the issue - I can confirm that this behavior has been lately reported to us as a design mistake and we are currently investigating if the issue is eligible to be fixed as a Hotfix. I have internally reported that you are also affected by this issue.

    I will update the thread once more information is available on this.

    Many thanks for your patience on this.

    Thank you for using Microsoft Forums and Communities.
    Nina Peneva
    Support Engineer
    Microsoft Dynamics CRM

    Follow EMEA Microsoft Dynamics CRM Support on Twitter at https://twitter.com/MSDynCRMSupport

    Wednesday, July 02, 2014 3:20 PM
  • Hi all,

    in addition to my first response,  I would like to ask you to provide me the number of the related Service Requests in case you have already contacted Microsoft Support in this regards. This will allow us to add consider them in our Hotfix Investigation going forward.

    Many thanks in advance.

    Nina Peneva
    Support Engineer
    Microsoft Dynamics CRM

    Follow EMEA Microsoft Dynamics CRM Support on Twitter at https://twitter.com/MSDynCRMSupport

    Thursday, July 03, 2014 8:40 AM
  • I am having this issue when trying to import a solution from my CRM 2013 development org to test.  Is there a hot fix to resolve the issue, or is the recommendation still to remove and recreate all sections on the merged form?

    Thank you.

    Lisa

    Wednesday, July 16, 2014 3:30 PM
  • Hi,

    I am also facing with merge forms after upgrade from 2011 to 2013.

    In 2011, contact having 2 main forms "information" and  contact finance form.

    After upgrade to 2013, information merged with contact  form and created new form (contact finance details) and merged with contact finance form and deactivated both information and contact finance form from contact entity.

    Issue is when importing managed solution  from dev to another environment( dev to preprod) , both contact finance and contact finance details form are showing in active state. Contact finance form should be inactive state.  Is there any product bug?

    please let me know if any one have ideas?

    Thanks

    Tuesday, July 22, 2014 5:11 PM
  • Jukka has a creative workaround for this here:

    http://niiranen.eu/crm/2014/10/dont-merge-forms-in-crm-2013

    He says Save As and then delete the original merged form works for him...


    Simon Hetzel Microsoft Dynamics CRM Consultancy Microsoft Server/Infrastructure Architecture http://uk.linkedin.com/in/simonhetzel

    Saturday, October 18, 2014 11:26 AM