Best Practices for Implementing Salesforce CRM - Cloud Experts

Using data access design patternsTM functional considerationsOnce you enable TM it can’t be disabled, so evaluate the following features before proceeding:FeatureDynamic account-to-territory assignmentsExplicit account-to-territory assignmentUser-to-territory assignmentsA user can be assigned to >1 territoryA territory can have >1 userTerritory hierarchy granularityRole hierarchy vs. territory hierarchyAccount ownershipInheritance of opportunitiesRe-alignment modeling and “what-if” analysisAPI accessThis means that….Drive re-alignments and new record assignments using declarativebusiness rules, not code.If you use “named accounts” ownership or have ownership ruleexceptions, you can use TM to directly assign accounts to users viaeach user’s association with a territory.Assignments are explicitly declared in the TM system.You can implement pods, overlays, and temporary territorycoverage functions.You can implement pods and shared territories.The hierarchy is an exact re-creation of your sales organization.If you implement TM, your territory hierarchy governs your defaultrecord access in a private sharing model, which means you cansimplify your role hierarchy with fewer roles.But territory management doesn’t supersede the role hierarchy. Themost permissive setting wins.Account ownership doesn’t have the same significance because TMdetermines default record access in a private sharing model. Mostcustomers revert ownership to a single default record owner in thiscase.In some cases, opportunities automatically inherit the territory valueassigned to the account.You cannot define more than one territory alignment, butassignments can be tested using the “Preview Account Assignment”function in sandbox.Territories are exposed to the API, so you can load territories froma .csv file. Additional API functions are included in Help &Training.Lastly, because of the scope of this functionality and its impact on record access, we highly recommendthat you consult with a TM expert from an implementation partner before proceeding.Summary: Best practices for designing your data access modelBecause the record access model is so important, plan to spend sufficient time on analysis and design.Below are several recommendations and best practices, gleaned from the most complex implementations.• Define your business requirements – Every complex implementation has complex requirements.Create a list of the most important business needs, written as business requirements, as shown in theexamples below.BEST PRACTICE 8