Hello all,
I am having difficulty with the modify associations view. In the junction-junction section of the connectivity tab, I am not able to change the display name of connected records. So I cant tell which feature each row relates to. And also when I right click, the "select" option doesnt actually select and there is no option to "flash".
Using arcgis pro v2.9.5 and UN v5. Any advice? tia
Solved! Go to Solution.
You can adjust the display by changing the display field:
On 3.2, there is a flash on the right click and select does work. Maybe it was fixed in 2.9.9
Listing the Junction Object tables with def queries does cause issues with the association tools. We do not split them up with def queries and just leave them as one table. They are adding subtype group tables to 3.3 to resolve this issue, but for now, one table in the map is the best option.
You can adjust the display by changing the display field:
On 3.2, there is a flash on the right click and select does work. Maybe it was fixed in 2.9.9
Thanks Mike, I can see thats how it should work but in many cases thats not how the app is working unfortunately. Im not sure if this is a common/known issue or some other blocker is present.
You can see in the two snips the modify associations display is different despite the same settings.
What do you mean repeat in the map Mike?
Do you have a layer in the map pointing to the same target Service Layer more than once. Maybe it is repeated with a def query? Subtype Group Layers count as one layer
Thanks Mike. Yes I do have multiple layers managed w/ definition query including the Electric Junction Object table from the above screen shots. Is there possibly something Ive set up incorrectly, or some best practice I should follow to allow Modify Associations tool to work with this config?
Listing the Junction Object tables with def queries does cause issues with the association tools. We do not split them up with def queries and just leave them as one table. They are adding subtype group tables to 3.3 to resolve this issue, but for now, one table in the map is the best option.