Closed pjdohertygis closed 7 months ago
This may end up being related to https://github.com/pjdohertygis/DeploymentOrderTool/issues/13
It seems Selected features would resolve the workflow, but the main limitation is that the table is highlighted and does not allow to easily copy / paste from the table. If the Button widget supported Exporting the connected data to a CSV, would that resolve the issue?
Then you'd be able to add a Export button near the Table.
This would need to be a new enhancement request for Experience Builder.
I like the idea of export csv as a button as it would be more intuitive than the current interface
However, that would just be a nice to have.
I'll show our users the interaction if we go with Select vs Filter and see what they think. It is really handy to be able to copy and paste right from the app because they have a separate excel file they paste it into.
If we implement this - let's double check performance of export over various levels of connectivity
Ok using the approach @avezina mentioned seems to work.
The table loads blank until a selection is made
And you can still copy/paste from the table! The csv download actually appears to be faster than using the "filter" approach.
Closing unless we receive feedback that this doesn't work for some reason.
Which app?
Deployment Order Tool 2.0
Describe requirements
We would like the end user to only see the table (or contents in the able) once a grid selection is made. Is there a way to only load the table once the map is clicked on? Only open the side panel once the map is clicked on? Any other ideas?
Alternatives
We could use "select" action instead of "filter" action. This makes the table "blank" until the grid is clicked on, but then the table is highlighted and does not allow for a copy / paste from the app.
We could also hide the slide panel when it loads and tell the user not to open until they click on the map?
Other Relevant Info
This is what it looks like when it loads - the table does not mean anything.
Priority impact
p0 - not time sensitive
Impact
It is just a little confusing for the end user, they will see strange results in the table and might not know that the selection has not yet been made.