Loading

Salesforce API: INACTIVE_OWNER_OR_USER Error When Assigning a Task to an Inactive User

Дата публикации: Jun 9, 2026
Описание

When using the Salesforce API to assign a Task record to an inactive user, most Salesforce organizations return the error: "INACTIVE_OWNER_OR_USER, operation performed with inactive user." However, in some organizations, the same API operation completes successfully without error. This inconsistency occurs because of a specific org-level permission called "Create Audit Fields."

Решение

Root Cause: Create Audit Fields Permission

The "Create Audit Fields" permission (also known as the "Allow setting of audit fields such as Created By, Created Date, Last Modified By, Last Modified Date via API" permission) allows the API to set system audit fields on records. When this permission is enabled at the org level, Salesforce relaxes enforcement of the INACTIVE_OWNER_OR_USER validation, allowing assignment to inactive users via API. When the permission is disabled (the default state for most orgs), Salesforce enforces the validation and returns the INACTIVE_OWNER_OR_USER error.

How to Check and Enable the Permission

To view or enable the Create Audit Fields permission, contact Salesforce Support to request it be enabled, or refer to the Salesforce Help article linked in Additional Resources for the enablement process.
Note: Assigning records to inactive users via the Salesforce API is only supported through API calls — this cannot be done through the Salesforce user interface.


Дополнительные ресурсы

Enable the 'Create Audit Fields' Permission in Salesforce

Номер статьи базы знаний

000386481

 
Загрузка
Salesforce Help | Article