Updating Bundles with Segments
When you update an installed bundle in a target account, the custom segment definitions from the source bundle overwrite the account's settings, except for the following:
-
Segment use settings are merged
-
Display order is not changed
-
GL Impact flags are not changed
-
Segment values are preserved or merged.
For any custom segment that includes data, a preference can be set that is applied during bundle updates. This preference indicates whether: the target account custom segment data should be preserved, or data from the bundled custom segment and target account custom segment should be merged, during the update. The default is to preserve data.
On the Set Preferences page of the Bundle Builder, you'll see a list for custom segments with Preserve Data and Merge Data options. If you select Preserve Data, the bundle update doesn't change the target account's custom segment values. If you select Merge Data, the bundle update merges custom segment values without deleting any values from the target account. The avoidance of target account custom segment value deletion is due to the possibility that a custom segment can have GL impact. In addition, no option is provided to replace data for a custom segment, also to avoid unintentional changes to GL impact.
For more information about setting bundle preferences, see Step 4 Set Preferences and Bundle Object Preferences.
If the custom segment type in the source account is changed, the type is updated on the custom segment in the target account. Be aware of the effect the change will have:
-
If the custom segment type is changed from list/record to multi-select, the segment is removed from any transaction sublists. Transaction column applications are not valid for multi-select lists.
-
If the custom segment type is changed from multi-select to list/record, data can be lost.
If the Allow GL Custom Segment Deletion preference is enabled, an update to a bundle can delete a custom segment. If the Allow GL Custom Segment Deletion preference is not enabled, an error appears when you attempt to update a bundle containing a deleted custom segment.
You should avoid deleting custom segments using the bundle update. The best practice is to inactivate any custom segments that are no longer needed.
For more information about custom segments, see Custom Segments.