Hi,
In the current AGOL Experience Builder (Nov2023) , the layer list widget has a new option called "View in Table" - located is next to ZOom-to, ^ Increase transparency , details, etc.. - that's great.
When end-users click on "View in table" , it adds the layer to the table widget correctly except it is missing the "filter by selection" button inside the table widget.
Also other issue, if we click "View in Table" repetitively, it keeps adding the same layer to the Table widget
Thank you
_______________
side-note : the ^ Increase transparency and v Decrease transparency is a bit clumsy. Wouldn't it be nicer to have a slider?
______________
Also in normal Table Widget operation, why don't you immediately apply the "show selection" by default if that button is not greyed-out (indicating some selection is made).
If selection is made on this table layer, then assume "show selection" by default. (not show all) !THINK: if someone selected features on a layer and the table is displayed, don't you think they'd prefer seeing those selected features as defult, instead of _all_ ?
Thank you for the feedback.
A sheet opened by "View in Table" is indeed a temporary copy of the original data. It is generated dynamically and does not support selection, which is why you won't see the Selection/Clear selection buttons on the panel.
As for the number of times you can view the data in the table, there is currently no limit. You can view it as many times as you need without any restrictions.
Do these behaviours raise any issues in your use case? It would be great if we could discuss it with a clearer use justification.
Also in normal Table Widget operation, why don't you immediately apply the "show selection" by default if that button is not greyed-out (indicating some selection is made).
If selection is made on this table layer, then assume "show selection" by default. (not show all) !THINK: if someone selected features on a layer and the table is displayed, don't you think they'd prefer seeing those selected features as defult, instead of _all_ ?
Apart from single selection, table also supports multiple selection. If the table switches to the selected view after making a selection, users will not be able to make further selections. Additionally, if users deselect records from the selected view, those records will be removed.
Considering the multiple selection experience, the decision of whether to show selections is left to the users.
side-note : the ^ Increase transparency and v Decrease transparency is a bit clumsy. Wouldn't it be nicer to have a slider?
@FredericPoliart_EsriAU As for the side note here -
Yes, I agree that it would be better for the user experience, however, the Map Layers widget utilizes API which does not provide this capability currently. And I do not think there will be a change in this UIUX soon, unfortunately.