alexed1
FlowScreenComponentsBasePack-Draw a Line-Screen Crash after clicking Previous
I'm using the latest version of the FlowScreenComponentsBasePack (version 3.2.2)
I have a screen with a "Draw a Line" which works fine upon first screen rendering.
However, if you click 'Next', and on the next screen click 'Previous' to re-draw the screen with the line, you get a screen crash:
Flow encountered an error when processing and converting between data types. Please check the flow and ensure all data types are matched correctly.
You can easily replicate this issue. Create a screen flow.
Create a Screen element, labelled Screen1. Don't put anything on the screen other than the 'Draw a Line', with API name Line1, change the Line Thickness slider to '5'. Click done.
Now copy that first screen element, so you have two elements, Screen1, and Copy1 of Screen1.
Debug the flow.
First screen renders with the line ok, click 'Next' Second screen renders with line ok. click 'Previous'. CRASH.
Notably, if you don't touch the thickness slider from the default of '1', the problem does not occur. But if you do save the slider with a value greater than 1, and then save it back to 1, the problem continues, so I believe the bug is in the storage of the non-default line thickness value. As soon as you touch it, it overrides the default and somehow the datatype is bad when it renders the screen upon a 'Previous'. Very weird.
@alexed1 @adwhite75 Could one of you have someone take a quick look at this very simple component and let me know what needs to change to make sure the component behaves correctly when the User revisits the screen via the Previous button?
If it is an underlying SF bug, the scratch org I am testing with is on CS58, which is patch level: Summer '23 Patch 14.3
@alexed1 It's an LWC (w/CPE) replacement for the standalone horizontalLine Aura component.
This is also happening on any button push even if it is Finish button. I am unable to use Draw A Line. Salesforce has recommended removing the component so that my flow will work.
@adwhite75 or @alexed1 Is there someone you could have take a quick look at this?