locked
Publishing Customizations CRM 4

    Question

  • Hi,

    this is probably a really dumb question......but here goes...

    If you make several customizations to a CRM Test system, then you are happy with the changes, is there a way to publish to the Live system from within the Test system? (I know it sounds really dumb, but it would be really convenient).


    Cheers and regards Rossco
    Thursday, May 13, 2010 3:06 AM

Answers

  • Actually the Attribute definitions are exported in the file and re-created on the target system when the configuration file is uploaded - it works just fine.

    You'll run into more problems if you create attributes on the two systems manually - such as when you create the attribute slightly differently on test vs. live - very tough to maintain consistent implementation.

    The tool Tiaan mentions is great, (I was thinking about it last night when I added the followup to my own post.) I'm not sure it's a match for your scenario. -

    If you've been manually modifying the attributes on both systems independently, I'd encourage you to export a config file from production and create a new 'fresh' dev environment. - From that point forward, in as much as possible, make your changes in one system and export/import them to the other. 


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, May 13, 2010 3:00 PM
    Moderator

All replies

  • No, but you cen export them as a customization XML file and then import them to your production system. - doesn't take more than a few seconds -

     


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, May 13, 2010 3:18 AM
    Moderator
  • There are some additional tools out there for synching customizations automatically - but I don't see those as a solution for your need to publish to production on demand.

    HTH. -

     


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, May 13, 2010 3:19 AM
    Moderator
  • No, but you cen export them as a customization XML file and then import them to your production system. - doesn't take more than a few seconds -

     


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell


    Hi Scott,

    thanks for the quick reply.....but you can't export the attributes can you? so you still have to recreatee the attributes on the live system?


    Cheers and regards Rossco
    Thursday, May 13, 2010 3:29 AM
  • Hi yes there is an easier way!

    http://blog.halan.se/file.axd?file=2010%2f3%2fCcmSetup1.15.exe

    The main features of CRM Configuration Manager are,

    • Easy access to the features of CRM Customization Manager
    • Possible to select a CRM server as destination, allowing one click export and import.
    • Create advance export/import selections for later use inside scripts / installations

    This release includes CRM Customization Manager v2.0 that contains fixes and few new features,

    • JavaScript Export/Import, This allows you to extract JavaScript to a local folder, where you can work in a proper script editor, and later import them back. You can also create new javascripts in the same folder, just follow the name convention and they will also be imported to the correct entity / event.
    • Zip support, Now all features works with zipped customizations
    • Include Related Entities, This features will automatically include related entities to the selected entities, so their relationships are exported and can be reviewed for conflicts. This is recommended during the development process when relationships may change.
    • Publish Workflows, Publish operation now also publishes workflows

    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Thursday, May 13, 2010 5:24 AM
  • Actually the Attribute definitions are exported in the file and re-created on the target system when the configuration file is uploaded - it works just fine.

    You'll run into more problems if you create attributes on the two systems manually - such as when you create the attribute slightly differently on test vs. live - very tough to maintain consistent implementation.

    The tool Tiaan mentions is great, (I was thinking about it last night when I added the followup to my own post.) I'm not sure it's a match for your scenario. -

    If you've been manually modifying the attributes on both systems independently, I'd encourage you to export a config file from production and create a new 'fresh' dev environment. - From that point forward, in as much as possible, make your changes in one system and export/import them to the other. 


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, May 13, 2010 3:00 PM
    Moderator
  • Actually the Attribute definitions are exported in the file and re-created on the target system when the configuration file is uploaded - it works just fine.

    You'll run into more problems if you create attributes on the two systems manually - such as when you create the attribute slightly differently on test vs. live - very tough to maintain consistent implementation.

    The tool Tiaan mentions is great, (I was thinking about it last night when I added the followup to my own post.) I'm not sure it's a match for your scenario. -

    If you've been manually modifying the attributes on both systems independently, I'd encourage you to export a config file from production and create a new 'fresh' dev environment. - From that point forward, in as much as possible, make your changes in one system and export/import them to the other. 


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell

    Thanks Scott and Tiaan,

    Scott, you are absolutely right about the creation then manual recreation of customizations...as I have already run into issues because on one system something small was just slightly different...for some reason I thought the attributes were not included on the XML file, so thanks very much for that info and clearing that up for me :-)

    One more confrimation though, by config file you are referring to the standard Import/Export Customizations options??

    Tiaan, thanks for the link and the info :-)


    Cheers and regards Rossco
    Thursday, May 13, 2010 8:17 PM
  • Hi,

    got it now...thanks both of you :-)


    Cheers and regards Rossco
    Thursday, May 13, 2010 9:55 PM