Gift IDs are not constituent IDs for Smart Ask imports

For GiveCampus constituent data and imports.

Keep the constituent identifier and gift transaction identifier in separate mapped fields. The default imported-gift identity combines a transaction ID with the constituent identifier. Replacing the constituent identifier with a gift or system-record ID can change matching; have the import mapping reviewed before another upload when this has already occurred. Smart Ask’s requirements panel asks for constituent identity/contact data and giving history with gift ID, gift type, amount, and payment date, including recent gifts. An exported target-gift range alone does not replace that giving history. Use the actual provided templates and data-requirements status. Whether a school’s NXT connector has supplied the required gift records depends on its enabled import and run history. A field described only as Fiscal Year Giving needs its exact mapping/definition and school fiscal-year boundary before choosing which year’s value belongs there.