[GIS] Creating relationship class with ArcPy using GlobalID

arcpyerror-000800relationship-class

I'm trying to create a relationship class with Python using a GlobalID.

When I use Python it gives me the error:

Failed to execute. Parameters are not valid. ERROR 000800: The value
is not a member of GLOBALID. Failed to execute
(CreateRelationshipClass).

When I try to use the Create Relationship Class tool through the Toolbox, I get the same error. If I select GlobalID as the primary key, it will ONLY let me select a GlobalID as the foreign key. It will not let me select a GUID of my choice.

But when I'm in ArcCatalog and right click the Dataset and go to New > Relationship Class…

It works!

What's wrong here?

Best Answer

Well I found out the bug that was logged for this is NIM082537.

You can follow the status of it here: http://support.esri.com/en/bugs/nimbus/role/beta10_1/TklNMDgyNTM3

It might be necessary to copy/paste URL into address bar.

Related Solutions

[GIS] create relationship class with stand alone python script

Since you're setting your environment variable env.workspace, I think you may be misleading the tool by re-stating the name of the database in your variables: origin_table,destination_table, and relationship_type.

What the tool sees this:

origin_table = "a.gdb\a.gdb\Trail_meta"
destination_table = "a.gdb\a.gdb\trails_mfg"
out_relationship_class = "a.gdb\a.gdb\t3meta"

Redefine your variables to this:

origin_table = "Trail_meta"
destination_table = "trails_mfg"
out_relationship_class = "t3meta"

Also, it looks like all you want to import is the env module from arcpy, you can do that by simply using the from arcpy import env command instead of importing the entire arcpy module first. This may save you a bit of time when running the script.

[GIS] Foreign Key is not added to destination table after the creation of a relationship class

@vince:

Relationship classes tell the geodatabase about existing relationships. The key columns need to exist. There are many reasons why the columns should be created with the table, most importantly, to avoid the fragmentation caused by adding a column.

If you don't define the relationships in the geodatabase (not all of which support the concept of foreign keys, so they are optional), then you don't get the benefits of relationship classes.

@BenSNadler:

The foreign key options in the dialog filter based on the input field data type. If the foreign key field does not exist you need to manually add it. I suggest using the arcgis tool add field management to be clear. The geodatabase relationship does not place any database level constraints on the field. To the DB it is just a regular field.

I added those fields manually and then created the relationship classes.

Best Answer

Related Solutions

[GIS] create relationship class with stand alone python script

[GIS] Foreign Key is not added to destination table after the creation of a relationship class

Related Question