We’re experiencing issues with the supplier import utility in MC 2022.1 when trying to bulk upload 150+ supplier records. The import fails around record 47-52 with a generic validation error that doesn’t specify which field is causing the problem.
Our CSV includes standard fields plus three custom attributes (Certification_Level, Risk_Score, Preferred_Status). When we import suppliers individually through the UI, they work fine, but the bulk utility keeps failing. The error log shows:
Validation failed for record 49
Error code: SUPP_IMPORT_VAL_001
Details: Custom attribute mapping error
The documentation mentions field-level validation but doesn’t explain how to troubleshoot bulk import failures with custom attributes. Has anyone successfully configured bulk supplier imports with custom fields? We need to onboard these suppliers by month-end for an upcoming audit.
Thanks for the tip. I verified the CSV is UTF-8 encoded and checked our custom attribute names. They match what I see in the admin console: Certification_Level, Risk_Score, Preferred_Status. Still getting the same error at record 49. Is there a way to enable more detailed logging for the import utility to see exactly which validation rule is failing?
I’ve seen this before. The bulk import utility in 2022.1 has stricter validation than the UI form. Check your CSV encoding first - it needs to be UTF-8 without BOM. Also, custom attribute column headers must match the exact API names, not display names. Try exporting a sample supplier with your custom fields to see the correct format.
Restart the service and retry the import. The detailed log should show which specific field and validation rule failed. Also check if your custom attributes have any conditional validation rules that might not be obvious - sometimes Risk_Score fields have numeric range validators that aren’t documented well.
Sara, that was exactly it! The Preferred_Status field had allowed values of ‘Yes’ and ‘No’ but our CSV had ‘yes’ and ‘no’ in lowercase. After fixing the capitalization, the import still failed because Risk_Score was expecting integers but we had decimal values. Fixed both issues and now stuck at a different error related to date formatting in one of the standard fields.