[AGMNS]

We are using a sandbox account for development and have bundled a number of changes and applied them to our production account.

Each new bundle adds in all previous record types, lists scripts etc. when creating a new bundle even though those previous items are not related to a newly created Record Type with an associated list record and selected for the bundle. These of course appear as conflicts when the new bundle is brought into production. These then have to be duplicated(safest choice)by the bundle install. This leads to hours of work to delete duplicate record types etc.

Is there any way to bundle only those record types and move them to production without NS automatically adding all the other previous bundle records?
This is a cached copy. Click here to see the original post.

[smehta]

Have you refreshed your sandbox after it was upgraded to 2013.2? If not, I recommend doing that because then you’ll be able to benefit from the features of 13.2 that will take care a lot of your concerns mentioned here.

Hope this helps.

[AGMNS]

RE: Suitebundler woes

As a follow up to your post Suhas.

I did refresh my Sandbox account and was able to Bundle a custom record type and it’s records that existed in Sandbox to Production.

Thanks for your suggestion.

Now for the results ….

I had previously bundled and moved the custom record type (only the record type) to Production and had created 2 test records. After subsequent modifications and testing in Sandbox I deleted the 2 test records in Production and created a new bundle in Sandbox that contained the custom record type and 110 custom records.

When I brought the bundle into Production I chose to “Replace” the existing custom record type and “Add” the custom records.

Once In production I did a saved search exporting to a csv file of the 110 records. I notice that existing data in some fields did not exist at all in the csv OR the existing data was not in the correct columns in some cases.

I went back to NS and checked an individual record (Setup/Customization/Record Types and then “List” from the record type line) then edit. All the fields were there and their data was correct in the proper fields.

In Production I went to Setup/Customization/Record Types and opened the custom record type. Only about half the fields were listed in the fields tab that existed in the same record type in Sandbox before the bundle was moved to Production.

This is strange and disconcerting behavior for a bundle. Any thoughts on why this may have happened?

As a footnote:

I uninstalled the bundle from Production, deleted the custom record type in Production and reinstalled the same bundle. This time the custom record type had ALL the correct fields and on export from a saved search had all the correct data in the proper fields.

[Author]

Posts