Collector and Tables Relationship class

[SiranErysian2]

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?

[deleted-user-qpvAI3Fo0MKR]

Got the invite, checking now.

[SiranErysian2]

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.

[SiranErysian2]

Joshua,

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.