#Trailhead Challenges1,178 人がディスカッション中

Hi , 

Try this 

public class AccountHandler {
    public static Account insertNewAccount(String AccountName){
        Account acct = new Account(Name=AccountName);
        try {
            insert acct;
        } catch (DMLException e){
            return null;
        }
        return acct;
    }
}

Hi @SHUBHAM KUMAR SINGH

+1 to Danish.  

One more thing: those errors read like Agent Script validation messages, so it’s worth switching the new Builder to Script view and looking at the action definitions directly. If the inputs and outputs blocks are empty there, the action didn’t pull the flow schema. You can either recreate the action or add the inputs and outputs with their types in the script (string for email, memberNumber and experienceName, object for the record outputs). Then save and activate the new version before checking the challenge. 

Hi @Hang Stanford

You’re close, don’t reset anything yet. Keiji’s tip is the right place to start. The checker looks for the latest version of the agent and the exact name, so: 

• In Setup, open Agentforce Agents, then open Sales Coach Agent in Builder.
• Check the name and API name match what the challenge asks for exactly, spaces and capitals included.
• If you have more than one version, deactivate the older one, make sure the latest version has all the topics and actions from the steps, and activate it.
• Check that the challenge is pointed at the same org you built in. Some Agentforce modules need the special Agentforce Developer Edition org from the module’s signup link, not a standard playground.
• Log out of the org, log back in, and click Check Challenge again.

 If these steps do not help, could you please share a screenshot of the exact error that you see!

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

理由と設定のポイント： 

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

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

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

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

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

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 

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!

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!