#Salesforce221 人がディスカッション中

Hello @Nancy Magalhaes have you had a look at materials suggested in the Admin certification guide ?

• Trailmix: Prepare for Your Salesforce Platform Administrator Certification
• Superbadge: Object Relationships
• Superbadge: Flow Administration

 To test your knowledge

• https://www.salesforceben.com/salesforce-admin-practice-exam/ (free)
• https://www.udemy.com/course/salesforce-admin-certification-adm-201-6-practice-tests/ (paid)

Eric

Hi @M Anjil Reddy Good question! Profiles provide baseline user access, Permission Sets grant additional permissions, and Permission Set Groups combine multiple permission sets for easier access management.

If a user cannot access an object or field, I would check:

1. Profile: Verify the user's assigned profile.
2. Object Permissions: Check Read, Create, Edit, and Delete access.
3. Permission Sets: Verify assigned permissions.
4. Permission Set Groups: Check group assignments and muting permissions.
5. Field-Level Security: Confirm field Read/Edit access.
6. Record Access: Check OWD, sharing rules, and role hierarchy if the object is accessible but records are not.

My suggestion: Use the User Access Summary to identify effective permissions before making changes.

📘 Salesforce Security Guide – Trailhead

Hope this helps!

Hi @Rakesh Goud You can use an After-Save Record-Triggered Flow to automatically update related records when an Account's Industry changes.

Steps:

1. Go to Setup → Flows → New Flow → Record-Triggered Flow.
2. Select Account as the object.
3. Trigger the Flow when a record is updated.
4. Select After Save because we need to update related records.
5. Add a Decision element to check whether the Industry has changed.
6. Use Update Records to update the related records, such as Contacts, based on the Account Id.
7. Save, debug, and activate the Flow.

How to prevent recursion and unnecessary updates:

• Use ISCHANGED(Industry) to run the Flow only when Industry changes.
• Set the entry criteria to run only when the record meets the required conditions.
• Update only related records that actually need changes.
• Avoid updating the same Account again unless required.
• Check whether any other Flows or Apex Triggers could update the Account again.
• Use one Update Records element for matching records instead of updating records individually in a loop.

Real-Time Example:

If an Account's Industry changes from Banking to Healthcare, the Flow can automatically update a custom Industry field on all related Contacts.

Useful Salesforce Documentation:

• Record-Triggered Flows – Trailhead
• Flow Builder – Salesforce Help
• Flow Best Practices – Salesforce Architects

My suggestion: Use an After-Save Flow with change detection and filtered updates. This helps avoid unnecessary execution and reduces the risk of recursion.

Hope this helps!

Use {{ ref('Account','Id') }} instead of the Trailhead-recommended approach, which was causing an issue. I used this alternative, and it successfully resolved the error. 

Below the generated JSON.  

Hi @SAITEJA B Good question! In real Salesforce projects, security should follow the Principle of Least Privilege, meaning users should access only the data required for their jobs.

1. Recommended Security Model

1. Profiles: Assign minimum permissions based on user responsibilities.
2. Permission Sets: Provide additional object, field, and system permissions based on department needs.
3. OWD: Set sensitive objects to Private by default.
4. Role Hierarchy: Allow managers to access their team's records where required.
5. Sharing Rules: Share selected records between departments based on business requirements.
6. Field-Level Security: Restrict confidential fields such as Salary, Revenue, and Customer Financial Details.

2. Department-Wise Example

• Sales Team: Access Leads, Accounts, Contacts, and Opportunities.
• Marketing Team: Access Campaigns and required Lead information.
• Support Team: Access Cases and relevant customer information.

3. Important Best Practices

• Use Permission Set Groups for department-specific access.
• Avoid unnecessary View All and Modify All permissions.
• Use Sharing Rules to provide additional record access.
• Test access using different user accounts.
• Review permissions regularly.

4. Official Salesforce Resources

• Salesforce Data Security
• Control Access to Objects
• Control Access to Fields
• Control Access to Records

Create three test users representing Sales, Marketing, and Support. Configure OWD, Permission Sets, Roles, and Sharing Rules, then verify what each user can access.

Key Point:

Start with minimum access and provide additional permissions only when required. 

Hope this helps! Venkat Yadav | SFDCINDIA