#Salesforce토론 중인 항목 221개

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

Hi @SAITEJA B Good question! Record-Triggered Flows are a great way to automate business processes in Salesforce without writing Apex code.

1. Recommended Flow Design

Scenario: When an Opportunity moves to Closed Won, update the record, send an email, and create a follow-up Task.

1. Create Flow: Setup → Flows → New Flow → Record-Triggered Flow.
2. Select Object: Opportunity.
3. Entry Condition: Stage = Closed Won.
4. Trigger: When a record is created or updated.
5. Run Condition: Only when the record meets the entry conditions for the first time.
6. Update Record: Update required Opportunity fields.
7. Send Email: Use the Send Email action to notify the Opportunity Owner.
8. Create Task: Create a follow-up Task assigned to the Opportunity Owner.

2. Important Best Practices

• Use an After-Save Flow for creating Tasks and sending emails.
• Use a Before-Save Flow when only updating fields on the triggering record.
• Avoid unnecessary Get Records and Update Records inside loops.
• Prevent repeated execution using entry conditions.
• Add fault paths and test using Flow Debugger.

3. Official Salesforce Resources

• Record-Triggered Flows
• Flow Builder Basics
• Flow Builder Documentation

Build this automation in a Developer Org and test what happens when an Opportunity changes from Negotiation to Closed Won.

Key Point:

Use Record-Triggered Flows for business automation without Apex, but always focus on performance, error handling, and avoiding duplicate actions. 

Hope this helps! Venkat Yadav | SFDCINDIA

Hi @Vivek Dayafule You're welcome! I understand your concern. Since you've already completed the prerequisites, I don't think you need to repeat all the steps.

A few suggestions:

1. Org Compatibility: Confirm whether your Quick Start org supports Slack deployment.
2. Agent Activation: Your screenshot shows the Product Management Agent is active.
3. Slack Deployment: Check whether the agent is deployed to Slack, not just connected or authorized.
4. Email Difference: Since Salesforce Support contacted you about the email address, confirm whether user mapping is causing the issue.
5. Trailhead Support: Ask them to verify whether your org is correctly provisioned for this challenge.

 Since you've already tried the required steps, I would focus on Salesforce Support confirming the org's Slack deployment eligibility rather than repeating the setup. 

Hope this gets resolved soon! Venkat Yadav | SFDCINDIA

Hi @Sai Pavani Yamsani Good question! The best way to improve Apex coding skills is to combine Trailhead learning with real-time business scenarios.

1. Practical Apex Exercises

1. Apex Classes: Create a class to calculate discounts based on Opportunity Amount.
2. Triggers: Automatically update Account fields when related Contacts are created.
3. Collections: Practice List, Set, and Map using Account and Contact records.
4. Exception Handling: Use try-catch blocks to handle DML errors.
5. Governor Limits: Practice bulk processing of 200 records without SOQL or DML inside loops.
6. Test Classes: Write positive, negative, and bulk test cases using assertions.

2. Recommended Trailhead Resources

• Apex Basics & Database
• Apex Triggers
• Apex Testing
• Apex Governor Limits

Build one complete project, such as a Student Management or Employee Management application, using Apex classes, triggers, collections, and test classes. 

Key Point: Don't just complete Trailhead badges. Practice writing code independently, debugging errors, and understanding why your code works.

Consistent hands-on practice will improve both your Apex coding skills and interview confidence.

Hope this helps!

Venkat Yadav | SFDCINDIA

Hi @Sai Kumar Good question! In real Salesforce projects, deployments should follow a proper process to avoid production issues.

1. Recommended Deployment Process

Development Sandbox → Testing Sandbox → UAT → Production

1. Development: Build and test changes in a Developer Sandbox.
2. Testing: Verify Apex, Flows, permissions, and dependencies.
3. UAT: Allow business users to test and approve the changes.
4. Production: Validate and deploy after successful testing.

2. Salesforce Deployment Tools

• Change Sets: Best for simple Admin changes and smaller deployments between connected orgs.
• Salesforce CLI: Best for developers deploying metadata using VS Code, Git, and automation.
• DevOps Center: Useful for team collaboration, version control, work items, and release pipelines.

3. Best Practices

1. Maintain at least 75% overall Apex code coverage and cover every trigger with tests.
2. Avoid SOQL and DML inside loops.
3. Include all required metadata dependencies.
4. Validate changes before production deployment.
5. Use Git for version control and code reviews.
6. Prepare a rollback plan and perform post-deployment testing.

4. Official Salesforce Documentation

• Change Sets
• Salesforce CLI Deployment
• DevOps Center
• Salesforce CLI Quick Deployment

Start with Change Sets to understand deployments, then learn Salesforce CLI with Git. For team-based projects, explore DevOps Center.

Key Point: A successful deployment is not just moving changes to production. It's about testing, validation, security, and minimizing business impact.

Hope this helps!

Venkat Yadav | SFDCINDIA

Hi @Sai KumarGood question! Bulkification is one of the most important Apex development practices, especially when handling large volumes of Salesforce records. 

1. Best Practices for Bulkified Apex

1. Avoid SOQL inside loops: Query all required records at once.
2. Avoid DML inside loops: Use Lists to perform bulk insert, update, or delete operations.
3. Use Collections: Use List, Set, and Map to process records efficiently.
4. Handle Multiple Records: Always design triggers to process 200 records, not just one.
5. Use Trigger Handlers: Keep business logic in separate Apex classes.
6. Avoid Recursion: Prevent unnecessary repeated trigger execution.
7. Write Test Classes: Test single records, bulk records, and error scenarios.

2. Important Governor Limits

• SOQL Queries: 100 per synchronous transaction.
• DML Statements: 150 per transaction.
• SOQL Rows: 50,000 per transaction.
• CPU Time: 10 seconds for synchronous Apex transactions.

3. Common Mistakes to Avoid

• Writing SOQL or DML inside loops.
• Assuming a trigger processes only one record.
• Running unnecessary queries and updates.
• Not testing with 200 records.

4. Official Salesforce Resources

• Bulk Apex Triggers
• Apex Governor Limits
• Apex Testing

Build an Account and Contact automation. When multiple Contacts are inserted, update their related Accounts using one SOQL query and one bulk DML operation.

Key Point:

Always write Apex code that works for 1 record and 200 records, not just a single record. 

Hope this helps! Venkat Yadav | SFDCINDIA

Hi @Sai Kumar Good question! The best way to learn Salesforce Flows is to practice real-world business scenarios.

1. Practical Flow Scenarios

1. Record-Triggered Flow: Create a follow-up Task when an Opportunity is Closed Won.
2. Screen Flow: Build a customer registration or case creation form.
3. Scheduled-Triggered Flow: Check overdue Cases daily and notify owners.
4. Scheduled Paths: Send a reminder 3 days after a Lead is created.
5. Fault Paths: Handle Flow errors and log failure details.

2. Important Best Practices

• Use entry conditions to avoid unnecessary execution.
• Use before-save Flows for updating fields on the triggering record.
• Avoid unnecessary Get Records and Update Records inside loops.
• Prevent recursion by checking field changes.
• Test using Flow Debugger and different scenarios.

3. Official Salesforce Resources

• Flow Basics
• Record-Triggered Flows
• Screen Flows
• Flow Builder Documentation

Build one complete Lead Management project using different Flow types and error handling.

Key Point:

Don't just learn how to create Flows. Understand when to use each Flow type and how to troubleshoot issues. 

Hope this helps! Venkat Yadav | SFDCINDIA

@Max Jedrzejewski    Are any participants joining as guests or from a meeting room? Salesforce says ECI doesn’t receive their email addresses in those cases and treats the call as external.

Try a call with two employees logged into their company Google accounts. If the emails are still blank, raise an SF Support case with this example to check why they’re not coming through.