Jitterbit · Database connector (SQL Server)
Cannot insert explicit value for identity column
Short answer
This Jitterbit SQL Server error means the identity column is included in the INSERT the connector generates while IDENTITY_INSERT is OFF. To let SQL Server assign identity values, map the identity target field with Unmap.
VerifiedLast verified
01Error text
Database Error: Cannot insert explicit value for identity column in table '<table>' when IDENTITY_INSERT is set to OFF.02Likely causes
- The identity column is included in the INSERT the connector generates.
- Mapping the field to a null value does not exclude it. Only the Unmap function removes a target field from the INSERT.
03How to fix it
- To let SQL Server assign identity values, map the identity target field with Unmap.
- If you must insert explicit values, set IDENTITY_INSERT on the target table in the activity's pre- and post-SQL scripts.
04Official documentation
→Related errors
- Base64 decoding failedThis Jitterbit error in DBLookup or DBExecute means an agent earlier than 12.9 tried to Base64-decode a JDBC result that only looks like Base64, such as a JWT. For private agents, upgrade to version 12.9 or later.
- Database connection could not be established due to a security policy violationThis Jitterbit error means agent 12.10 or later blocked a database connection to a loopback address or one that uses a restricted connection string parameter. On the private agent, configure the [JdbcSecurity] section of jitterbit.conf to allow the specific connection or parameter.
- Field value too long / values were truncatedThis Jitterbit database error means a mapped source value is longer than the target column, and by default the value is rejected. In the activity configuration, enable Allow truncation of character fields.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries