UC is preparing to implement sales cloud and would like to its users to have read only access to an account record if they have access to its child opportunity record. How would a data architect implement this sharing requirement between objects?
Option D? Really? Creating an owner-based sharing rule for this scenario sounds like overkill. Let's not make things more complicated than they need to be.
As a data architect, I'd go with option A. Criteria-based sharing rules give you more control and flexibility to handle complex requirements. Plus, it keeps the logic centralized.
Hmm, I'm torn between A and C. Criteria-based sharing rules could be more flexible, but adding users to the account team is simpler. Decisions, decisions...
Hmm, I'm torn between A and C. Criteria-based sharing rules could be more flexible, but adding users to the account team is simpler. Decisions, decisions...
Option B sounds like a convenient solution, but I'm not sure if implicit sharing will really handle this requirement. Better to be safe and go with a more explicit approach.
Option B sounds like a convenient solution, but I'm not sure if implicit sharing will really handle this requirement. Better to be safe and go with a more explicit approach.
Pamella
2 months agoJenelle
28 days agoCharlesetta
1 months agoTrinidad
2 months agoRoy
2 months agoMichael
17 days agoRosendo
19 days agoCarissa
20 days agoMerissa
28 days agoFrancine
1 months agoNieves
1 months agoAlonso
1 months agoJulio
3 months agoGalen
3 months agoLeonardo
1 months agoChantay
2 months agoRyan
2 months agoTyra
3 months agoRusty
3 months agoTesha
3 months agoRupert
2 months agoLelia
2 months agoBrittani
2 months agoJoesph
3 months ago