Feed

Was able to resolve this by deploying the message channel first and then the lwc components.

Hello @jessica watson

If your custom object is not appearing in the Report Builder's list of available report types in Salesforce, it’s likely due to one of the following reasons: the object hasn’t been added to a report type, it lacks the necessary permissions, or it’s not properly configured for reporting. Here’s how to resolve this, especially in the context of a Trailhead challenge: 

  - Go to

  - Look for an existing report type that includes your custom object (e.g., "Accounts with CustomObject__c") or create a new one. 

    - Click

    - Select a primary object (e.g., Account, Contact, or Opportunity) that relates to your custom object. 

    - In the

, add your custom object (e.g., `CustomObject__c`) using a lookup or master-detail relationship. 

    - Save the report type and ensure it’s marked as "Deployed" (not in development). 

-

  - Ensure your user profile (e.g., System Administrator) has access to the custom object. Go to

permissions are enabled. 

  - If the object is new, check that it’s been deployed (not just created in a sandbox or draft state). 

  - If your custom object is related to a standard object (e.g., via a lookup or master-detail field), ensure the relationship field is active and the report type includes this relationship. For example, if `CustomObject__c` has a lookup to Account, the report type must define this junction. 

  - In Trailhead challenges, playgrounds are pre-configured, and some custom objects might be hidden or restricted until specific steps are completed. Review the challenge instructions to see if you need to create or enable the object first (e.g., via a provided data model or setup task). 

  - If the challenge provides a specific report type, use that instead of creating a new one, as custom report types might not be recognized by the validation. 

-

  - After making changes, refresh the Report Builder (

dropdown again. 

  - If the object still doesn’t appear, create a simple test report using the new report type and verify it works. 

  - The object might be marked as "Allow Reports" in its definition.

and ensure "Allow Reports" is checked. 

  - If the object was recently created, wait for metadata propagation (up to 10 minutes) or reset the challenge to regenerate the playground. 

It looks like you're encountering a permission or visibility issue while trying to link a connected app to your service agent. The error "descriptor": "markup://aura:noAccess" typically means that the component or functionality you're trying to use is restricted due to insufficient permissions or is not exposed in the current context.

Here are a few things to check:

1. Permission Sets: Ensure that your user profile or permission set has access to the connected app. Sometimes, the app is created under a different namespace or is restricted to admin users.
2. App Visibility: Make sure the connected app is marked as "Visible" to your current user or service profile. If it's managed or coming from a package, visibility settings might be restricted.
3. Namespace Conflicts: If you're working in a namespace-enabled org (like in managed packages), this kind of error can also show up if the component isn't shared across namespaces properly.
4. Use of Aura or LWC Components: The "markup://aura:noAccess" is specific to Aura framework. If you're using a custom Lightning component to manage the UI, it might not have access to certain internal components or methods.

To better prepare for these real-world Salesforce issues, resources like Pass4Future offer practical exam questions that often reflect similar scenarios in actual environments. Their resources are helpful not only for exam prep but also for applying best practices in projects. If the issue persists, try reviewing debug logs or enabling Lightning Debug Mode for more detailed error messages. You can also try linking the app using the API or Metadata deployment as a workaround.

Let me know if you want help walking through the setup step by step.

always use official resources for exam preparation

https://trailhead.salesforce.com/content/learn/projects/connect-your-agentforce-org-with-slack/add-metadata-for-your-agent

@Buyan thyagarajand

you can do this for each group, global is not necessary, you can also control the behaviour in a flow or apex code to reset the setting if a user goes against it. 

but generally it is a setting in the group 

list<collaborationGroupmember> cgms = new List<CollaborationGroupMember>();        cgms = [select id,CollaborationGroupId,NotificationFrequency from collaborationGroupmember where CollaborationGroupId=:'<YOUR Chatter group ID>'];        for(collaborationGroupmember c: cgms){            c.NotificationFrequency='W'; //[W]eekly [D]aily [P] everypost [N]ever        }        update cgms;