locked
Importing Customizations CRM 4.0 64-bit RRS feed

  • Question

  • I was wondering if I can import customizations from the 64-bit version of CRM to the 32-Bit  I am getting an error when trying to import and I think that is what it is.  Thank you.
    Thursday, March 12, 2009 3:05 PM

Answers

  •  Yes, - you can move a customization from a 64 bit server to a 32 bit server - however, you may get errors if you are moving from one server updated to one of a rollup/patch to another implementation that has not been patched or has a different version of the patch.
    Scott Sewell | http:\\blog.CustomerEffective.com
    Thursday, March 12, 2009 11:02 PM
    Moderator
  • If you are having trouble importing customizations from environment 1 to environment 2, it doesn't have anything to do with 32 vs 64.

    1.  If they are on different rollup versions, then you will get errors.  rollup 3 fixes this, I believe.
    2.  If you have a custom entity in environment 1 that you have already configured in environment 2, or if you have the same entity and you have done created attributes that are also in  environment 1, even if they have the same names and schemas, it can cause errors.  best thing to do is delete the custom entity from environment 2 and import from environment 1 so the configurations are in parity.

    Monday, March 30, 2009 12:18 PM
    Moderator

All replies

  •  Yes, - you can move a customization from a 64 bit server to a 32 bit server - however, you may get errors if you are moving from one server updated to one of a rollup/patch to another implementation that has not been patched or has a different version of the patch.
    Scott Sewell | http:\\blog.CustomerEffective.com
    Thursday, March 12, 2009 11:02 PM
    Moderator
  • Were you able to move the customization from one server to another?
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Sunday, March 15, 2009 7:44 PM
    Moderator
  • No actually it gave me sort of a generalized error.  I updated both to roll up 2 and still got the error.  I am still unable to move the customizations if you have any idea's.  Let me know what you will need as I had to put this on hold sorry I did not get back to you right away but I am very busy trying to get this client live.
    Tuesday, March 17, 2009 5:54 PM
  • I typically will have better luck importing a few entities at a time -

    Can you import just the account (or contact) and see what messages you get -  Once you get one or two entities to import correctly, move on to some of the custom entities.
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Tuesday, March 17, 2009 6:42 PM
    Moderator
  • CRMNoob - 

    Did you happen to export / reimport an object that had relationships with other custom entities intact?

    If so check ou this posting I came across today - it may help describe your challenge - even if it doesn't provide a solution.
     http://stateracrm.blogspot.com/2009/01/how-not-to-mess-up-your-environments-or.html

    This may not include a solution to the problem, but I think it answers the question that you, me and several others have faced recently.

    Scott.
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Tuesday, March 24, 2009 9:18 PM
    Moderator
  • If you are having trouble importing customizations from environment 1 to environment 2, it doesn't have anything to do with 32 vs 64.

    1.  If they are on different rollup versions, then you will get errors.  rollup 3 fixes this, I believe.
    2.  If you have a custom entity in environment 1 that you have already configured in environment 2, or if you have the same entity and you have done created attributes that are also in  environment 1, even if they have the same names and schemas, it can cause errors.  best thing to do is delete the custom entity from environment 2 and import from environment 1 so the configurations are in parity.

    Monday, March 30, 2009 12:18 PM
    Moderator
  • Yes, when it comes to adding attributes to entities they all must originate from the same environment.  Dynamics uses GUIDs as row identifiers in the (meta) data base.  If you create the same (named) attibute in two different location -- even though identical in all aspects -- they will collide upon importing.

    Of course, it would be helpful to know more about what exactly your problem is.
    Monday, March 30, 2009 5:01 PM