Unsupported relationship type when publishing

[KirkJones]

I am trying to create a survey in connect version 3.11.123  using an existing feature layer.  There are two related tables and both the primary and foreign keys are the globalid.  When I go to publish I get an error stating "survey123 unsupported relationship type esriFieldTypeGlobalID in key field globalid for table globalid".  I haven't really found anything in my searching for solutions.

 

[DougBrowning · Accepted solution]

The related table calls the field parentglobalid.  You can have other relationships but this one has to be there i think.

Hope that helps

[KirkJones]

I apologize for my lack of understanding.  So does that mean I need to add the parentglobalid field to my table?

[DougBrowning]

yes add the field parentglobalid  string 255 to the child table.

[KirkJones]

Thank you

[ShariForbes]

This solution worked; however, the "parentglobalid" has to be a GUID field, not a text field, otherwise you cannot make a relationship class with two different types of fields. 

[IanMackenzie]

I suspect the issue may be using the same name for primary and foreign key (primary key in/of the parent table and foreign key of the parent in the child table).  These names need to be different, e.g. "GlobalID" as the primary key of /in the parent table, "parentglobalid" as the foreign key of the parent table in the child table (see example screenshot below).  I didn't try changing the names from what was previously suggested so its also possible this is just an ESRI naming convention that needs to be adhered to.   I set both keys as type GUID.

[DougBrowning]

They do not need to be different - I use the same field name on both sides of the relationship class all the time.

It is 123 that has to have those set field names since it is coded in.