I really need this too. I was happy to obtain data from an another Layer in my pop up with FeatureSetbyName or FeatureSetbyID, but really disapointed to see that it doesn't work for style...
An example of where this would be useful: I have points symbolised as pie charts and I want the pie chart to show the sum of all values from the join table related to that that point. Currently with a join view, I get several pie charts on top of each other. Or similarly, I would like the size of a point symbol to change according to the sum of all values from the join table related to that that point. Currently with a join view, I get several separate points on top of each other.
Feature class with related tables gives us a clean, logical structure. Unfortunately, to symbolize maps based on values calculated from multiple fields in a related table, we either duplicate fields in feature class and table, and add code to sync values, or break up the proper relational structure of our attributes.
Use case: 1:N relate, only use most recent value. Use most recent inspection date, and inspection interval, and current date, to symbolize features needing inspection in the coming year.
I imagine there may be performance issues with this request: a related popup is singular, vs calculated symbology for everything displayed - but sometimes the symbology is worth the wait, and the mapmaker can judge whether to employ it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
