Dynamic Forms for Flow (beta)

As a Flow Builder,

I want Labels and API Names to be consistent on Screen Flows,

So that I know what to do

Please upvote here; https://ideas.salesforce.com/s/idea/a0B8W00000QcijGUAR/make-api-name-and-label-behaviour-consistent-for-screen-flows

#Salesforce #Salesforce Admin #Salesforce Developer #Flow #CRM Configuration #TrailblazerCommunity #AwesomeAdmins

@* Salesforce Developers *  @* Salesforce Platform * @Admin Trailblazers @Flow Toolbelt @Flow Orchestration @Flow Reactive Screen Components (GA) @Flow for Nonprofit Admins @Lightning Flow Discussions @Salesforce Flow Automation @Screen Flow Action Button Beta

Dynamic forms for Flow don't currently support certain filed types including Currency and Time. Are there any plans to make these available and if so when? 

And how about Rich Text with an editor?

Whilst I'm on the subject, Time variables generally are almost impossible to work with in flows. Are there any plans to change that? When?

Thanks.

Sean

Hi, in Spring 23, we can Easily add Lookup fields to flow screens and create a record directly from the Lookup field with Dynamic Forms for Flow. However, it does not give me the option even as an admin to create a new record. I can search for records but not create a new one inside the lookup. 

We have a form for a Grant Process  that has several conditional sections (one: if Grant Term Length is 2 years, only show two of the Grant sections.) We have pushed to Production and the conditional filtering didn't come. Is there something to do besides build all that over again??

Thanks

I'm attempting to use record fields on a screen flow for the first time, and even though mailing address (Contact object) is an option for me to choose, it's not recognising that I'm populating the field. 

After the screen I have a decision that asks if the mailing address is null, and I get the following error message when debugging the flow:

The flow failed because the "varContact.MailingAddress" variable was set with an incompatible data type. Make sure that assignments to this variable use only compatible data types".

Any idea? I'm struggling to find anything online that can help.

I've loved the addition of the record fields into screenflow, it has massively helped overcome one issue I found in the dependent picklists being only 3 tiers and me needing 5 for Case creation.

But, I cannot see a standard object 'Activity' in the list of objects when I create the variable to use for the record.  Why is this, am I doing something incorrect or is this object not supported?

We previously were having difficulty with how conditional fields rendered. The solution to the problem was that we needed to do the condition by the field, not the section. I now have a much larger group of fields that I would like to condition by section. Twenty rows of five fields each. This would require hundreds of separate field condition filters. 

Do we know why not, or if i can do the conditions by section. It allows me to do the filters by section. But do they work?

Thanks!

Loving dynamic forms for flow! From my testing, it respects FLS which is great. Does it also support language localisation? I'm assuming (hoping) the answer is yes. I'm talking about Flow Improvements in Summer 21 at the London Admins user group next week and want to make sure I get my story straight. Thanks :)