Lightning Component input and output behavior in Salesforce Flows

December 13, 2020•70 words

When using lightning components in flows, the behavior of input and output variables can be really strange when navigating backward through the process. Should the component remember its default value or if the value has mutated, should it use the new value?
I've struggled with this a couple times on client work.

While not perfect, Alex Edelstein shares some tricks to getting it to behave the way you want. UnofficialSF

👍❤️🫶👏👌🤯🤔😂😍😭😢😡😮

Subscribe to the author

You'll only receive email when they publish something new.

More from Scott McClung
All posts

Death of good conversation

December 9, 2020•21 words

The attempt to change someone's mind is the death of good conversation. - Celeste Headless - Jordan Harbinger Show ep. 423 ...

Read post

Edge case date issues in APEX

December 31, 2020•172 words

Chris Peterson tweeted a good reminder this morning that the subtle difference between YYYY and yyyy in the Java date format can lead to unexpected date bugs in your APEX code around this time of year. For most of the year, the output of Datetime.format('MM/dd/YYYY') and Datetime.format('MM/dd/yyyy') will appear to be interchangeable and all your tests will seem to pass. The java date format documentation doesn't make it particularly clear that the YYYY year format is using the ISO week date...

Read post

Lightning Component input and output behavior in Salesforce Flows

More from Scott McClungAll posts

Death of good conversation

Edge case date issues in APEX

More from Scott McClung
All posts