This error is not caused by Apsona. It originates from Salesforce Duplicate Rules. Even if Apsona’s import wizard is set to “Add no checking,” Salesforce can still block record creation when its Duplicate Rules detect potential matches. Apsona simply passes Salesforce’s error message back to the user and cannot override Salesforce’s data integrity enforcement.
Salesforce Duplicate Rules were configured with an action of “Block” when potential duplicates are detected. This prevented new Account records from being created, even though Apsona’s duplicate checking was disabled.
The customer was advised to update Salesforce Duplicate Rules by either:
Temporarily deactivating the specific rule causing the block, or
Changing the rule action from “Block” to “Allow” (so records are flagged as potential duplicates but still created).
These changes must be made directly in Salesforce by an Administrator. Apsona settings were already correctly configured, When record creation fails with duplicate errors, always check Salesforce Duplicate Rules first. Apsona’s “Add no checking” bypasses only Apsona logic—it does not bypass Salesforce enforcement.