For GiveCampus constituent data and imports.
Do not deduplicate imported gifts by constituent/date/amount alone. Identity is determined by the import configuration's unique fields and parent constituent; the no-configuration fallback uses transaction ID together with the constituent identity. Review existing rules before changing to a composite ID. Missing Gift Deletion controls whether omitted imported gifts are removed and defaults to false; a full-file upload is not inherently a delete instruction. A CRM copy of a native GiveCampus gift is not automatically reconciled merely by matching date/amount. The standard mapping does not confirm a universal GiveCampus Gift ID column. Have the implementation team validate round-trip mapping and rolling-history effects with sample records before relying on them.
Comments
0 comments
Please sign in to leave a comment.