Name Conflict Configuration

Overview

Custom objects and fields whose names match managed package components will behave correctly in all ERX Core functions. For example, in previous releases, a custom field on the Application object named Applicant_Type__c would conflict with the managed package field named EnrollmentrxRx__Applicant_Type__c and Super Clone would fail when trying to clone these fields.

As of the Winter '21 release, custom objects and fields whose names match managed package components will behave correctly in all ERX Core functions by selecting the Configure Name Conflict button. This will initiate ERX Core to configure itself automatically to handle the naming conflict.

In releases prior to Winter ‘21, functionality such as Super Clone or the configuration of a custom requirement item object (RIO) would fail if a custom object name or a custom field name matched the names of existing managed package objects or fields.

For example, if a custom field on the Application object were created named Applicant_Type__c, this would conflict with the managed package field named EnrollmentrxRx__Applicant_Type__c and Super Clone would fail when trying to clone these fields.