So, I've written triggers to set the value of a case owner's department field based on the queue name or the user department. The triggers work just fine, including when I did a dataload to populate a different field. Post upsert extract showed that the upsert initiated the trigger, which populated that department field for 68k records.
Unfortunately, I'm having problems getting the test class to complete. It is returning a too many soql statements during a map statement that is before any processing loops.
The too many SOQL statements is occurring at the second map statement.
Trigger:
trigger Case_SetOwnerDept_Update on Case (before update) { // When 'Owner' field is changed, update 'Case Owner's Department' too Set <String> sUserIDs = new Set<String>(); Set <String> sQueueIDs = new Set<String>(); Set <String> sOwnerIDs = new Set<String>();
Map <String, User> mUsers = new Map<String,User>([Select ID, Department from User where ID in:sUserIDs]); Map <String, Group> mGroups = new Map<String,Group>([Select ID, Name From Group where type='Queue' and ID in :sQueueIDs]); Map<ID, Case> mCases = new Map<ID, Case>();
I can and have set up validation on the detail record that prevents it from saving if its master record is not at a particular status; however, I would prefer that the New button on the related list be either hidden or return an alert based on master record status.
Ex.
Projects - master with action items - detail
New Action item should not be created unless project is approved. I can prevent action item creation with object validation, but from a user perspective, it makes more sense if the button on the related list is hidden until project=approved, or if clicking New returns an alert that master status must be xxx.
Can this be done with custom button using formula?
