*DataTable* - _(Reactive Component Source)_ - Input fields using DataTable row as default value are overridden

[andrewmondy]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Steps to reproduce the behavior:

1. Create a new screen flow,
2. Create an arbitrary Get Records element,
3. Create a Screen element with a USF DataTable showing the records and a Text entry component with the default value of the DataTable Selected Row (any field).
4. Create a second screen element to show the value of the Text field from the first screen.
5. Run the Screen Flow, choose a row in the datatable, note that the text field value is updated to the field from the datatable by defualt.
6. Change the value of the text field to something else. Click Next

Expected behaviour

The value of the text field should be shown as the entered text from the prior screen

Actual behaviour

The value of the text field shows the original default value from the DataTable row instead

Screenshots

If applicable, add screenshots to help explain your problem.

Debug Logs

If applicable, please insert debug logs here

[andrewmondy]

[ericrsmith35]

I'm not sure why this is happening. I've tested this workaround and it should resolve your issue.

• Create a formula resource in the flow and have it be the value of the Alias field in the selected row from the Datatable
• Use the formula as the default value for the text input

[ericrsmith35]

@alexed1 @adwhite75 The built in Data Table does not have this issue. Is there anything different I should be doing to support this type of reactivity?

[tdimel]

Ran into this today and verified the workaround works; however, I noticed that not all input components are affected. This is using most recent version of Datatable (4.3.2).

Affected Input Components:
Text
Picklist
Date
Checkbox (workaround does not work in a straightforward way, see next post)

Unaffected Input Components (values update as expected):
Address
Currency
Phone
Email
Long Text Area

**edited to include checkbox
***edited to add checkbox caveat

[tdimel]

The workaround for checkboxes does not work UNLESS you display the value of the datatable.outputSelectedRow.booleanField on the screen.

Scenario:
Screen with single row selection datatable displaying a collection of contact records, with columns of Name and Do Not Call. Screen also has a checkbox component titled, Do Not Call.

To work around this bug, a formula has been created (fxDoNotCall) that is set to {!Datatable.outputSelectedRow.DoNotCall} field, and the checkbox component has its default value set to this formula.

When running the flow, the checkbox remains blank (null) and does not reflect the proper Do Not Call values for any contact selected.

Now add a Display Text component to the screen, and set its value to {!Datatable.outputSelectedRow.DoNotCall}.

Rerun the flow, and the Do Not Call checkbox reflects the value of the Do Not Call field for the selected contact.

EDIT: I re-created this scenario with the SF native Data Table component and it worked exactly the same, so the above is just to help others for whom the workaround is not working for checkboxes as this behavior is a SF bug, not an USF one. I didn't see this in Known Issues so will submit a support case.

My final workaround was to have the display text element on the screen, and put conditional visibility on it to show when both the checkbox value was true AND false, effectively hiding it from view.

FINAL EDIT: My support ticket was closed and I was told this issue would not be added to the Known Issues list. Their suggested workaround was to keep the Display Text element on the screen, hidden behind conditional visibility.