Select to view content in your preferred language

Symbolize using arcade relationship class functions

72
1
Wednesday
Status: Open
lmurrayADOT
Regular Contributor

It would help a lot to be able to build an arcade expression using the FeatureSetByRelationshipName or FeatureSetByRelationshipClass to reference a value in a separate table.  The Join View option doesn't work well because if I want to make a schema change in the parent layer, I have to delete the join and then recreate it after the change, which creates a new feature service and causes me to recreate any layers and repair any maps I used that join in.  The expression would run on the fly without having to create a separate layer.

1 Comment
VenkataKondepati

Strong idea. Arcade already gives us FeatureSetByRelationshipName/Class, but the real gap is being able to use it cleanly in more places (pop-ups/labels/symbology) as a first-class “join-on-the-fly” pattern. Join Views are painful operationally—any schema tweak forces a rebuild and breaks downstream maps/apps because the service identity changes. If Arcade could reliably pull related-table values on demand (with good performance + caching/limits), it would reduce duplicate layers, simplify governance, and make schemas easier to evolve without collateral damage.

– Venkat