Has anybody an update on this issue?
Thanks,
Doreen
You cannot use a relate or relationship class to do symbology of a 1:M relationship. As far as symbolizing you have to convert the 1:M relationship to a 1:1 relationship. This can be done either by using summary tools, or if you have ArcGIS 10.1 or higher, by putting everything into the same geodatabase, joining the features on one field, and exporting the features to create a 1:1 feature class.
IF you are querying fields from only one data source in the relationship, then a relate works fine to select the records in the related feature class. However, the methods mentioned in the first paragraph are the only efficient way to query fields that involve the combination of the two datasets.
Of course, both of these methods do not refresh if you edit the original data, so they constantly have to be recreated.
If you are willing to use an Inner Join (only records that match in both data sources are visible) you can use the Make Query Table/. But that tool does not refresh if you edit the original data, cannot be edited, and performs badly, so it sucks. I always use the other methods I mentioned and never use this tool.
For some queries and analysis you can use cursors and dictionaries to perform the join in memory and get results, but it won't generally help with symbology without creating a new feature class..
Thanks a lot Richard for your help!!!!
Best wishes,
Doreen
Has there been any more progress on this?
My scenario is that I have a geometry layer with parks, and a table that will progressively be filled out when the park has been mowed and when it is next due to be mowed. I have set this up as a relationship class. I would like to be able to symbolise on multiple different factors, mostly timewise i.e. what parks are due to be mowed in July verse those in August ... all while keeping track of what has been done by who in the past.
In case anyone comes here looking for an answer to symbolizing by related table, here is a link to a collector discussion that resolves this question, it works in ArcMap, ArcPro and in Web apps.
Thanks Michael, very informative.
Unless I'm missing something the 2 solutions in that thread both rely on external functionality not present in ArcMap and Pro by themselves: publishing the joined/related table as a feature service (so you need ArcGIS Online or ArcGIS Server), or using DB tools to create a filtered view of the related table that ArcMap/Pro can use a 1:1 join on. Conceptually they're both the same solution.