Constituent Manager export files use a column header format of [service]_[feed] to identify the origin of each data field across multiple databases. For example, "FinalsiteOpen_StudentDates" means FinalsiteOpen is the service and StudentDates is the feed that brought the data in.
💡Quick answers
- What does the column header format in export files indicate? The service (data source) and the feed (specific data pipeline) that brought that field into the Finalsite database, separated by an underscore.
- What does a column named "FinalsiteOpen_StudentDates" mean? FinalsiteOpen is the service where that data is stored, and StudentDates is the feed that brought it into the Finalsite database.
- Why does Constituent Manager use this naming convention? To clearly identify which data source each field comes from when constituent data is stored across multiple databases or integrations.
Finalsite normalizes importIDs across data sources - meaning that constituent data can be accessed even when it's stored in multiple databases. To ensure that it remains clear which source/feed contains individual data fields, data export column headers follow the format: ["service"]_["feed"].
A column named "FinalsiteOpen_StudentDates" means that FinalsiteOpen is the service where that data is stored, and StudentDates is the feed that brought it into the Finalsite database.
Comments
Please Sign in to leave a comment if you don't see the comment box below.