Here’s the complete solution addressing all three aspects - UOM synchronization, custom UOM migration, and BOM import validation logic:
Step 1: Register Custom UOMs in Import Whitelist
Navigate to Administration > Import Configuration > UOM Validation Registry. In env-r2020x, this is separate from the main UOM catalog. Click ‘Add Custom UOM’ and register each of your custom units (EA_CUSTOM, BOX_50, ROLL_100M). Set validation mode to ‘Allow with Conversion Check’.
Step 2: Reconfigure UOM Conversion Matrix
Go to Administration > UOM Management > Conversion Matrix. The upgrade migrated your custom UOMs but didn’t preserve conversion relationships in the new schema format. For each custom UOM:
// Verify conversion factors are registered
UOMConversion conv = UOMHelper.getConversion("BOX_50", "EA");
if (conv == null) {
// Register conversion: 1 BOX_50 = 50 EA
UOMHelper.registerConversion("BOX_50", "EA", 50.0);
}
Repeat for all custom units with conversion dependencies.
Step 3: Update BOM Import Validation Schema
The BOM import validation logic changed significantly in env-r2020x. Update your import templates to reference the new schema version:
<BOMImport schemaVersion="2020x_v2.1">
<ValidationRules>
<UOMValidation mode="strict" allowCustom="true"/>
</ValidationRules>
</BOMImport>
Step 4: Clear Validation Cache
After configuration changes, the import validator maintains a cache that must be manually cleared. Execute this through the system management console:
wt.method.RemoteMethodServer.clearCache("BOMImportValidator")
wt.pom.DatastoreCache.invalidate("UOMRegistry")
Step 5: Test Import with Validation Logging
Enable detailed validation logging before retesting your BOM import. Add this to site.xconf:
<Property name="wt.bom.import.validation.logLevel" value="DEBUG"/>
This will show exactly which validation stage fails if issues persist.
Post-Migration Best Practice:
Create a UOM synchronization verification script that runs after upgrades. Check that all custom UOMs exist in both the catalog AND the import registry, with proper conversion factors. This prevents similar issues in future upgrades.
The root cause is that env-r2020x separated import validation from the general UOM catalog for data quality control, but the upgrade migration scripts don’t automatically populate the new import-specific registry. Manual reconfiguration is required for any custom UOM implementations.
Test with a small sample BOM file first (5-10 parts) before running your full supplier onboarding imports. The validation cache can take 10-15 minutes to fully refresh after configuration changes.
This draft is based on general ENOVIA knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.