Skip to main content

#Best Practice0 discussing

I'm on a project that's at the beginning stages of building an Org that will ultimately have a large number of users whose access rights will vary greatly by user function/role.  

 

The current design is to use only 1 or 2 Profiles, and manage all of the access needs via Permission Sets and Public Groups.  Is this a recommended approach?  

 

My concern is that certain features which are dependent on Profiles - like Field-Level Security, Record Types, etc - don't support using Perm Sets and Pub Groups.  

 

Is there a best practice for determining how many Profiles an org needs, out of the gates, versus Perm Sets and Public Groups?    (FYI, the current design is to not use the OOTB Role Hierarchy either...in case that impacts this decision)  

 

Thanks, in advance!

 

#Best Practices  #Object Access  #Profiles  #Profile  #Best Practice  #Best Practices Advice  #Permission Set  #Service Cloud

4 answers
  1. Jul 10, 2025, 1:42 AM
    What did you ultimately decide? I’m in the same situation. Very customized record types I don’t need others to see. It’s just clutter in their view.
0/9000

Any idea how to calculate the cyclometric complexity of any apex class without control flow graph in Salesforce? and how this issues will be resolved---There are high number of independent paths through the block of code

 

#Apex Class #Best Practice

0/9000

This topic is formatted as a question.  Topics are not meant to be used as a format for asking a single question. Think of them as categories that you can apply to questions to identify the subject matter of the question.  The topic feed is a "container" for multiple posts and questions that are related to the same subject matter.  #Best Practice

0/9000
Basically what the title says. We are starting from the ground floor with NPSP and are looking for some soft credit setups that have worked for other organizations out there. Thanks in advance.
3 answers
0/9000

I am tasked with applying a large number of data fixes to our new salesforce system. Apparently the best practice is to only do data fixes through an outage window because automations such as triggers, handlers, flows, workflows, validation rules, integrations and other automations, may fire causing unwanted results and slowing the load execution time. We cannot afford the outage time. I've heard it suggested that it is possible to turn off automations on a per user basis which would allow the datafix user account to have automations turned off while other users continue i.e. no outage. This feature would need to encompass all automations else a general outage would still be needed. 

 

In the interim I am doing automation impact assessments to determine the data fixes that will not require an outage. No-outage data fixes are rare however!

 

Can the forum point me a better way to achieve low to no user impact and high data fix throughput?

1 comment
  1. Jun 10, 2021, 10:50 AM

    Colin,

    Can I ask how you are uploading the “fixed” data back into Salesforce? If you are using

    Dataloader.io to insert data back in and you leave the default 200 records per batch that is where you may not get your expected results. As with all of the automations Salesforce allows us to do will fail. But on most upload tools like Dataloader.io

    you can set how many records get updated/inserted. Yes if you choose 5 records per batch and you have a million rows, this will take some time, but no outage. This can also be ran during busniess hours as this wouldn’t have a huge impact on the system, butI would recommend running after hours, not saying I haven’t had to run a mass data “fix” during buisness hours before.

    Secondonly, this recommendation is something you can eventually add in or add just into some of the big automations you currently have. On the user object you would add a checkbox named “Skip Automation”. Then add a decision conditon at the beggining of all flows, validation rules, process builders that checks the checkbox on the user record to Skip that automation or continue. If that checkbox is true the don’t run the automation, if false continue like normal. When we are all first starting we don’t think of doing this, but I highly recommend doing this as eventually we all run into situations like this. We can update our user or another user with this checkbox = true and then when we do a mass upload of data Salesforce won’t run all of the automations. Don’t forget to uncheck the box when you are done with the data fix tho.

    Hope this helps let me know if you need any further assistance.

0/9000

Hey Guys!

 

I am wondering if any admin have best practices they use or follow for regression testing? We have a large Service group with many departments and have never had a formal process to follow for regression testing. I am looking to create a template to be used for consistency, but wanted to see if others have had similar issues with large companies. TIA for any tips or things to avoid!

 

#Regressiontesting #Bestpractice #Service #Fieldservice   

0/9000

Hi all. I have some questions regarding the clinical data model.

  • Care Plan: I understand that there is a difference between the EHR and the FHIR-aligned clinical data model - The former has a set of customized managed objects with EhrCarePlan__c being the one at the center of the Care Plan structure, while the latter leverages Cases with a Care Plan record type. If my understanding so far is correct, the question is: Should I use the former when I have data coming exclusively from integration with EHR, or should I consider as best practice that this is a legacy data model and all new implementations should follow the FHIR-aligned one?
  • Leads: What is the difference between a CandidatePatient__c record and a Lead record in the model?
  • Do you believe it's possible to use the clinical data model side by side with stock service and sales cloud in the same org provided that you properly map record types and processes (specially for cases, leads and tasks? Or would it be wiser to have them in separate orgs?

Any clarification will be deeply appreciated!

2 comments
0/9000

We have classified our Accounts as A, B, C or D, depending on how important they are to us. Our Contacts can have relationships with many Accounts.

 

For each Contact, I would like to calculate a rolled up A, B, C or D, based on all the Accounts that the Contact has a relationship with.

 

Does anyone have ideas on the best practice for achieving this, please?

0/9000

Hi all, 

 

Is there any recommendations of best practice for tracking reoccurring static blocks which feature in multiple emails across a range of different journey's/single sends?

 

Ideally we want to track back to which email/journey it has come from without having to go in and update links for each send as it's often a dynamic content block with 40+ different links behind so it's very time consuming to create individual links.

 

Thank you in advance for any help,

 

Sarah

1 comment
0/9000

Hello All,

I'm thinking of make the cases OWD public for my org, but I'm concerned about the cases for the community portal.

Does anyone have similar setup can advise what is the best practice?

Thanks 

2 comments
  1. Apr 27, 2021, 7:27 PM
    There is an internal OWD and an external OWD. The external OWD is what defines the default for community users. You likely want to keep the external OWD private and not share all cases with all users in the community, otherwise they'll be able to see each others' cases.
0/9000