I'm struggling with a problem and I feel like I'm missing something obvious. I'm trying to migrate a non-spatial table with attachments to a feature class with those same attachments. I'm working in ArcGIS Pro 2.9.1, and the non-spatial table has the X and Y fields. I've tried several things...
Any recommendations without going back to the original attachment images, creating new match tables, etc?
Solved! Go to Solution.
Going back to the original images may be quicker 🙂
But it is possible...
1. In your original table, make sure you have some sort of unique ID field
2. In the original attachments table, join this ID field to the attachment table using objectid
3. Use Display XY data as described on the original table
4. Enable attachments on the now created new feature class
5. Add the ID field to the new attachment table
6. Append the old attachment table to the new feature class attachment table
7. Join the objectids from the new feature class to the new attachment table using the ID field
8. Recalculate the parent objectids
9. Delete the excessive fields from the feature class
Your new feature class now has the correct attachments!
Going back to the original images may be quicker 🙂
But it is possible...
1. In your original table, make sure you have some sort of unique ID field
2. In the original attachments table, join this ID field to the attachment table using objectid
3. Use Display XY data as described on the original table
4. Enable attachments on the now created new feature class
5. Add the ID field to the new attachment table
6. Append the old attachment table to the new feature class attachment table
7. Join the objectids from the new feature class to the new attachment table using the ID field
8. Recalculate the parent objectids
9. Delete the excessive fields from the feature class
Your new feature class now has the correct attachments!
Yes, this worked! One of my problems was that I had GlobalIDs in the original tables, which were causing problems when trying to migrate attachments to a new feature class. But after creating a new GDB and deleting GlobalID, this worked perfect. Thanks!
This is what I ended up with, which worked well if a little clunky.
To add on some further help for the next person coming along also...
We had a feature class with photo attachments populated using field maps but surveyed accurately separately to the app. So we had a X, Y and Z fields to which the data needed to be shifted to put it in the correct location. As above, the 'XY Table to Point' tool worked fine for this but didn't carry across the attachments. We've created the attached (pun intended) toolbox with each tool working together to update the locations of data and carry across the attachments (for some reason it wasn't working within the single model for the XY Table to Point part but splitting it worked). This solution is based on the above methodologies.