MIXED_DML_OPERATION about sfdx-batch-orchestrator

[dschibster]

Hi! Thanks for using Batch Orchestrator. :) First of all: is that a Batch Class that is processing Users? Usually, mixed DML can be handled by switching Context by designating a separate User to perform the Insert of Users, before / after the rest of the Objects is inserted.

[fentes]

Hey the (test) class is used to (de)activate users at a specific date, So the class itself is just performing DML on User object. But after that, the orchestrator is logging the results which led to the issue.
I assume that the logs are inserted synchronously after the job finished. It it somehow possible to inserting the logs by publishing an event (like nebula does)?

[dschibster]

Hah, I needed a second to recognize it's Georg! The Name I read in the Email was way less clear than the user name here :D Good to see you on here.
Yes, that can be done by using Enhanced Logging: https://dschibster.github.io/sfdx-batch-orchestrator/logging/
It's important to mark the Checkbox "Enhanced Logging" on the Batch Apex Job Record to true, too.

[gluch]

Hi there :)

Usually we would mark the "Enhanced Logging" checkbox, but this is a test class which is failing and it is pointing us to BatchJobLogger.cls (method: logLegacy).

According to Salesforce it is possible to isolate DML operations on different sObject with the @future annotation.
This prevents the mixed DML error at least on our Sandbox.

I wonder if this change does not screw up anything:

Again, with the above change our test class is working fine.

[dschibster]

I might enable this as a separate method in the future because I would need to test the full implications of it. But good to know. Thanks for the input and best wishes from Japan!