Thanks
Ryan
1 answer
So the essence of it is this - What the DropBox for Salesforce is probably doing is this - Once you update the User to "In - Active", the App[DropBox for Salesforce] is updating one of their records(belonging to their Custom Object) and also they're trying to update the "DI Auth" field on the User object too(probably an effort from the DropBox side to empty out the DI Auth field since the User is no longer Active).
So in one transaction there is an update on Custom Object also there is an update on the User object(which is basically a Setup/Configuration object). Thus this is mixed operation and Salesforce doesn't allow this.
Since this is coming from the vendor's Trigger, the only way out is to get in contact with the vendor and let them know of the same. Only then would they be able to fix it on their side and give you a patch / update to fix the same.
As an alternative(quicker solution), you can try the Freeze option so as to stop the User from logging in for now or the hard way is to inactive the Trigger(which is not recommended and going to be tedious).
