I am building a web app using Experience Builder and I have two trail layers that are views and I am unable to select them as ' Selectable Layers' for the Elevation Profile widget. I see selectable layers available that are not views (roads, utility lines, watercourses), but these are not relevant to this purpose of this widget. I tested the Trails hosted feature layer (not view), and I am able to select it. We are hoping to use the views to hide certain fields and apply queries.
Am I not seeing my trail layers as selectable because they are views? Or could there be another reason?
Thanks!
Hi @KatGIS , thank you for posting. I cannot seem to reproduce this issue with a layer view on my end.
Is there anything specific you may have configured for these views? Specific filters/queries? Hidden specific fields?
Hi @AlixVezina , thanks for the response.
This prompted to me to recreate the views, and now I can use the trail views as selectable layers in the widget!
I am not entirely sure where the issue came from in the original views though - it was a simple query (official =1), and a few non-essential fields hidden. After posting, I realized I was having trouble with the Shape__Length field appearing in the table (it was visible as pop up, but not visible in selecting to hide/display in table), perhaps related to that?
Thanks.
Hi @AlixVezina, I just reproduced this error again with the new views. The trail layers were nested into two groups (Human Use/Trails/Official Trails). It seems that selectable layers are only recognized one group in.
Hi @KatGIS thanks for letting me know! I've had no luck reproducing this issue so far. If you don't mind, please would you be able to write down the steps that allowed you to reproduce it? Starting from your hosted feature layer, through creating the view and the web map you are using? Thank you!
Hi @AlixVezina,
Here are the steps:
It does not seem to be the fact that it is a view, but just that it's nested in two groups.
Thanks!
Hi @KatGIS , thank you for the details! You are correct, it appears to be an issue when layers are nested in a subgroup. Thanks for finding this, we'll work on fixing it!
This should now be fixed with the June release of ArcGIS Online.