How to Upload Person Address with Custom Address Type using HDL

This issue typically arises due to:

• Duplicate or missing Source Keys

• Non-unique SourceSystemOwner/SourceSystemId combinations

• Incorrect mapping of custom address types

Recommended Solution:

Update your HDL file so that each Person Address record uses a unique combination of SourceSystemOwner and SourceSystemId, especially when loading multiple addresses (e.g., Home, Mailing, Custom types) for the same person.

METADATA|PersonAddress|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PersonId(SourceSystemId)|AddressType|AddressLine1|AddressLine2|Building|FloorNumber|TownOrCity|Region1|Region2|Region3|Country|PostalCode|SourceRef001=ADDRESS_ID|PrimaryFlag
MERGE|PersonAddress|US_CUSTOM|ADDR001|2018/01/01|4712/12/31|WKR001|Home|123 Main St||||New York||NY||US|10001|ADDR_REF_001|Y
MERGE|PersonAddress|US_CUSTOM|ADDR002|2018/01/01|4712/12/31|WKR001|Mailing|456 Elm St||||Chicago||IL||US|60601|ADDR_REF_002|
MERGE|PersonAddress|US_CUSTOM|ADDR003|2018/01/01|4712/12/31|WKR001|Emergency|789 Pine Ave||||Dallas||TX||US|75201|ADDR_REF_003|

Key Tips:

• SourceSystemId must be unique per record.

• If using custom address types, ensure they are already defined in the application.

• Double-check PrimaryFlag values – only one address per person should be marked primary (Y).

• Avoid reusing SourceSystemId across different records to prevent mapping conflicts.

I hope this blog post was helpful for you. If you have any questions or feedback, please leave a comment below.