- Home
- :
- All Communities
- :
- Products
- :
- ArcGIS Enterprise
- :
- ArcGIS Enterprise Questions
- :
- Relate shows wrong record in web map.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Relate shows wrong record in web map.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning,
I'm having an unusual issue with related tables in services consumed in a web map. Despite the Global IDs of the primary feature matching correctly with the Related IDs of the associated tables, the form showing up as being related is not correct. Here's the setup:
Enterprise 10.8.1
Feature service published from Pro has multiple instances of a single feature class "Post Inventory" which has relates to five difference forms that correspond with street signs, as they descent in height down the post in the real world (Main Signs, Second Signs, etc). The post Inventory feature class is duplicated in the Pro .aprx and joined to each form (so there are six total, one just the feature class and then one for each sign hierarchy) so that the sign type in the form can be used to drive symbology.
Published service is used in a web app (WAB 2.23) via web map, so that users can edit the information of the post or the actual signs themselves.
Okay here's the problem: Everything is working correctly in the publishing ArcPro document. All attributes match correctly based on the matching Global IDs (See first three attached photos "Pro ___") Photo 4 is an example of a location where the issue is occurring though it seems to be feature-class-wide. When just examining the attribute tables in the app, things seem fine. See photos "App Main Sign and App Second Sign to see that attributes match what is expected based on the Pro doc. BUT, when clicking on the Post Inventory and scrolling down the the related tables and selecting "Main Sign Form" it does not recognize a a related record. When doing the same with Second Sign Form, the related record is totally inaccurate, giving a result for the wrong street (See "App No Relates" and "App Second Sign Edit Error."
No changes have been made to the Pro doc, feature classes or related forms. Interestingly, fixing the issue is as simple as overwriting the feature service. The issue occurred a couple of weeks ago, I overwrote the service, and everything was fine until this morning when the issue occurred again. I overwrote the service before writing this post and it's fixed again.
So, any thoughts on what might cause a service to display incorrect related forms when the underlying data is accurate and hasn't changed? Server restart? Resource instability?
How
