Select to view content in your preferred language

how to combine feature class with attachments with related table data with attachments

695
0
10-03-2022 02:07 PM
L77
by
Frequent Contributor

My coworker created a feature class and collected stormwater outfall data with attachments using Survey 123. Now that dataset is a feature class with an attachment table. Every time she re-visited a location she would create a new point on the map so there are duplicate locations where the points on the map are not stacked but are close spatially, and the site id is the only thing that shows that it is the same location for multiple visits. Each point has tabular data in the attribute table and photos in an attachment table.

This year she created a feature class for all of the outfall locations and is using a related table for each site visit and there is an attachment table for the photos.

How do I combine the previous years data with the current years template?

So far I used the table to table tool to convert the previous years site visits from a feature class to a table.

Then I used the merge tool to merge the two related tables together.

Then I used the merge tool to merge the attachment tables together.

Then I made a copy of the outfalls feature class and was going to create a relationship class between it and the related table that had the merged data but I wasn't sure what to do about the global ID and GUID and what to put in the "create relationship class" tool.

This is the feature class point layer of the Outfalls

The IDFull is the only field that is the same in the point layer and the related table, but it also had a global id field, (This is the only point layer).

Lorraine77_0-1664830208012.png

This is the merged related table. There are global id's for the previous years site visits feature class, and from the current years related table data.

The Full_ID is the only dataset that shows which outfall location the data was collected for the previous year because they didn't use the same point on the map so each time they went out they dropped a new point so it doesn't align spatially but does based on this field.

There is a GUID field  but that is only populating for new data collection in the related table.

Lorraine77_1-1664830378221.png

This is the merged attachments table and it has a global id and a REL_GlobablID

Lorraine77_2-1664830613878.png

As a side note there isn't any data that has been collected for this year using the new related table, but my coworker created a bunch of new fields she wants to use.

Her goal is to see the previous years data in the current years related table so she can use previous years information to auto-populate information in the survey.

Sorry I know this is confusing. Let me know if you have any advice or have any questions.

I'm at the point where I think I need to create a relationship class between the outfalls point layer, and the related table and the attachment table, but I am concerned that I might mess up the global id's that show which datasets go together.

0 Kudos
0 Replies