Define Report Columns
Report columns are the fields Engage keeps for each execution record. Every event the integration reports is mapped onto these same columns, and every view is a selection of them, so the column list is the foundation the rest of the configuration stands on.
Before you begin
- The integration's Configure form is open. See Configure an integration.
What Engage seeds for you
When the form opens, Engage reads every event schema in the manifest and creates one column per distinct field name across all of them. A field that appears in two events becomes one column. Each seeded column takes the field name as its DisplayName and a Type derived from the schema.
Because of this, N Columns added is rarely zero on a first visit, and the task is usually to check the seeded list rather than build one.
Open the column table
- In the Define report columns section, select Add columns.
The Define columns drawer opens, titled Edit Defined columns when a configuration already exists. It holds a table with four editable columns.
| Column | What to enter |
|---|---|
| FieldName | The identifier the mapping targets. Letters, digits, underscores, and hyphens; must start with a letter, underscore, or hyphen. |
| DisplayName | The heading shown in views. Cannot be empty and must be unique. |
| Type | String, Integer, Float, or Date |
| Description | Optional |
Add or change columns
- Select Add Column below the table to add a row.
- Enter the FieldName and DisplayName, and select a Type.
- To remove a column, select the delete control at the end of its row.
- Select Add, or Update when editing, to return to the form.
The button stays disabled while any row has an empty field name or display name, or while any row shows an error.
Limits
An integration can hold at most 70 columns, split by type:
| Type | Maximum |
|---|---|
| String | 30 |
| Integer | 15 |
| Float | 15 |
| Date | 10 |
Add Column is disabled once 70 is reached, and changing a column's type to one whose limit is full is refused with a message naming the limit.
Choosing what to keep
The seeded list is the union of every event, which is the right starting point but not always the right end point. Remove a column when nothing needs to filter, sort, or read it in Engage. Keep every field that identifies a record, because views need a key column and the mapping needs somewhere to put each event's identifying data.
Renaming a FieldName after events have been mapped leaves the existing mapping pointing at a name that no longer exists, so Map Fields has to be reopened and the column reconnected. Rename display names freely; rename field names before mapping.
How you know it worked
N Columns added in the form reflects the new count, and the column names appear as targets the next time you open Map Fields on any event.
When it does not work
| Symptom | Cause | What to do |
|---|---|---|
| Special Characters not allowed on a field name | The name contains a space or a character other than letters, digits, underscore, or hyphen, or starts with a digit | Use only permitted characters and start with a letter |
| Duplicate event name not allowed on a field name | Another row already has that field name | Choose a different field name |
| Display name cannot be empty | The display name was cleared | Enter a display name |
| Duplicate display name not allowed | Another row already has that display name | Choose a different display name |
| Maximum 70 columns allowed (30 String, 15 Int, 15 Float, 10 Date) | The total limit is reached | Remove a column before adding another |
| Maximum 30 String columns allowed, or the equivalent for another type | That type's limit is reached | Remove a column of that type, or choose a different type |