Overview
Over time, workspaces may accumulate multiple metadata fields that represent the same concept. For example, you may have fields like:
Contract Value
Total Contract Value
ContractValue (without a space)
Even though these fields mean the same thing, they may be used inconsistently across contracts. Values may also come from different sources—intake forms, integrations, or SDC. This leads to duplicate columns in the repository and multiple filters for the same concept, making it hard, in this example, to filter all the contracts under a specific contract value.
The Merge Metadata Fields feature helps you consolidate these duplicates into a single, reliable field used across all contracts.
Why Merging Is Needed
When multiple fields capture the same information:
Different contracts may use different fields.
Reporting becomes unreliable because the same data is spread across multiple columns.
Downstream workflows and integrations may depend on inconsistent metadata.
Merging solves this by:
Combining duplicate fields into a single field.
Ensuring all past and future data points use one unified field.
Cleaning up the repository so only the correct field remains visible.
How to Merge Metadata Fields
Step 1: Navigate to Metadata Manager
Go to Settings
Open Manage Metadata
Click Metadata Manager
You’ll see a new button called Merge Metadata Fields
Step 2: Select Duplicate Fields
On the merge screen:
Left side: Select all the fields you consider duplicates.
You don’t need to select everything—only the fields that should be merged.
Right side: Select the field you want to merge into.
The fields on the left will be merged into the field selected on the right.
Step 3: Run the Merge
Click Merge.
The merge process will begin in the background.
You can check progress using the Check all merge statuses button.
Once complete:
The merged fields disappear from the repository.
Only the merged field remains.
What Happens After a Merge
Several important updates happen automatically:
1. Repository Cleanup
Duplicate columns are removed. All values now live in the merged field.
2. Intake Form Updates
If any of the merged fields were connected to intake forms across multiple workflows, all those links are moved to the merged field.
3. Template Placeholder Updates
If the duplicate fields were referenced in templates, their IDs continue to work.
The system maps everything to the merge field behind the scenes.
4. Integration Continuity
No integration changes are required.
All incoming data routes to the merge field after the merge.
5. Merged Field ID
After the merge:
The merged field’s ID becomes the canonical ID.
Any new feature, workflow, or integration should use this ID going forward.
Limitations
Cross-Type Merging Is Not Supported
You cannot merge fields of different data types.
Example:
Contract Value (Currency)
Contract Value (Short Answer)
These cannot be merged because the system cannot reconcile the data automatically. For example, a short-answer value like “Ten Thousand Dollars” cannot be reliably converted into a proper currency field.