The ServiceMax package has a trigger on the user object that is running when we make updates to user records. We have a batch process that updates users in bulk and in some cases the ServiceMax package code throws an fatal exception of too many SOQL statements.
I cannot set what the ServiceMax code is doing, but in the attached log you can see that our code has executed 2 DML operations with a total of 3487 user records being updated. Even though we've done just two bulk DML operations the ServiceMax code is running 100+ queries.
The ServiceMax code needs to be corrected to stop consuming so many resources so customers don't run into this issue.
What is the underlying problem do you intend to solve with this idea?
error creates work delays and potentially lost data
How is the problem being addressed today, if at all?