For GiveCampus constituent data and imports.
The legacy constituent-details panel displays separate cell, home and work phone fields. Importing only a preferred-phone value does not automatically populate all three. Confirm the actual profile interface and mapped field before treating a blank displayed phone as an import failure.
The custom-field model distinguishes single-valued List from Multi-select List, with separate storage and segment conditions for multiple selections. Confirm that the actual import/editor supports the intended type and mapping before loading multiple program values; a single list field does not automatically become multi-select because several rows contain different programs. These data fields are separate from donor form dropdown questions.
The profile's imported school Activities and a VMS cohort's Activity condition are different data contexts. Check the actual segmentation interface rather than assuming an identically named condition filters imported school activities. A reviewed custom field may be appropriate when the desired condition is unavailable. Missing affiliations still require inspection of the source rows, mapping and resulting person records.
Comments
0 comments
Please sign in to leave a comment.