Related Tables in Collector: Spoke to Jeff Shaner and others at ESRI Conference 2018 and it was suggested that I use the Global ID field as the Primary key when joining a stand alone table with point feature class in map service published for Collector. Is this when the Global ID field is established? My table does not have a global id field. I have another field that I proposed to use that is in both the table and the feature class attributes. Why Global ID is suggested to use? Do I need to create a relationship between the table and the feature in the geodatabase for the table to appear in Collector?
To answer your first question, if you publish your data to AGOL without a GlobalID, then a GlobalID is automatically generated. It is suggested as a primary key because it is system generated, is unique and
In order for the related table to appear in Collector your workflow should be:
Feel free to PM me if you have any questions on this one.
Joshua,
I did all of the above and it did not work. The relationship was created from feature to tabIe but I want to have all the information in the table that includes many records for the points, in the feature to reflect that information when identifying the point feature. I don't see that when I click on the points in Arc Map mxd.
I went ahead and published my map to AGOL. I used the feature class as my origin table/feature class and the related table as the destination table/feature class. I see the feature class and table. I see the Global ID field. GUID field in related table is not populated. When I click on the features in the pop up I see at the bottom with Edit and zoom, Show related records (in the table) but when I click on that I get window that says No Results Found. Also, there is a field in the related table that shows the relationship class but it has a lock on it. How will my users see the information in the related table in Collector? I am making progress but still need your help.
Thanks you for your response. I have been working with your suggestions.
I posted some information on the Geonet site but I want to include more information and screen shots if possible.
I opened my map in AGOL and Collector and see my features. I see the related table
Clicking on a point in the map show the pop up.
Clicking on Show related Records
The related table has a field that is supposed to show the previous year’s measurements for each point record. There are more than 1 year that I wanted to show thus the 1 to Many relationship.
But there is nothing there. Also it is locked. Everything is shared.
It made sense to me when creating the relationship class that the feature was the origin table/feature class and the related table the destination. See below.
Should I switch them?
In Collector I see the related table at the bottom of the Details for a feature. There is View> but it is empty. This is where I would like my users to see the related historic information for the particular feature to compare with the data they will be collecting in the field. There is New> which has all the fields that are included in the feature class which was used to edit the information last year. So I would like to edit here and just have them view the related table with the information at the bottom of this list. However, when I click on the edit function to collect information on a point, I do not see the related table. I guess that’s Ok but where should the edits be captured? I have to strip the information from last year’s collection in the feature class every time and re-publish the map. At the user conference, I spoke with some of the Collector developers and they suggested just adding information in the related table. But some of that information will always be the same and I would make those fields not editable.
I hope this gives you some idea of what I’m trying to do. I hope you can continue to assist me.
Thank you.
Siran D. Erysian, M.A., GISP,
Research Analyst II – GIS
Think Spatially
Department of Water Resources
3374 E. Shields Ave, Rm. A-1, Fresno, CA 93726 (559) 230-3312
Siran.Erysian@water.ca.gov
So the way the Relationship Class will work is this:
When you create a new record in the Related Table, the GUID will be populated with the GlobalID of the Feature it's related to.
The reason you aren't seeing any records when you click on the feature is because there are no records related to that feature until you create them.
If you're wanting to related existing records to the features, you'll need to create the relationships manually in ArcMap using GlobalID -> GUID, or, alternately, use some existing key(s) that relate the table to the features.
I'd suggest reading up a little on Relationship Classes before doing any more work.
I want to relate existing records to the features and I did use the Global ID and GUID in the relate as you saw in the screen capture. I want to see the existing records, not create new ones.
I am familiar with relationship classes and have done them several times successfully. Probably what I need to do is use a field that already exists in both the feature class and the related table so it will work. But everyone has so far suggested using the Global ID and the GUID which I had done manually in the mxd but there are no related records. It didn’t make sense to me to use those fields.
I’ll try another field and let you know the result.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
