Skip to main content
主题#Screen Flow

#Screen Flow11 人正在讨论

提问...
Amy Hogan (Olinsky Law Group 的 Certified Litify Administrator)
9月25日 20:58
Hi! I am looking to create a flow that updates multiple objects at once. Any recommendations on which courses will best help guide me?

I plan to create a quick action button, insert the data once and have it auto update multiple objects including creating an event/activity.  

 

#Screen Flow

3 个回答
  1. Eric Burté (DEVOTEAM) Forum Ambassador
    9月25日 23:23

    Hello @Amy Hogan, if they are all related.. why not. Otherwise, you can also wait for the Winter'27 release and give a try to this new feature : "Process Multiple Records With Screen Flows from List Views and Related Lists". That works only with screen flows for now on. You navigate to a list view page, select all the concern records, and then you are able to Launch a screen flow based on a collection of all flashed records. 

    Eric

撰写回答...
0/9000
Craig Munster (MSA 的 Salesforce Administator) 提问于 #Flow
9月14日 15:03
Convert field formula into a button formula

I have a screen flow that I'd like users to be able to access two different ways: from a field on the Opportunity Product object, as well as a Detail Page Button. What's paramount is where the screen flow returns at its end: I need it to end on a view of the product related list on the related Opportunity record. I got it to work successfully on the field version. Here's my formula field:  

 

HYPERLINK("/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product" &"?recordId=" &Id &"&retURL=/lightning/r/Opportunity/" & OpportunityId & "/related/OpportunityLineItems/view", 

"CLONE", 

"_self" 

) 

 

But for the life of me, I can't get the Button version of the URL to go back to the Product related list. I figured out that I can't reference the Opportunity Id via merge field in this scenario, so I created a formula field called Opportunity_Id__c, which just utilizes a CASESAFEID version of the Opportunity Id.  

 

In order to save time, here is a list of the various versions I've tried that DON'T work:  

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id}&retURL=/{!OpportunityLineItem.Id

} 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/Opportunity/&OpportunityId&/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/Opportunity/OpportunityLineItem.Opportunity_Id__c/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id}&retURL=/lightning/r/Opportunity/{!Opportunity.Id

}/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/Opportunity/&OpportunityLineItem.Opportunity_Id__c&/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id}&retURL=/lightning/r/OpportunityLineItem.Id

} 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

OpportunityLineItem.Id

}&retURL=/lightning/r/&OpportunityLineItem.Opportunity_Id__c&/related/OpportunityLineItems/view 

 

 

Anyone have any thoughts, tips, or suggestions?  

 

#Flow  #Flows  #Screen Flow  #Formulas

7 个回答
  1. Craig Munster (MSA)
    9月21日 14:54

    Hi @Deepak Sachdeva

    , 

     

    Thank you for the suggestion. I tried that, exactly as you laid out, but it still did not work.  

     

    I am happy to announce, however, that I spoke with Salesforce support on Friday and they did get it to work. Confusingly, it was one of the options I had tried before, which is in the list of my original post.  

     

    This is the URL that worked:  

     

    /flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

    OpportunityLineItem.Id

    }&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

撰写回答...
0/9000
Mario Santellan (HEB Grocery) 提问于 #Flow
9月2日 17:10
Help with mapping attachment names into a field

Hi everyone! 

 

I am trying to configure a new screenflow to have it's Uploaded File's name mapped into a text field.  I tried creating a Variable (Text-Collection) and added an Update Records element after the screen in an attempt to map it, but I can't get it right.   

 

What am I doing wrong here? 

 

Help with mapping attachment names into a field

 

image.png

 

image.png

 

 

 

 

 

#Flow  #Screen Flow  #Flows

12 个回答
  1. Himanshu Shekhar (AQBEE Innovations Pvt. Ltd.)
    9月8日 03:09

    @Mario Santellan

      

    your flow is basically right — the only broken piece is the GetFileName filter value. In that resource picker you're currently on 'Related Record ID', which is the record you attached the files to, not the uploaded file. Instead pick the Upload File component's 'Content Document IDs' output (Upload File > Content Document IDs) — that's the list of the uploaded files' Ids. Also change the operator from Equals to In, since that output is a collection: the condition should read Content Document ID In → Upload File > Content Document IDs. Equals against a collection is exactly why nothing matched. Your Title mapping is already right — Title lives on the ContentDocument record, which is why 'Content Document from GetFileName > Title' works in AddAttachmentName (Title = file name without the extension; add FileExtension if you need the .pdf/.docx part). On multiples: with 'Only the first record' selected you'll capture just the first file's name. If a partner uploads 2+ files and you want them all, switch GetFileName to 'All records', add a Loop over it, and in an Assignment append each 'Loop > Title' (plus a comma) into a Text variable, then map that variable into File Name. If one name is enough, first-record is perfect as-is. Give that a try — it should populate.

撰写回答...
0/9000
Rajendra Kumar (REDA.One) 提问于 #Flow
9月9日 08:15
Screen Flow Picklist Choices showing duplicate values for dependent picklist in non-English languages

Hi everyone, 

We are facing an unusual issue with a

Salesforce Screen Flow

and wanted to check if anyone has experienced something similar. 

We have a custom

multi-select picklist configured as a restricted dependent picklist

. Its controlling field is a Checkbox (Boolean) field. 

In our Screen Flow, we are using a

"Picklist Choices" Dynamic Choice Set

directly against this field and displaying the values in a DropdownBox. 

The behavior is different depending on the language: 

 

  • English: The values display correctly, with each value appearing only once.
  • Spanish / Portuguese: Each value appears twice in the dropdown. 

    For example:

Día 

Día 

Hora 

Hora 

 

We have already checked a few possible causes: 

 

  • Object Describe confirms there are only 2 active picklist values — no duplicates in the field metadata.
  • There are no custom Value Translation entries configured for this field in Translation Workbench.
  • The object has only one Record Type, so this does not appear to be record-type related.
  • The duplication happens only when the field is configured as a dependent picklist and the language is changed from English to a non-English language. 

    One additional constraint is that the controlling dependency comes from a 

managed package field

, so we cannot remove or modify the controllingField in the subscriber org. Attempting to do so results in: 

Cannot modify managed object: entity=CustomFieldDefinition, field=PicklistControllerEnumOrId, state=installed 

Has anyone seen this behavior? 

We are wondering if this is a known limitation/bug with

Flow's "Picklist Choices" Dynamic Choice Set and dependent picklists when using non-English locales

. 

If so: 

 

  • Is there a known Salesforce issue or official fix?
  • Is this expected behavior with dependent picklists?
  • Is there a recommended workaround?
  • Should we avoid using Picklist Choices for dependent picklists and instead use the native field binding or static Choice resources? 

    Any insights or similar experiences would be greatly appreciated. Thanks!

#Flow  #Screen Flow

3 个回答
  1. Kundan Kumar Jha (Infosys)
    9月9日 15:58

    Hi Rajendra, 

     

    No exact official Known Issue matches this precisely, but there's a related open one: 

    "Incorrect and duplicate picklist values are showing for a multi-select picklist" (W-9269778, Status: In Review, no workaround yet). 

    Reference:

    https://trailblazer.salesforce.com/issues_view?id=a1p4V000001nogNQAQ

     

     

    Given no confirmed fix exists for your exact case, skip Picklist Choices for this field and use one of these instead: 

     

    1. Record Choice Set on PicklistValueInfo, filtered by EntityParticleId and ControllingFieldValue. This queries raw values directly, bypassing whatever translation-label logic is causing the duplication. 

     

    2. Or use the native "Dependent Picklists" screen component, built specifically for controlling/dependent picklist pairs:

    https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp_dependentpicklists.htm&type=5

     

     

    Both avoid the automatic locale/label resolution that Picklist Choices relies on, which is the likely root cause here. 

     

    Also worth filing a case with Support referencing this exact repro, since it's specific enough (locale + dependent + managed package controller) that it may not be tracked yet.

撰写回答...
0/9000
Ken Tallman
8月27日 03:59
Use Screen Flow to display values from a record and allow edits in a controlled manner

I have an old survey tool written in SF Sites that populates a record in Salesforce. This has worked great for many years and continues to work well, but a key feature that used to allow staff to view and edit the full survey from within SF no longer works (SF retired the feature). I wonder if I can use a Screen Flow to accomplish the same thing. Ideally I would display all 63 questions with the various responses for each question 

 

The custom Survey object has a set of questions and responses where the responses might look like:

  • Most of the time
  • Sometimes
  • Rarely
  • Never

These responses would be assigned a number, 1-4 respectively, and that number is stored with, for example Question 9. On the record in SF, all we see is Q9 with a value of 3 if they responded with Rarely. Seeing that Q9 = 3 isn't very useful since there are too many questions to memorize, so I need a way to display all the questions, all the answers for each question, and the selected answer to each question. If we an get that far, then I need the SF user to be able to change a survey response and have the numeric value associated with that response updated on the corresponding Survey record in SF. 

 

Is this possible? 

 

Below are more sample questions. Note that question 8 will have stored 3, question 9 will have stored 1, and question 10 will have stored 4.  

Use Screen Flow to display values from a record and allow edits in a controlled manner

 

 

 

#Screen Flow

5 个回答
  1. Ken Tallman
    8月31日 00:20

    Thank you. This was a good suggestion as it forced me to reconsider what I'm doing. I now have a partially working flow and am able to have the flow display the values currently in the picklists. That would be great if the data was actually stored as these picklist values, but instead the data is stored as a number indicating which sequential picklist selection was made. This is because we use this numerical representation in formulas. So now my question has shifted a bit. I've created parallel fields on the record with the actual question and answers and can display and edit those. Now I need a way to set these parallel fields based on the numerical values stored in the original fields. For example, the first three questions have these values stored on the record:Thank you. This was a good suggestion as it forced me to reconsider what I'm doing. I now have a partially working flow and am able to have the flow display the values currently in the picklists.

     

    That corresponds to these values in the parallel picklists:

    image.png

     

    In other words, 13 years old was the 4th picklist value in question 1, Male was the second picklist value in question 2, and Heterosexual was the first picklist value in question 3. 

     

    I thought there was a way to map from these numerical values to set the picklist values, and vice versa, but I can't find it. I will need to first map from the number to the parallel picklist value, then if changes are made in the screenflow, then map from there back to the numeric value. 

     

    In case you're interested, here is the beginning of the flow: 

    image.png

     

     

撰写回答...
0/9000
Micah Smalley (Public Responsibility in Medicine & Research 的 Senior Systems Administrator) 提问于 #Flow
2024年2月29日 22:29
Address Validation Rule for Screen Flow

I am trying to configure a validation rule in my screen flow for the input of the address component. This consists of the Mailing Street, City, State, and Country. There is no "required" field to click on this component, so I am hoping to use a validation rule to make sure that all necessary fields are filled. Initially I had it set to check that all of the above fields were not blank, but in my testing I remembered that some countries do not have states. I have the list of countries with states, and I'm hoping to make a validation rule that considers the following:

 

If the country is one with states, then validate that all address fields are filled in. Else if the country is one without states, make sure that all fields except state are filled in. 

 

I am struggling to put the if, else statement in my head into a validation rule for the flow.

 

Also, validation rules in flow are different than fields within Salesforce, as the statement should return true if valid.

 

#Flow

13 个回答
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    2024年3月1日 20:39

    Sure, try this.

    Start with all the fields that should not be blank - street, city, country.

     

    Then you hvae two conditions. Either there is a Country with states (province), then state should have a value. or a country without states, then you don't need a value.

    AND(
        NOT(ISBLANK({!Address.street})),
        NOT(ISBLANK({!Address.city})),
        NOT(ISBLANK({!Address.country})),
        OR(
            AND(
                ISBLANK({!Address.province}),
                CASE({!Address.country},
                    "Australia", 1,
                    "United States", 1,
                    "Mexico", 1,
                    0
                ) = 0
            ),
            AND(
                NOT(ISBLANK({!Address.province})),
                CASE({!Address.country},
                    "Australia", 1,
                    "United States", 1,
                    "Mexico", 1,
                    0
                ) = 1
            )
        )
    )
撰写回答...
0/9000
Michael Kolodner (Kolodner.com LLC 的 Salesforce MVP / Nonprofit Consultant) 发布于 #Flow
4月8日 13:03

It's Natural: Sometimes People Don't Finish

Be careful not to build screen flows that won’t take their final actions!

https://www.freelikeapuppy.tech/post/it-s-natural-sometimes-people-don-t-finish

 

It's Natural: Sometimes People Don't FinishBe careful not to build screen flows that won’t take their final actions!

 

 

@Admin Group, Philadelphia, US @Nonprofit User Group, Philadelphia, US @Admin Group, West Chester, US @Nonprofit and Education MindShare @Salesforce MVP Collaboration Space

 

 

#Flow  #Screen Flow

撰写评论...
0/9000
Nicky Torstensson (Salesforce 的 Senior Technical Architect)
3月20日 08:52

Screen Flow Lookup Component Filters, Limitations and Workaround

 

To anyone who is looking into this, I hope this may help you. 

 

The Lookup screen components, as well as record variable lookup fields has limitations in screen flows. Documentation is here

Lookup Screen Input Component and the considerations states:

  • Dependent lookup filters aren’t enforced for the Lookup component in a flow. Other lookup filters are enforced the same as they are in Lightning Experience record pages. When the flow accesses the Salesforce database, lookup filters are enforced. For example, when the flow executes the Create Records element, the flow fails if the value of the lookup field doesn’t meet the lookup filter requirements.
  • Dependent lookup filters aren’t supported.

 

Consider a business scenario:

  1. User has a picklist field, referencing a global picklist.
  2. Object record also has a picklist field, referencing the same global picklist.
  3. Lookup field on object record has lookup filter, only if the picklist values are equal.

This works fine on flexipages, but not in screen flow lookup components. 

 

Workaround:

However, if the lookup filter is changed from EQUALS to CONTAINS, then the filter still works. Just note, this is then not supported. 

 

#Screen Flow  #Lookup Filter

撰写评论...
0/9000
Sudipta Deb (Silverline 的 Enterprise Architect) 发布于 #Flow
2月3日 15:36

🚀 New Salesforce Feature Explained: Flow Embedded Analytics

 

Understanding how your Salesforce Flows behave in real time just got easier!

In my latest video on Technical Potpourri, I explore Salesforce’s new Flow Embedded Analytics feature, which brings powerful visibility directly into the Flow Canvas.

 

🔍 What’s covered in the video?

• Total flow runs displayed on each flow element

• Clear insights into execution paths and performance

• How this helps admins and developers debug and optimize flows faster

 

If you work with Salesforce Flows, this feature is a game-changer for performance analysis and troubleshooting.

 

🎥 Watch the full video here:

👉 https://youtu.be/FdfXfq6JTqo

 

 

🚀 New Salesforce Feature Explained: Flow Embedded Analytics Understanding how your Salesforce Flows behave in real time just got easier!In my latest video on Technical Potpourri, I explore Salesforce

 

@The Blog Group @* Release Readiness Trailblazers *

 

 

#Flow  #Flows  #Screen Flow  #New Releases  #Release Readiness

1 条评论
撰写评论...
0/9000
Nate Schaufler (Edgewood Management, LLC 的 CRM Associate) 提问于 #Flow
2023年11月8日 20:14
Upload File - Screen Flow

When adding a Upload File screen component, it appears from my research that you need to create the record prior then relate to the Related Record ID.  If that is the case, its a little problematic as I want all components on one nice neat screen.

 

Any suggestions or confirmation is most appreciated.

 

thanks

#Flow   #Screen Flow #Sales Cloud

5 个回答
撰写回答...
0/9000