We observed two different data keys between the migrated policy and the regular (Jurisdictional) policy:
haveYouReceivedACopyOfTheCustomerSPatriotActCertification
haveYouReceivedACopyOfTheCustomersPatriotActCertification
The second policy is currently in scope within the journey.
Although the two keys appear nearly identical, they are technically different because the first key contains an uppercase “S” in CustomerS, making the entity datastore treat them as separate properties.
Are These Treated as Separate Fields?
Yes. These are treated as two separate fields:
haveYouReceivedACopyOfTheCustomerSPatriotActCertification
haveYouReceivedACopyOfTheCustomersPatriotActCertification
The entity datastore is case-sensitive, meaning even minor case differences within a datakey result in distinct entity properties.
Why Does the Audit Display Only One Field While APIs Show Both?
The difference in behavior is due to how each surface resolves and presents the field information.
Audit Log Behavior
The audit log displays fields using the human-readable UI label configured in the policy rather than the raw datakey itself.
Since both fields share nearly identical display labels (for example:
“Have you received a copy of the Customer's Patriot Act Certification?”), the audit drawer renders them as a single visible row. The underlying datakey difference is effectively masked at the presentation layer.
Entity Draft and Verified Data API Behavior
The Entity Draft and Verified Data APIs return the entity’s raw stored properties.
Because both datakeys exist independently at the storage level, the APIs correctly return both fields separately in the response payload.
This is expected behavior.
Will These Fields Overwrite Each Other?
No. Since the datakeys are distinct, neither field will overwrite the other.
The currently active journey, which uses the jurisdictional policy, reads from and writes to:
haveYouReceivedACopyOfTheCustomersPatriotActCertification
(lowercase “s”)
The legacy migrated value stored under:
haveYouReceivedACopyOfTheCustomerSPatriotActCertification
(uppercase “S”)
remains visible in API responses but is not surfaced within any in-scope journey task.