After adding MID server profile to the MID server there appears to be logic in the system that adds settings from the profile to the MID but it can lead to duplicates - Known Error

After adding MID server profile to the MID server there appears to be logic in the system that adds settings from the profile to the MID but it can lead to duplicates Description After adding the MID server profile to the MID server there appears to be logic in the system that adds settings from the profile to the MID but it can lead to duplicates

Steps to Reproduce

1. Please go to instance mid servers 2. Please personalize your list view so that you have the Profile ID in the list 3. If there is a value in that field, please clear the field 4. Please update the Profile ID field with the value as required. 5. Then open the MID server record and notice that some settings are duplicated such as IP ranges or clusters especially look at the related lists called "IP Ranges" and "Included in Clusters"

Workaround Profile ID is not meant to be changed manually. It's designed for containerized mid-servers only. Hence the configurations are not deleted when the profile is removed manually.

To remove the duplicates you can go to the profile and use the 'Sync to MID servers' link to sync the configurations.

Note: this will affect all the MID Servers which have the profile linked.

To address the duplicate records getting created, we need to make small changes in the MIDConfigurationUtil script include and The defect has been fixed in Vancouver.