Bulk Import on Snowflake-Backed Objects
To bulk import on an object that is based on a Snowflake table, Elementum must be granted the correct permissions to create and update records in Snowflake. If these permissions are missing, the import will continue to fail silently — no error is displayed in Elementum.Verify Snowflake Permissions
Confirm that the Elementum service account has been granted
CREATE and UPDATE privileges on the target Snowflake table.Resolving “String is too long and would be truncated” Errors
When writing to a Snowflake-backed object, you may see an error like:Identify the Column and Value
Note the column name and the specific value referenced in the error message. These tell you exactly which field is too long.
Locate the Source of the Value
Trace the value back to its source — for example, the record being imported, the field mapping in your automation, or the upstream Data Mine query.
Shorten or Remove the Value
Update the source data so the value fits within the column’s character limit, then retry the operation. For automations, review the field mapping to confirm the source field’s values stay within the expected length.
Confirm or Increase the Column Length
If shortening the value is not an option, reach out to a database administrator with access to The same administrator can typically increase the column length in Snowflake if a larger limit is required.
information_schema.columns and ask them to confirm the column’s defined maximum length: