[slarsen]

I am updating a bundle from sandbox to production. One of the items is a saved search which has two columns on the results referring to custom fields.

In the bundle, it automatically includes these two custom fields, which is fine, even though they exist on production already. The problem is when I perform the update NetSuite sees the conflict with existing objects and my only options are Add and Rename OR Replace Existing Object

What does Replace Existing Object mean? These objects obviously have data associated with them in records. When it performs the replace, will the data be preserved or will it all get wiped out? This is critical and very confusing. Imagine saying “Oh go ahead and replace it since I haven’t made any changes” and then it wipes out the previous object AND data and installs this new one.

Can someone confirm the actual behavior of this AND NetSuite, could you use less obfuscated wording, particularly with something as critical as overwriting data? Like Update Object or Replace and Preserve Data?

Thanks.
This is a cached copy. Click here to see the original post.

[slarsen]

RE: Updating bundle – what does Replace Existing Object actually mean?

Bump…. anybody? Dead in our tracks as we are not taking the chance until we get some sort of confirmation. NetSuite? Anyone?

[slarsen]

RE: Updating bundle – what does Replace Existing Object actually mean?

For those that may run into this…

The documentation explains ‘Replace Existing Object’ but doesn’t explain what happens to any records where this object is already being used — particularly does it wipe out the data set in the field for those existing records or not. Though you would “think” it does not, it would certainly be better to see that in writing somewhere.

I did receive confirmation from NetSuite product management and it’s here for anyone else searching on this issue (there is also an enhancement to add this to the documentation).

It updates the field definition to match that in the source account. If it is really the same field, with the same properties, then there won’t be any discernible impact. Notably data entered into the field on case (or whatever) records won’t be deleted or modified.

However, if it is a different type of field altogether (say the existing field is TEXT and the incoming field is INTEGER), then data will have to be deleted as numeric fields can’t hold text values. Note the same thing happens regardless of bundler when you edit an existing field in a single account and change it’s type (a popup warns you data will need to be deleted).

But in the case that it is truly not the same field, then you should probably choose Add & Rename which will create a new field and change the script ID so it is unique

[BrettKnights]

RE: Updating bundle – what does Replace Existing Object actually mean?

Thanks for following up on this and posting your results.

Because one of the scripts I was bundling had a saved search as a parameter I wasn’t able to remove the search from the bundle so this was fairly critical information.

[rmercene_ns]

Yes, and just to add to what was mentioned above, NetSuite has documentation in the Help Center under:

SuiteFlex (Customization, Scripting, and Web Services) : SuiteBundler : SuiteBundle Installation and Update : Resolving Conflicting Objects

The documentation above details the difference between Add and Rename and Replace Existing Object.

Note that if we Replace Existing Object for custom records and lists that contain data, users are now given an option as to what they want to do with their data. Users can choose to either Replace Data, Preserve Data or Merge Data between the source and target accounts.

[BrettKnights]

RE: Updating bundle – what does Replace Existing Object actually mean?

I really hope the default is “Preserve Data” If you meant one of the others but didn’t you can always update the bundle. If you meant to Preserver Data but didn’t you are hosed.

[rmercene_ns]

Hi Brett, yes, the default is Preserve Data for that one.

[Author]

Posts