Non-intake fields ignored merge preferences

When you processed E2B R3+ follow-up data, fields not included in the Intake form did not follow your configured merge preferences. The system always used the default merge behavior, which could keep outdated information or prevent expected updates during case processing. (39088218)

Before

When you imported follow-up data for E2B R3+ cases, fields that were not available in the Intake form always used the system’s default merge behavior. Configured merge preferences, including Force Update, were ignored for these fields. Because of this, existing case information could remain unchanged even when incoming follow-up data was intended to replace or remove it. In some situations, outdated reporter details or duplicate records were retained after follow-up processing. This behavior made case updates inconsistent and required you to manually review and correct merged case information before completing case processing activities.

After

The application now applies configured merge preferences to E2B R3+ fields, even when those fields are not included in the Intake form. When you process follow-up data, the system correctly applies the selected merge option so existing case information is updated, retained, or removed according to your configured rules.

Impacted Areas

Intake processing