Feed

Thanks Mustafa, we are using Outlook.

Do you think the standard Salesforce Outlook Integration plugin can handle this requirement smoothly?

Our goal is for the AM to be able to create a new case with a single click upon receiving an email, without any manual data entry. We need the system to automatically map the relevant fields, carry over any attachments, and natively link the Case to the correct Account and Contact based on the original sender's email address.

Also, does the plugin allow the AM to easily relate a newly received email to an already existing case in Salesforce, and seamlessly continue managing the entire email thread and replies directly from within the Case?

Workaround (not a solution): 

What I have observed is, that I had somehow two (!) salesforce orgs connected to the slack instance.  

I have entered "self employed" as a company name on sign up ... now I have got two org entries: one named "self" and the other named "self-employed".  

This is very strange, because I have never (!) added the first one. That did not follow the setup advised in the trail as it had the "map users automatically" set (not disabled, as advised).  

So in sheer panic I have deleted (disconnected) the two orgs and have reiterated all the steps in the second part of the trail. ... and that eventually worked out.  

As I have admitted before this was the outcome of a panic reaction. It might have very well been sufficient to simply delete (disconnect) the first org. But I do not know.  

This is not at all a page of glory, admittedly ... but this has let me finish the trail and therefore the "TDX Quest 2026". 

And this is actually the reason I am writing this:

At this point, let me take advantage of the moment and thank all the friendly contributors. 

Take care

1. What exactly does "Choice Value" do ? 

• Think of the Label as the mask (e.g., "Edge Communications") and the Choice Value as the real identity behind the mask (e.g., 0018000000Sj7YyAAJ).

2. Which field should we choose normally ? 

In

• Why? Because the ultimate goal of picking a record in a screen Flow is usually to do something with it later in the Flow (update it, delete it, link a Contact to it, create a Task, etc.). To perform any of these actions, Salesforce requires the unique 15 or 18-character Record ID.

3. What happens if we choose another field ? 

If you choose a field other than Id (like

• The Danger: If you store the Name as the Choice Value, and later in your Flow you try to use an "Update Records" element with that value, the Flow will crash. Salesforce cannot update a record using its Name; it absolutely needs the Id.
• When is it useful? You would only choose a field other than Id if your Flow doesn't care about the record itself afterward, but just wants to grab a piece of text. For example, if you query a custom object "Predefined Comments" and you just want to inject the text of the comment into a case description.

@Hasan Mustafa

As per the instruction they mentioned in the trailhead I think new action should not be needed .Let me try modifying this and calling seperate action to set in before reasoning 

instructions: ->         
   |Convert the date provided by the user into the YYYY-MM-DD format and store it in the @variables.converted_date variable before using it for the {!@actions.Get_Sessions} action. 

You cannot make the page read-only. But, you can upgrade to Dynamic Forms and make the fields read-only.