#Trailhead Challenges1.287 discutindo

The behaviour you describe is almost always caused by how the country folders are shared, plus a couple of report settings, and the clean fix is to stop using the role hierarchy for folder access altogether. 

Why access disappears after the role move 

Report folder sharing does not roll up the hierarchy the way record sharing does. If the Country A folder is shared with the role "Sales Rep Country A" (or "Roles and Subordinates" of a Country A/Regional role), the grant only applies to users in that role (or below it). A user you move up to Global Management is no longer in that branch, so they silently lose Viewer access to the folder even though they now see more records. 

Why reports come back empty or error 

1. Scope filters that depend on the user's position: "My Team's Opportunities/Accounts", "My Territory's...", or "My Records" only return records owned by the user and their subordinates. From Global Management the subordinates are different, so the result set changes. 

2. Filters on role fields, for example "Owner Role equals Sales Rep Country A", or relative filters like "Owner Role = my role", stop matching. 

3. Sharing recalculation: after a role change Salesforce recalculates group membership and sharing, which can take a while in large orgs (or be delayed if deferred sharing maintenance is on), so reports can look incomplete for a short time. 

4. Errors usually mean the report now lives in a folder the user cannot access, or it references a report type/field the user no longer has permission to see. 

Recommended architecture: decouple the three concerns 

1. Role = reporting line and record ownership. Keep product managers in the role that reflects their real position (country or regional) and stop moving them. 

2. Record visibility = sharing rules or permissions. Give global viewers read access to all Accounts/Opportunities with a permission set that grants "View All" on those objects (or criteria/ownership-based sharing rules to a public group, if you want to limit it by country or record type). This works independently of their role. 

3. Folder access = public groups. Create groups such as "Reports - Country A Viewers" and "Reports - Global Viewers", share each country folder with the relevant groups (Viewer access), and put the product managers in the global group. Groups can also contain roles or roles and subordinates, so local teams keep their access automatically. 

4. Build cross-country reports with scope "All Accounts/Opportunities" and explicit country filters instead of "My Team's" scopes, so the same report works for everyone and simply returns what the running user can see. 

References: 

Share a Lightning Report or Dashboard Folder:

Create and Edit Public Groups:

Sharing Rules overview:

Trailhead, Data Security (Control Access to Records):

Assumption: I am assuming your folders are currently shared with roles (or roles and subordinates) and that the empty reports use "My Team's"-type scopes or role-based filters; if the folders are shared with groups already, please check the report scope and filters of one affected report and share them here.

This sounds like the "Create Prompts" unit of the User Engagement module, where you build the targeted prompt "Get Help Anywhere in the Console App" in the Sales Console. In that unit the custom theme color is optional ("If you want to select a custom theme color..."), so if the challenge check complains about the theme being set to Dark, the simplest fix is to edit the prompt and remove the custom color (or switch it to Light), then check the challenge again. 

How to edit a prompt that is already active: 

1. In your Trailhead Playground, go to Setup, type "in-app" in Quick Find and open In-App Guidance. 

2. Find "Get Help Anywhere in the Console App" and from the row-level action menu choose Edit. The In-App Guidance Builder opens in a new tab. (If the builder opens on another app, use the App Launcher to open Sales Console.) 

3. In the builder bar, open the "On This Page" list and select the prompt, then click Edit. 

4. On the position/appearance step, uncheck "Use a custom color for in-app guidance" (or keep it and choose Light), click Next, and Save. 

5. Click Settings in the builder header if you also need to verify the action button URL, schedule (End Date about 3 months out, Show when the page loads, Times to Show 2, Days In Between 5), profile/permission options and the API Name GetHelpAnywhereintheConsoleApp. 

6. Click Done and run the challenge check again. 

If the Edit option is greyed out or the builder won't save, an alternative is to delete the prompt from the In-App Guidance page and recreate it following the unit steps without choosing a custom color. Also make sure the Trusted URL for

(API name help_salesforce_com, img-src enabled) exists, since the same challenge checks it. 

Unit:

Considerations for Creating In-App Guidance:

Assumption: your post doesn't include the exact error text or unit name, so I am assuming it is this unit and that the checker message refers to the prompt's custom theme. If it is a different unit, please paste the full error message and the unit link.

Short answer: you generally cannot (and do not need to) write QuoteAccountId into the standard Quote.AccountId field. On the Quote object, AccountId is a system-derived, read-only reference that Salesforce fills from the related Opportunity's Account. It is not createable/updateable through the UI, Flow, Apex or the API, so an update like AccountId = QuoteAccountId will be rejected or ignored. For quotes created without an Opportunity, QuoteAccountId (label "Account for Quote") is the field Salesforce intends you to use as the account relationship. 

For your future Order process this is already covered: Salesforce's documentation for quotes without opportunities says associating the quote to an account is optional but recommended, because an account is required to convert the quote to an order. When you create an Order from such a quote, the account comes from the quote's account (QuoteAccountId), so you don't need Quote.AccountId populated. 

Practical recommendations: 

1. Make QuoteAccountId required (validation rule, e.g. ISBLANK(OpportunityId) && ISBLANK(QuoteAccountId)) so every quote can be turned into an Order. 

2. After enabling the feature, open Object Manager > Quote > Fields > Account for Quote and grant field-level security to your profiles/permission sets. It is hidden by default, which is why it often looks unavailable in Flow, reports and Apex. 

3. In reports, flows, sharing logic and Apex, use one source of truth, for example a formula field BLANKVALUE(QuoteAccountId, Opportunity.AccountId), so logic works for quotes with and without an Opportunity. 

4. If you create Orders yourself via Flow/Apex (rather than the standard Create Order action), set Order.AccountId = Quote.QuoteAccountId and Order.QuoteId = Quote.Id. 

References: 

Enable Quote Creation Without a Related Opportunity:

Release note, Create Quotes Without a Related Opportunity:

Quote object reference:

Assumption: the statement that Quote.AccountId is read-only is based on the Quote object reference field properties and commonly reported org behaviour; please confirm in a sandbox (e.g. attempt the update in a Flow or Developer Console) before designing around it.

Hi @Smita Arora

This error can occur if the ExternalReservation → Contact relationship is not active/configured correctly. 

Please try the following: 

1.  Go to Data Cloud → Data Model → ExternalReservation. 
2.  Open Relationships → Edit. 
3.  Enable Show inactive relationships. 
4.  Check that the Contact ID relationship to Contact/Individual is active. 
5.  Save the relationship and refresh the page. 
6.  Then go back to Setup → Object Manager → Contact → Data Cloud Related List and verify the ExternalReservation related list again. 

Also make sure the Data Streams show Success and contain records before testing the related list. The Trailhead module notes that data-stream processing can take some time.  

If the issue still occurs, I would recommend creating a fresh Trailhead Data 360 playground and repeating the setup, as similar UNKNOWN_EXCEPTION issues have been reported in this challenge.  

If you find this response helpful, please mark it as the Accepted Answer, as it may also help other Trailblazers.