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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

table click = only some {{e.columns}} #255

Open
ryanhamilton opened this issue Nov 4, 2024 · 1 comment
Open

table click = only some {{e.columns}} #255

ryanhamilton opened this issue Nov 4, 2024 · 1 comment

Comments

@ryanhamilton
Copy link
Contributor

user-ar user -sid

  • When clicking on a table, only few elements got passed in the {{e.columns}} variables, would be great to have all columns values passed.
@ryanhamilton
Copy link
Contributor Author

user-ab

When an interactive table is clicked, the variables in memory populate inconsistently with each click; some clicks in the table will result in extra fields from the table being held as variables in memory, while clicks on different rows in the same column on the table will not have those extra variables stored. E.g. when I click on row 1 in table X, X.FieldA will be populated and visible in the debug panel, but when I click on row 2, X.FieldA will disappear from the debug panel and any downstream queries will use the stale value of X.FieldA in row 1. This makes the table interactivity feature unreliable to base drilldowns and other user features on. Could this please be fixed? In general, it would be good if there were more optionality on the fields/variables that can be populated in memory given a table click, instead of just the first few fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant