Skip to main content

#Trailhead Challenges1 180 personnes en discutent

Hands-on challenges are the “secret sauce” of Trailhead. Before searching for solutions to superbadge challenges, review the Salesforce Certification Program Agreement and Policies. ** NOTE ** : If you were able to get a response that solved your issue, please mark it as the 'Best Answer' to help other Trailblazers. If the issue persists after 48 hours, create a Trailhead Help case at https://help.salesforce.com/s/support for further assistance.
愛子 千葉 a posé une question dans #Salesforce

「取引先責任者」について、 

既存の項目以外に、詳細情報を追加入力したいと考えています。 

項目としては20項目以上追加する予定なのですが、 

追加するデータは、A部門しかアクセスできないようにしたいと考えています。 

 

その場合、 

①「取引先責任者」にぶら下がる「別オブジェクト」として 

新たにオブジェクトを作成し、そこに項目追加していく方法が良いか 

②もしくは、既存の「取引先責任者」オブジェクト内に必要項目追加し 

項目アクセス権限で制御した方が良いのか 

どちらの方がレポート作成、権限設定など含め運用がしやすいでしょうか。 

 

②の場合、表示項目が多いとレイアウトが下に長くなるので 

それはあまり良くないなとは思っているのですが、 

同じオブジェクト内の方がレポート等作りやすいのかな? 

という思いもあったりで迷っております。 

 

①②以外にも、他にもっと良い方法があればぜひご教示願います。 

どうぞよろしくお願いいたします。 

 

 

#Salesforce  #Trailhead Challenges

1 réponse
  1. 25 oct., 22:11

    こんにちは。1人の取引先責任者に対して1件分の情報であれば、②の「取引先責任者に項目を追加し、権限で制御する」方法をおすすめします。 

    理由と設定のポイント: 

    1) レポート:同じオブジェクトにあるため、標準の「取引先責任者」レポートタイプでそのまま集計できます。カスタムレポートタイプの作成は不要です。 

    2) 権限:「A部門用」の権限セットを作成し、追加項目の参照・編集権限(項目レベルセキュリティ)を付与してA部門のユーザーに割り当てます。それ以外のユーザーには、画面だけでなくレポートやリストビューでも項目が表示されません。 

    3) レイアウト:動的フォーム(Dynamic Forms)で追加項目用のセクションを作り、タブに分けるか、表示条件でA部門のユーザーにだけ表示するようにすれば、ページが縦に長くなる問題も解消できます。 

    ①の別オブジェクトが向いているのは、1人の取引先責任者に複数件の情報(履歴など)を持たせる場合です。その場合は、オブジェクト権限をA部門の権限セットにだけ付与することで制御できます。 

    ご参考になれば幸いです。

0/9000

I have no idea what I did wrong but I am missing a step. I need guidance on how to reset the playground, though my account said I have maxed out my playground. It does not give me step by step to review what's active and what I can deactivate. I'm so closed to Innovator (91% completed) and this step is only 100 points. It said that a step is not yet complete in agentforce. It cannot find the most recent version of the agent ‘Sales Coach Agent’. 

 

I tried to reset the playground but I'm also running into no luck. Please help!

 

#Trailhead Challenges

0/9000

Hi  

I have completed the exact steps with same details in the Prompt Builder course - And i am stuck with this error; I have deleted, re- created several times yet the error- does not seem to resolve. 

 

Please help -

https://orgfarm-a09e7aab1a-dev-ed.develop.lightning.force.com/lightning/r/Case/500d200003aHKpmAAG/view

 

I am stuck and unable to move past this , please help me resolve this issue 

 

#Trailhead Challenges  #Agentforce

1 réponse
  1. 25 oct., 22:45

    Hi , 

     

    Salesforce Support has confirmed that this is a known issue.  

     

    Workaround to complete the challenge

     

    : Creating a new Org again from scratch and repeating the steps fixed the issue.   

     

    To create a new Org using the button " 

    Create Playground" on the unit, you should create a normal Playground from Profile > Hands-On Orgs

     

    section.  

    This will allow you to 

    Disconnect existing Einstein AI Playground

     

    from your Trailhead profile.  

    Once the exisiting Playground is disconnected, you will see " 

    Create Playground

     

    " button on the unit once again, you can use the same to initiate the creation of new Einstein AI Playground and repeat the steps.  

    This has worked for me & I was able to complete the badge.   

    https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007ifh14 

0/9000

I’m having problems with the Trailhead Create Sharing Rules. I’ve already successfully completed the previous steps, but here, after several reviews and having repeated it more than 3 times, I haven’t been able to fix the error: In the ‘Share Won Opportunities with Account Receivable’ sharing rule, it doesn’t look like the records are shared with the ‘Accounts Receivable’ role. 

Error Create Sharing Rules - In the ‘Share Won Opportunities with Account Receivable’ sharing rule, it doesn’t look like the records are shared with the ‘Accounts Receivable’ role.

 

 

image.png

 

 

 

#Trailhead Challenges

1 réponse
  1. 25 oct., 22:17

    Hi Luis, thanks for the screenshot, it shows two likely causes: 

    1) Your Opportunity organization-wide default is Public Read/Write. Sharing rules can only open access beyond the default, so with Public Read/Write the rule has nothing to share and the checker can't confirm it. Set Opportunity's default internal access to Private (as the earlier step asks), and let the recalculation finish. 

    2) The rule's criteria use Won equals True. Edit the rule and use the criteria exactly as written in the unit (Stage equals Closed Won), and set the access level the instructions specify. Keep the rule name exactly 'Share Won Opportunities with Account Receivable' and Share With = Roles: Accounts Receivable. 

    After saving, wait for the sharing recalculation email (or check Background Jobs) before you click Check Challenge. Hope this helps!

0/9000

Cannot get Communicate Between Lightning Web Components > Communicate from Parent to Child to validate after hours of troubleshooting.

  Constant error:     Step not yet complete in <<orgname>>

We can’t find the ‘counter’ attribute in the ‘c-numerator’ tag in augmentor.html”.    

1 réponse
  1. 25 oct., 22:15

    Hi Ellen, this checker reads the deployed augmentor.html in your org, so it's usually either the markup or the deploy. Things to check: 

    1) In augmentor.html, the child tag should pass the value as an attribute, like this: <c-numerator counter={startCounter}></c-numerator>. The attribute must be all lowercase (counter), with no quotes around the curly braces. 

    2) In numerator.js, counter must be a public property, declared with the api decorator and with api imported from lwc. 

    3) Right-click the augmentor folder in VS Code and choose SFDX: Deploy This Source to Org, and confirm there are no deploy errors. A local edit that wasn't deployed is the most common cause. 

    4) Make sure the org your VS Code project is authorized to is the same org selected in the challenge dropdown. 

    Hope this gets you past it!

0/9000

The step is still not being marked as completed in Agentforce.

I keep getting the following error: The stage is not yet completed in Agentforce

Sales coach Agent in Agentforce Sales Coach: Opportunity Coaching topic cannot be found.

Because of this error, I cannot proceed to the next step.

I have already tried all of the solutions suggested in the Trailblazer Community, but none of them resolved the issue.

Could you please investigate and fix this problem as soon as possible?

I am unable to continue with the module until this issue is resolved, and I am running out of time. Your prompt assistance would be greatly appreciated.

1 réponse
  1. 25 oct., 22:14

    Hi, this error means the checker can't find a topic with that exact name on the agent it's checking. A few things that usually fix it: 

    1) Open the Sales Coach agent in Agentforce Builder and confirm the topic is named exactly Opportunity Coaching (same spelling and capitalization, no extra spaces) and that its API name wasn't changed. 

    2) Make sure the topic is added to the agent itself, not only saved in the Topics library. 

    3) Deactivate the agent, save the changes, then activate it again. The checker reads the active version. 

    4) Confirm the org selected in the challenge dropdown is the one you configured. 

    If all of that matches and it still fails, open a case with Trailhead Help with a screenshot of the agent's topic list. Hope this helps!

0/9000

Hi everyone,

I'm completing the Trailhead module "Build with Agentforce Builder" and I'm stuck while creating the custom actions for the Experience Management subagent.

I created the flows provided in the playground:

  • Get Experience Details
  • Get Customer Details

Both flows are Active and have the expected variables configured.

Get Experience Details

  • experienceName – Text, Available for Input 
  • experienceRecord – Record (Experience__c), Available for Output 

Get Customer Details

  • email – Text, Available for Input 
  • memberNumber – Text, Available for Input 
  • contact – Record (Contact), Available for Output 

However, when I configure the custom actions in Agentforce Builder and enable Require Input to execute action or Show in conversation, I receive the following validation errors:

'email' is not a defined input of action 'Get_Customer_Details'

'memberNumber' is not a defined input of action 'Get_Customer_Details'

Action input 'experienceName' in 'Get_Experience_Details' has primitive type 'string' and does not require 'complex_data_type_name'. Only 'object' and 'list[object]' types require 'complex_data_type_name'.

Missing type for inputs 'email'. Expected a type after: (string, number, boolean, object, currency, ...)

Empty 'inputs' block — must contain at least one entry

Missing type for outputs 'contact'. Expected a type after: (string, number, boolean, object, currency, ...)

Empty 'outputs' block — must contain at least one entry

I've already tried:

  •  Verifying all Flow variables and their Input/Output settings. 
  •  Confirming both Flows are Active. 
  •  Removing and recreating the custom actions. 
  •  Refreshing Agentforce Builder. 

The Flow definitions appear to be correct, but Agentforce Builder continues to show these validation errors.

Has anyone experienced this in the Agentforce Builder Playground? Is this a known issue with the current Trailhead playground, or is there an additional configuration step I'm missing?

Any help would be greatly appreciated. Thanks! 

 

#Trailhead Challenges

1 réponse
  1. 25 oct., 22:13

    Hi Shubham, those errors mean the action's input/output schema is empty, so Agentforce Builder isn't seeing your flow variables. That usually happens when the action was created before the flow version with those variables was saved and activated, and the action keeps the old schema. Try this: 

    1) In Flow Builder, open each flow and confirm the active version has the variables marked Available for Input/Output, with API names exactly email, memberNumber, experienceName, contact, experienceRecord. 

    2) In Agentforce Builder, delete the two custom actions, refresh the page, and create them again from the flows. The inputs and outputs should now fill in automatically. 

    3) Only after they appear, set Require Input and Show in conversation. Don't add a complex data type to the text inputs; that's only for record/object types. 

    4) Save, then commit or activate the agent version before checking the challenge. 

    Hope this helps!

0/9000

trigger AccountAddressTrigger on Account (before insert, before update) { 

    for(Account a: Trigger.New){ 

        if(a.Match_Billing_Address__c == true && a.BillingPostalCode!= null){ 

            a.ShippingPostalCode=a.BillingPostalCode; 

        } 

    } 

} 

Failed to enqueue tests.: An unknown exception occurred. 

 

#Trailhead Challenges

1 réponse
  1. 25 oct., 22:13

    Hi Shreya, your trigger logic is fine. "Failed to enqueue tests: An unknown exception occurred" is an org-side error when the checker tries to run tests, not a problem with your code. Things that usually clear it: 

    1) Go to Setup > Apex Classes and click "Compile all classes". One broken class anywhere in the org can stop tests from queueing. 

    2) Check Setup > Apex Test Execution. If any test runs are stuck in the queue, abort them, wait a few minutes, then check the challenge again. 

    3) Make sure the trigger is Active and the Match_Billing_Address__c checkbox field exists with exactly that API name. 

    4) Optional: the challenge only asks you to copy the postal code when the checkbox is true, so you can drop the null check to match the spec exactly. 

    If it still fails, deploy the same trigger to a fresh playground. That error is often a temporary playground issue. Hope this helps!

0/9000

Step not yet complete in Playful Moose Playground

We couldn't find the correct settings for the profile 'HR Recruiter' object named 'Candidate__c'. Double check the instructions. I have done all the recruiting modules in a single playground and still it shows this error please help to solve this 

 

#Trailhead Challenges

1 réponse
  1. 25 oct., 22:10

    Hi Shreya, this checker compares the HR Recruiter profile's Candidate object permissions against the instructions exactly, so extra permissions fail it just like missing ones. Things to check: 

    1) Open Setup > Profiles > HR Recruiter > Object Settings > Candidates, and compare each box (Read, Create, Edit, Delete, View All, Modify All) with the unit's table. Untick anything the instructions don't list. 

    2) Confirm the profile name is exactly HR Recruiter and that it was cloned from the profile the unit specifies. 

    3) Check the Candidate tab setting on the same page, since it's part of the object settings the unit asks for. 

    4) Make sure there's only one Candidate object (API name Candidate__c) in the org. Doing every Recruiting module in one playground can sometimes leave a duplicate object or profile. 

    If it still fails after that, a fresh playground for this module usually clears it. Hope this helps!

0/9000

I can;t figure out what;s missing: We can’t find an Assignment element named 'Set the Error Message Output'. Make sure the API Name is 'Set_the_Error_Message_Output'.

 

#Trailhead Challenges

1 réponse
  1. 25 oct., 22:10

    Hi Eduardo, the checker matches on element type and API name exactly, so it's usually a small mismatch. Things to check: 

    1) The element must be an Assignment, not a Decision or Update Records element. 

    2) Open the element and confirm the API Name is exactly Set_the_Error_Message_Output. If you renamed the label after creating it, the API Name doesn't update automatically, and extra spaces or a missing underscore will fail the check. 

    3) Make sure you're editing the flow the challenge names, then Save and Activate. The checker reads the active version, so a newer unsaved or inactive version won't count. 

    4) Confirm the element is connected in the path the instructions describe (for example, on the fault connector), not left floating on the canvas. 

    Then check the challenge again against the same org. Hope this helps!

0/9000