Multiple constituent codes as native affiliations

For GiveCampus constituent data and imports.

Use native Constituents – Affiliations records for multiple constituent codes such as Alumni, Parent and Trustee; one person can have multiple affiliation values. Map each affiliation name (and its value such as a class year when applicable) to the same stable constituent ID using the configured import’s repeated affiliation record mapping. Do not concatenate Alumni;Parent into one value unless the import is explicitly configured to split it: the standard helper treats its supplied name/value as one affiliation. Numbered arbitrary custom fields are not required merely because a person has several affiliations. Confirm the file layout and mappings in the import preview before applying.