Skip to main content The last day to register for a Salesforce or Tableau exam is June 30th. Learn more about the new Salesforce certification experience coming July 21st.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.
7 answers
0/9000
3 answers
  1. Today, 3:13 AM
    I don't think its possible. You can try logging a case and see if they can do anything.
0/9000
2 answers
  1. Today, 3:07 AM

    Thank you for your prompt response, I did disconnect other playgrounds, still did not get the email to reset the password. 

0/9000

Module: Import Data

  

Tried different playgrounds and laptop but it didn't worked. Please see the screenshot.  

I am trying to map fields in Data Import Wizard but it doesn't display Map button on my system.

 

 

 

 

#Trailhead Challenges

0/9000

What are the steps needed to copy ldsUtils folder and include it in the force-app/main/default/lwc directory in the project? 

 

#Trailhead Challenges

0/9000

I have an orchestrated approval with three approvers. The approval process itself is working correctly now. I'm trying to add information in the screen flow used to gather info from the approvers. I've successfully added input variables to the screen flow, but no changes that I make to the screen in the screen flow appear to the approvers. What is going on here? 

 

I've deleted the older versions of the screen flow. I've deleted the older versions of the orchestration flow. It looks like what is being shown is maybe the original version of the screen from the template. How would I change this?

3 answers
  1. Today, 2:34 AM

    Hi Bruce, 

    Are you still having problems with this?  I have been working on an orchestrated approval process for the past couple of weeks.  I just tried adding display text on my approval screen that shows the values of a couple of Case fields that I pass into it.  Can you provide a couple of screenshots?

0/9000

I've checked the URL; the prompt is active and saved correctly. I've also refreshed and recreated the prompt, but the issue persists. I have checked each step twice, can someone guide me on what I might be doing wrong? 

 

Below I show you the error message: 

 

No encontramos la URL del botón de acción establecida en "https://help.salesforce.com/s/articleView?id=sf.console_lex_feature_parity.htm&type=5" en la ventana "Customize Navigation in Console (Personalizar la navegación en la consola)".

 

#Trailhead Challenges

7 answers
0/9000

I am creating our first flow approval process.  The approval process is on the Case object.  In the orchestration flow, I have two stages; one to get the approval group from custom metadata and to set the Case status to "Submitted for Approval".  The second stage has the screen flow (I used the template).  In that same flow, I have a step to update the Case status and a step to send an email based on the approval decision.  This works great if the screen is used to approve/reject the case approval.   

 

When I approve from the default email sent, the Approval Work Item record gets updated appropriately, but the Case status is not updated and the email is not sent.  I tried moving the Case update/email send to a separate flow and put that in a new stage in the orchestration flow.  This time when I approved by email, it did enter my new flow, but the approval decision was blank.  The approval decision is marked as input/output in the orchestration, as output in the screen approval flow, and as input in the last flow to update the status/send email.   

 

Has anybody used a flow approval process that allowed approval by email and had actions to perform based on the approval decision?  Is there other setup that needs to be done?  If the screen isn't used (i.e. approval done by email), does the Stage with the approval screen complete?

2 answers
  1. Today, 2:06 AM

    @Abhishek R Hi, I figured it out.  I didn't have the default value of the approvalDecision variable set to the output from the stage with the approval screen.  Once I set the default value, the approvalDecision had a value when passed into the flow in the next stage.  With all this, it is clear that subsequent actions (like updating the case status) need to be in a separate stage from the approval screen.  When they were in the same stage, the update records did not run if the approval was done via email (it ran if the approval was done using the work guide).

0/9000