Feed

I'm also seeing this. What's strange is that in my demo org, if you don't select an achievement type and try to search, the search finds the record. It looks like I'm able to create the course with the prerequisite that way.  

I completed this trail almost a year ago, so perhaps the functionality has changed slightly. But the course definitely exists in my demo org, so I'm not sure why it's not finding the result. It doesn't seem to find any other courses, either. 

When I get time, I'll see if I can reproduce this issue in another Education Cloud org that I have. If I can, this might be a Winter '27 regression/bug. I'm curious if other folks are also seeing this.

Hi , 

goto Setup --> Object Manager--> Contact --> Fields & Relationships --> new  

Hi @Rakesh Goud Even if OWD is set to Private, users can still access other users' records through additional sharing permissions.

Possible Reasons:

1. Role Hierarchy: Access to records owned by users below them.
2. Sharing Rules: Records shared based on owner or criteria.
3. Permission Sets: View All or Modify All permissions.
4. Manual Sharing: Records shared directly with users.
5. Record Teams: Access through Account or Opportunity Teams.
6. Apex Sharing: Records shared using Apex code.

How to Troubleshoot:

1. Check the user's Profile and Permission Sets.
2. Check the record's Sharing Hierarchy.
3. Verify Role Hierarchy and Sharing Rules.
4. Check Manual Sharing and Record Teams.
5. Review Apex sharing and related share records.

Useful Documentation:

• Salesforce Record Access
• Salesforce Sharing Architecture

Key Point: OWD Private restricts default access, but additional sharing mechanisms can grant access.

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!

Hi @Rakesh Goud  You can achieve this using a Validation Rule on the Opportunity object.

Steps:

1. Go to Setup → Object Manager → Opportunity.
2. Select Validation Rules → New.
3. Enter a rule name, such as Require_Fields_For_Closed_Won.
4. Add the following formula:

AND(
    ISPICKVAL(StageName, "Closed Won"),
    OR(
        ISBLANK(Amount),
        ISBLANK(CloseDate)
    )
)

Add an error message: "Please enter Amount and Close Date before closing the Opportunity."

1. Save and activate the rule.

How to Test:

• Set Stage to Closed Won and leave Amount blank → Validation error.
• Enter Amount but leave Close Date blank → Validation error.
• Enter both fields and select Closed Won → Record saves successfully.
• Select another stage → This validation rule does not block the save.

Important: In standard Salesforce, Close Date is already a required Opportunity field, so you generally cannot leave it blank. Also, this formula validates every save while the Opportunity is Closed Won, not just the initial stage change.

Useful Salesforce Documentation:

• Validation Rules – Salesforce Help
• Formula Operators and Functions
• Trailhead – Validation Rules

Hope this helps!