Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
andrewmondy opened this issue Nov 30, 2023 · 3 comments
Assignees

Comments

@andrewmondy
Copy link

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.
Screenshot 2023-11-30 at 4 45 24鈥疨M
Screenshot 2023-11-30 at 4 46 18鈥疨M
Screenshot 2023-11-30 at 4 46 04鈥疨M

Debug Logs

If applicable, please insert debug logs here

@andrewmondy
Copy link
Author

Screenshot 2023-11-30 at 5 00 31鈥疨M
Screenshot 2023-11-30 at 5 00 37鈥疨M

@ericrsmith35
Copy link
Collaborator

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
Copy link
Collaborator

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants