After our primary supplier upgraded their quality management system, XML imports for non-conformance records are failing with schema validation errors. The integration worked perfectly for 14 months before their system upgrade.
We receive automated XML files daily with supplier non-conformance data, but Trackwise is rejecting them during import:
Schema validation failed: Element 'SupplierNCR' not allowed
Expected: NonConformanceRecord
Line 12, Column 5
The supplier claims their XML structure hasn’t changed, but clearly something is different. I’ve compared the old and new XML files, and the root element name has changed from ‘NonConformanceRecord’ to ‘SupplierNCR’. We need to update either our XSD schema or the import mapping to handle this change.
Good advice. I’ve requested complete documentation from the supplier. In the meantime, I’m reviewing the current schema definition. What’s the best approach for making the schema flexible enough to handle both formats in case they send files from their old system occasionally?
The XSD schema is typically stored in the Trackwise integration configuration under Admin > Data Import > XML Import Definitions. You’ll need to edit the schema to accommodate the new element name. You might also need to update the field mapping if the internal structure of the XML changed beyond just the root element name.
The supplier won’t change their format back - it’s a vendor system upgrade affecting multiple customers. I need to update our schema. Where is the XSD schema definition stored in Trackwise for XML imports? Is it in the import configuration or a separate file?