Currently, Anaplan retains the original email ID case format (uppercase/lowercase) based on how it was first created in the system. Even if a user is deleted and re-created with the same email address in a different case format, Anaplan continues to enforce the originally stored casing.
For example:
- Initial creation:
abc.de@cognizant.com - Re-created as:
Abc.De@cognizant.com - Result: System still stores and returns
abc.de@cognizant.com
This behavior creates challenges in downstream integrations where email IDs are compared with external systems (such as Prism) that perform case-sensitive comparisons. As a result, mismatches occur despite the email logically being the same, leading to mapping inconsistencies, failed joins, and additional data transformation overhead.
Requested Enhancement
We propose one (or more) of the following improvements:
- Support case-insensitive text comparisons within Anaplan.
- Allow resetting or overriding stored email casing when a user is re-created.
