Error: Failure Message: "System.DmlException: Insert failed. First exception on row 407; first error: INACTIVE_OWNER_OR_USER, operation performed with inactive user: []",
Hi all,
We have a really weird situation. Sounds like this may be a Salesforce bug that was introduced recently. What we had working perfectly before (last 2 months), is failing as of this evening.
Background:
Created a change set in production this morning. Validated successfully. When trying to deploy the change set this evening, we get:
Failure Message: "System.DmlException: Insert failed. First exception on row 407; first error: INACTIVE_OWNER_OR_USER, operation performed with inactive user: []",
The line of code that is throwing the error is a inserting a custom object. The owner of the custom object may be an inactive user. From everything I have read, that is allowed.
Also, this used to run just fine before and the exact same code is throwing the exception.
This is only happening when the code is called from a Test Method (v24).
Any ideas what could the cause? Has something changed around how Salesforce enforces inactive users?
Error: Failure Message: "System.DmlException: Insert failed. First exception on row 407; first error: INACTIVE_OWNER_OR_USER, operation performed with inactive user: []",
Hi all,
We have a really weird situation. Sounds like this may be a Salesforce bug that was introduced recently. What we had working perfectly before (last 2 months), is failing as of this evening.
Background:
Created a change set in production this morning. Validated successfully. When trying to deploy the change set this evening, we get:
Failure Message: "System.DmlException: Insert failed. First exception on row 407; first error: INACTIVE_OWNER_OR_USER, operation performed with inactive user: []",
The line of code that is throwing the error is a inserting a custom object. The owner of the custom object may be an inactive user. From everything I have read, that is allowed.
Also, this used to run just fine before and the exact same code is throwing the exception.
This is only happening when the code is called from a Test Method (v24).
Any ideas what could the cause? Has something changed around how Salesforce enforces inactive users?
