Solved! Go to Solution.
Do you have any suggestions for workarounds when combining feature classes, such as with the merge or append tool. For example if I have 2 feature classes, each with one feature that has a document attached and merge them into a new feature class, as noted the attachments are lost. However, if I re-add the attachments to the _ATTACH table using the append tool, the relationship class says they both belong to the feature with ObjectID = 1. That is to say, the first record in the attribute table gets both attachments, while the 2nd gets none.
Similarly, If I append one dataset to the other, the target's attachments are maintained, but the input's are not. Append the input's _ATTACH table to the targets again assigns the input's attachments to the target's feature with ObjectID = 1.
Any ideas on how to work around this (especially with a scaleable solution), would be greatly appreciated.