Say I have a Feature Class and a Stand alone table set up with a Relationship Class
Say this is an inspection based Feature CLass....Say hydrants. I inspect these locations once a year.
I have the relationship class there to hold the historical records of the inspections over time.
How do I add records to the related table? If I add a record it creates a New Record in the Hydrant table...but how do I apply edits nand new records to the related table to house the historical records?
Can I edit the historical table in ArcMap? ArcGIS online? THanks
So I created a Relationship class on the Hydrant FC and the Historical Table.
Carnality: 1- Many
Notification: Forward (origin to destination) (Hydrant FC to Historical Table)
I didnt setup any rules at this point in the Relationship Class.
I can identify and see the related records...I can edit the related records...BUT cannot figure out how to add a new record to an existing FC point. Any thoughts? Is my Carnality set incorrect? How is this accomplished.
In a simple relationship, related objects can exist independently of each other.
In a composite relationship, destination objects can't exist independently of origin objects, so when the origin is deleted, the related destination objects are also deleted in a process called a cascade delete.
In simple relationships, getting this correct is critical. This is because when you delete a record in the origin class, the simple relationship class finds the matching records in the destination class and sets the value of their key fields to Null.
Yes I can add a new feature to the Hydrant FC no problem and it adds a record to the historical table.
But I want to add multiple records to the Historical table relating to that single Hydrant.
That make sense?
The Historical table is simply a stand alone table...no geometry.
And? That is how it is supposed to work. If you want to add an additional record to the table, edit it too. Just be sure to put in the correct value in the key field and you're good to go. (BTW, yeah, I know what a table is... Thanks.)
I was not implying that you did not know what a Table was...no need to get snippy.....just trying to point out that the related object was not another FC with Geometry but rather a table, if that were to affect things.
I was hoping for something a little more automatic....
So what you are saying is:
- that I have to actually figure out what Key field I am dealing with in the main FC
- Go back to the related table and add a new record and manually type in the ID from the main FC record I am dealing with.