Skip to main content

#Screen Flow2 人正在讨论

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
0/9000

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

🚀 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

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

🎉 Thanks to our Forum Ambassador @Ajaypreet Singh Saini 😍 for an awesome write-up on: How to dynamically find object prefixes to reuse same Screen Flow across multiple objects >> https://help.salesforce.com/s/articleView?id=005131979&type=1  Click to learn more! 

 

We would love to hear your feedback on our article. Please take a moment to let us know by clicking on the "Yes" or "No" button below the article.🎉 Thanks to our Forum Ambassador 😍 for an awesome write-up on: How to dynamically find object prefixes to reuse same Screen Flow across multiple objects >> Click to learn more! We would love to hear #Screen Flow

 

 

2 条评论
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    2025年8月14日 14:43

    Thanks @Bhavin Patel for the shoutout :)

0/9000

I have a date validation on a screen flow Needed_By>TODAY()+13 saying that the needed by date has to be in two weeks.. (there is also a default on the field of exactly two weeks)

 

I have no issue if i leave the default or make the default a later date, but when I make the date sooner, instead of showing the validation error message it gives me a fault:

 

Error element Request_Form (FlowScreen). The "6" value is a Text data type that's assigned to a field with an incompatible Number data type. Assign the value to a field with a compatible data type. #Flow #Screen Flow #Validation Rule

19 个回答
  1. Eric Smith (Retired) Forum Ambassador
    2023年12月5日 18:22

    @Raquel Riemer Yes, I am aware of this issue and it has been resolved in v1.0.1 which is available in v3.2.5 of the FlowScreenComponentsBasePack.

    https://unofficialsf.com/flow-action-and-screen-component-basepacks/

0/9000

Dear all, 

 

We are testing and debugging a "Data Capture Flow" but no details are displayed in the "Debug details" panel. 

 

Do you have any idea why ? 

 

Regards, 

 

Aur Fr  

 

#Screen Flow, #Salesforce Field Service

5 个回答
0/9000

 

[▶️]🔴🔥🎬 New Salesforce Summer 25 Flow Features You Need To See! 

 

In this video, I am sharing all the new Flow enhancements that came up with Summer 25 release. 

 

In this video, I have covered: 

🌟 - Create Flow New User Interface 

🌟 - Improve Article Navigation with Table of Contents 

🌟 - Control Over Component and Field Layout 

🌟 - Add Icons to Choice Resources and Visual Picker 

🌟 - Automatically Triggered Screen Actions 

🌟 - Add Fault Path in Flow 

🌟 - Enhanced Debug Log 

🌟 - Enhanced Email Action 

 

https://youtu.be/PankQiUAi6w

 

 

@The Blog Group @* Release Readiness Trailblazers *[▶️]🔴🔥🎬 New Salesforce Summer 25 Flow Features You Need To See! In this video, I am sharing all the new Flow enhancements that came up with Summer 25 release.

 

 

 

#Salesforce Developer  #Flow  #Salesforce Admin  #Saleforce Administrator  #Screen Flow  #Flownatics  #Scheduled Flow  #New Releases 

0/9000

🎉 Thanks to our Forum Ambassador @sushil kumar 😍 for an awesome write-up on: How to build New Record Screen With API Call Integration >> https://help.salesforce.com/s/articleView?id=004637097&type=1 Click to learn more! 

 

We would love to hear your feedback on our article. Please take a moment to let us know by clicking on the "Yes" or "No" button below the article. 

🎉 Thanks to our Forum Ambassador @sushil kumar 😍 for an awesome write-up on: How to build New Record Screen With API Call Integration >> https://help.salesforce.com/s/articleView?

 

#Screen Flow #API #Salesforce Developer

1 条评论
0/9000