Universal Containers, a global corporation of 50,000 users, has a 24x7 call center operated by 20,000 users that includes employees and contractors. Their sales organization is 10,000 strong and they started processing about 100,000 updates to opportunity custom fields called Priority and NextStep. They also started processing 20,000 updates to a highly nested territory hierarchy. There was a third mass update on a Next Step field on the Action Plan custom object that has Case as a lookup field. Users started seeing a Group membership lock error in the system. What is a probable cause for this error?

Question

Simone Perego · Accepted Answer

Lock contention due to system-initiated sharing rule recalculation

Simone Perego · Answer

Lock contention on Case records because of Action Plan custom object updates.

Simone Perego · Answer

Lock contention on Territory object because of Territory object updates.

Simone Perego · Answer

Lock contention on Account records because of Opportunity object updates.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 134 - Certified Sharing and Visibility Architect discussion

Suggested answer: A

0 comments