Hi, I published a hosted feature layer from ArcGIS Pro which contains a feature layer and table. The two are related with a relationship class established in the file Geodatabase containing the layer and table. In the web map I can see that the two are related and I am able to add records to the related table. Though I would like to display features from the layer based on filtering of values related records. Is this possible in either the web map or Experience Builder? I tried creating a view, but I think that is static and doesn't reflect any modifications made to the source table after the view is created. I can filter the table in both the web map and Experience Builder, but it doesn't seem to carry over to the related feature class. Thank you
Solved! Go to Solution.
@joeryan wrote:I tried creating a view, but I think that is static and doesn't reflect any modifications made to the source table after the view is created.
@joeryan, if you create a joined hosted feature layer view, it is actually dynamic! It also doesn't take up any more storage space. The one thing you have to be careful with though is making sure your schema is solid. If you need to add a field or change an alias, you will likely need to create a new joined hosted feature layer view and replace the layer being used in your experience. There are more and less technical ways to get around this (some that Esri do not recommend), but just know that that problem exists.
@joeryan wrote:I tried creating a view, but I think that is static and doesn't reflect any modifications made to the source table after the view is created.
@joeryan, if you create a joined hosted feature layer view, it is actually dynamic! It also doesn't take up any more storage space. The one thing you have to be careful with though is making sure your schema is solid. If you need to add a field or change an alias, you will likely need to create a new joined hosted feature layer view and replace the layer being used in your experience. There are more and less technical ways to get around this (some that Esri do not recommend), but just know that that problem exists.