Inspection Not Saving To Related Tables

Question

Hello,

I am having a problem trying to create a pole inspection map that I can use with the Collector app.  My issue is when I create a new inspection it does not save to the related table.  I wanted to be able to maintain an "inspection chain" so I've tried to set this up like the hydrant inspection example with a pole feature class and a related inspection table but it just doesn't seem to be working.  Is there something I'm missing?  I am using ArcGIS desktop 10.3.1 standard.

This is generally what I have so far...

A pole feature class with roughly 128k poles and a blank inspection table that is related (1-m) by a common GUID field (see attachment).

If anyone has any suggestions it would be greatly appreciated,

Josh

Clipboard01.jpg

SloanSelden.png

JoshHabel · Answer

Thanks that seems to have worked!

Josh

KevinBurke · Answer

Hi Josh,

Thank you for that information. I see that you do have the correct field types, however they are in the reverse order. For the poles layer, that should contain the Global ID field and the inspection table should contain the GUID field. The reason being is because the poles layer is the origin and the inspection table is the destination therefore the Global ID's should be generated for the existing pole features. Then when a new inspection is created for that pole, that value should be copied into the related GUID field to link them together. That gets done automatically when adding the related record in Collector.

But in general, the fields names don't really matter it's just the field types that do and the direction of the relationship as far as which is the origin and which is the destination.

For testing purposes, I'd recommend creating copies of the pole layer and inspection table just to test out that relationship.

Thank you.

-Kevin

JoshHabel · Answer

Kevin,

I double checked how I have the relationship set up and the Feature Class GlobalID field is actually a Guid Data Type that is for some reason named GlobalID and the table GlobalID field is a GlobalID Data Type that is named GlobalID_1.  So it would seem that i do have a Guid related to a GlobaID.  Is there a specific naming convention for the field names that it is looking for?

Thanks,

Josh