Territory management data quality validation rules fail to trigger during bulk import operations

betty_pro
Thu, 08 May 2025 08:42:00 +0000

We’ve configured comprehensive data quality validation rules for our territory management module to prevent invalid territory assignments, but these rules aren’t being enforced during bulk import operations via REST API. When we manually create or update territory records through the UI, validation works perfectly - invalid postal codes are rejected, overlapping territories are flagged, and required fields are enforced.

However, when importing territories through our integration:

POST /crmRestApi/resources/11.13.18.05/territories
Validation: Bypassed
Records Imported: 1,247
Invalid Records: ~340 (estimated)

The bulk import succeeds but creates invalid territory data that violates our quality rules. Our REST API configuration should be triggering the same validation as the UI, and our error handling is set up to reject invalid records. This is causing data integrity issues with territory assignments and impacting sales routing. Why would validation rules work in the UI but not through the API import process?