YES, we can change segmentation object, but there should not exist any segmentation model saved and available for the relevant segmentation profile. In case we try to open an old segmentation model then we will get error as shown below.
An alternative to this as per the standard would be to create new segmentation profile for the new segmentation object. Now, for such cases, typical challenge would be the effort require in providing authorization to all the business users. For big organization of multi-brand scenarios, providing authorization to all the brands would be complex and time-consuming activity.
If the new requirement is capable to accommodate all the attributes of old segmentation object, then we have an alternate approach to do this change without even creating new segmentation object and profile. We can call this a downward compatibility approach 🙂
Solution is to change the Data source of the segmentation object 🙂
As we change the data source, we will be prompted with the below screenshot. Additional, Changed & Missing attributes count will display to confirm while changing the existing data source of the segmentation model as shown below.
Ensure no segmentation models are available that have models with ‘MISSING ATTRIBUTES’. Here in above screenshot we have six attributes of such case.
If we remove fields from Segmentation attribute list but available in data source level, then existing segmentation model will still work by showing the missing attribute as part of separate Attribute group called as ‘REQUIRED ATTRIBUTES’. Below screenshot is that of an old segmentation model which is still showing the missing attribute under REQUIRED ATTRIBUTES.
However, I would recommend going with the standard approach of creating separate Segmentation Object and Segmentation Profile. Later we can deprecate the old segmentation profile so that existing segmentation models will still work.
Hope this info helps you all !!!