If you're importing evidence using a CSV file via Evidence > Add Evidence > Create evidence placeholder from file (CSV) and ControlMap displays an error indicating that your file contains invalid Objective IDs, the Objective IDs in your file likely don't match the exact values stored in your ControlMap tenant.
Follow the steps below to identify and correct the issue.
Who can use this feature?
Compliance Manager and Super Admin users
Verify your Objective IDs
Objective IDs in your CSV file must exactly match the Requirement values displayed in ControlMap. To find the correct values:
Navigate to Frameworks > Objectives.
Locate the Requirement column.
Copy the Objective ID exactly as it appears, including any prefixes, punctuation, or spacing (for example, "Article 6.1" or "4.1").
Use these exact values in the Objective ID column of your CSV file. Don't shorten, modify, or reformat them.
Avoid using sample file values without validating
The sample CSV file provided during the import process contains placeholder Objective IDs. These may not match the Objective IDs configured in your tenant.
Before importing, compare every Objective ID in your file against the values in your tenant's Frameworks > Objectives > Requirement column to confirm they're valid.
Use the Objectives export as a reference
To make it easier to populate your CSV file with valid Objective IDs, generate the Objectives report from your tenant and use it as your source of truth:
Navigate to Frameworks and select your framework.
Go to Reports.
Generate the Objective Report.
Use the Requirement values from the report to populate the Objective ID column in your CSV file.
Account for framework-specific formatting
Different frameworks use different ID formats. Make sure your IDs follow the formatting conventions specific to your framework. For example, DORA and GDPR use full identifiers like "Article 6.1" — copy them exactly as shown in ControlMap, including the prefix.
Verify Control IDs (if applicable)
If your CSV file also includes a Control ID column and you're receiving errors related to it, confirm that the Control IDs exist in your tenant:
Navigate to Controls.
Check the Code column to verify the Control ID exists.
If the Control ID is missing, import the relevant control set before importing your evidence.
Note: ControlMap distinguishes between the Control ID and Objective ID columns during import. Identical values are differentiated by their column placement, so make sure your IDs are in the correct columns.
Any questions?
Reach out to our support team by submitting a ticket.
Related to
