Skip to main content Heads Up, Trailblazers! Potential Impact to Playgrounds: We're performing some important maintenance beginning on June 27th, 2025. During this time, some of you might temporarily have trouble creating a new Trailhead Playground. If you hit a snag, please try again a bit later. Thanks for your patience as we work to improve your learning experience!

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

Showing This error "Error creating agent : java.lang.IllegalArgumentException: An error occurred while checking for user with id: EinsteinServiceAgent User More Details: ERRORS : An error occurred while checking for user with id: EinsteinServiceAgent User WARNINGS :" when I am filling  the field of Agent User  

 

#Trailhead Challenges  #Salesforce Admin

4 answers
  1. Today, 9:11 PM

    @Sai Kiran Reddy Karingula Has this issue been resolved? I am having a simliar issue and can't progress through the trail because I can't change the agent to EinsteinServiceAgent user. Also earlier in the trail it says to change the profile name to Einstein Agent User.

     

    It later asks to pick EinsteinServiceAgent user when on the "Customize your agent" screen. 

0/9000

estou na poarte de criar filtros para os relatorios porem da erro que nao tem o filtro mesmo tendo: 

 

Não foi possível encontrar o filtro para 'Setor' igual a Energia no relatório 'Status do caso'.

 

 

#Trailhead Challenges

0/9000

Using the new Mule Email Sent. It works if I put static text in the content, but if I use "payload.body", it gives me the error "Error while sending email: mark/reset not supported" when I execute the send command.     It doesn't even matter what the payload is, it can be a string, HTML it does the same thing.    I also tried to put payload.body into a variable and set MIMETYPE = text/html, same error.  Anyone know what I am doing wrong?     

7 answers
0/9000

Hello, I have completed the Trailhead Guide to creating Initial Submission Actions but get the following error:    The initial submission action is not correct for the 'Discount Approval Process'. VP approval does not appear to be required for discounts over 40% for step #2 in the process.

 

I have included a screenshot of my initial submission actions in the attachment. Thank you.   

4 answers
  1. Today, 8:38 PM

    Hi @KEERTHI POTLAPALLI

      

     

    Yes I am still receiving an issue. Here is the URL of the unit: 

    Guide to Initial Submission Actions in Approval

    . I deactivated and relabeled the unique name for the approval steps in the old approval process and started another approval process from scratch. Now I am receiving this issue:  

     

    There was an unexpected error in your org which is preventing this assessment check from completing: System.DmlException: Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Discount_Percent__c]: [Discount_Percent__c]

     

    I have attached a screenshot of my new approval process. Thank you.

0/9000

Hi Folks, 

 

We are looking to create a report that can do the following: 

1. Contacts that gave between July -September 

AND 

2. Contacts that gave a second Year End gift - so between November-December 

 

They then want to import those contacts into a campaign. 

 

A joined report can show me both of those opportunity lists, but it seems like a manual cross check, which is daunting. I also looked at doing a filter for contacts that gave between July-Sept, gave 2 gifts that year, and are not recurring donors. But there are still a bunch of outliers that just randomly gave an additional gift that year, not necessarily year end. 

 

Any insights would be greatly appreciated!

0/9000
Created 3 page layouts(default was renamed and used to clone the other 2). Later for some reason, I had to delete the default page layout although default had to be set to another page layout. 

 

All components are built in a scratch org. When I tried to pull the components from scratch org to repo, I received the error: Entity of type 'Layout' named 'CML_Case__c-Case Layout' cannot be found   

 

Entity of type 'Layout' named 'CML_Case__c-CML Case Page Layout Type 3' cannot be found.

 

Please let me know how I can resolve this and move all my components to the repo successfully.
2 answers
  1. Today, 8:31 PM

    Try to use CLI:

    sf project retrieve start -m "Layout:ObjectName-Layout Name"
0/9000

Hello all, I am trying to retrieve a layout in FSL through package.xml from the Work Order object but the layout cannot be found. 

 

I tried retrieving sing this: 

<types>

    <members>WorkOrder-FSL Work Order Layout</members>

    <name>Layout</name>

</types>

 

Does anyone know what is wrong with this? Thanks.

 

Screenshots:Cannot find layoutimage.png

3 answers
0/9000

TL;DR: In need of specific instructions to enable SMS-based login with SMS TOTP for Experience Cloud

  

 

Hello – I am seeking support from this community to implement a specific login option for Experience Cloud.  Getting this solution implemented will benefit thousands of deserving families served by our client.  

 

What we need to set up:

 

Users need to login to Experience Cloud via their mobile number (not an email address).  For identity verification, users need to receive a TOTP (time-based, one-time password) texted code (via SMS, not a third party authentication app). 

 

Though I have searched the Help documentation and Trailhead for hours trying to solve this on my own, I simply cannot find a clear set of instructions for what to do anywhere.  Everything I do find takes me to instructions for a different option than what we are trying to implement. 

 

Here are the pertinent details:

  1. Salesforce NPC with Experience Cloud 
  2. We will have both Customer Community and Customer Community Plus users using this feature 
  3. We have paid for Available Identity Verification Message Credits (a Usage-based entitlement), and our Company Information page shows that they are present in our org. 
  4. I have the Login by phone number option configured in the Administration Settings > Login and Registration > Login Page Setup, but cannot figure out how to get the texted code sent out. 
  5. We are not planning to implement self-registration at this time, if relevant.  Our clients are willing to do what they need to do on the backend to set up individual users. 
  6. We are also implementing an SMS app for other purposes in the project. It’s not my understanding that Salesforce requires use of a third-party SMS provider in order to enable SMS/TOTP, since we paid for those – but if that’s how we need to do this, that’s how we’ll do it. 

 

I have already consulted with Experience Cloud experts within my own organization; it just has not come up on any project before.  SMS authentication is not my personal area of expertise either.  I would greatly appreciate a set of clear instructions – where to go, what to enable or configure, ideally specific and making no assumptions that I’ve had previous experience with Mobile Identity or Salesforce Identity or any of those other products. 

 

If you don’t have those details, but you have hints, or are willing to @mention someone you think may know  how to do this, that would be great too! 

  

 When I get the details and confirm it’s working, I’ll gladly share any learnings for anyone who finds themselves in this situation in the future! Thank you for your support! 

8 answers
  1. Today, 8:29 PM

    There is a whole side to this that is not documented anywhere and in a recent implementation of passwordless I went through it. 

    After completing all the settings that you might find online, you will find that there is no standard way to verify the mobile number for external users, so you will need to build something that allows the external user to verify their mobile (we built an LWC). 

    Also, if you are not using Self-Registration, there is a hidden field (not mentioned anywhere) called "Admin Trusted Mobile Number" which only gets checked off when the self registration is done and the user verifies their mobile number or when an Administator (User with a System Administrator profile) enters their mobile number in their user record. 

    So even when the users can edit their profile and through your LWC they can verify the mobile number, if an Administrator did not enter that information in the user record, the Standard Login Discovery will not allow the user to login. 

    I am trying to build something around that so that the process is not so painful for existing experience cloud users or non-self-registered users. 

    Will keep you posted on the findings.

0/9000