When using Data Pipelines to migrate data from one hosted feature layer schema to another hosted feature layer schema, there needs to be a way to maintain attachments (much like in the Append geoprocessing tool in ArcPro).
Our team collects biological and cultural data for the government, and these data must ultimately live in a hosted feature layer that meets the spatial data standards of this government entity. Because of the somewhat complex schema nature of this schema, configuring Field Maps Smart Forms or Survey123 Forms to feed directly into this schema is unrealistic. Additionally, the schema is difficult for non-GIS/data-users to navigate or understand and most of the biologists/archeologists that are QCing the data have no little to no GIS experience.
Our workflow to overcome this challenge is to have simple hosted feature layers where our field forms are sending data to. Our biologists/archeologists review the data for accuracy in these simple schemas, then the GIS specialists migrate those data to the standardized schemas where they will live indefinitely and be accessible to our governmental partners in a Hub environment.
We love the idea of using Data Pipelines, and have created a tool to make this migration possible, but we lose the attachments when the tool is executed. We won't be able to incorporate Data Pipelines officially until we are able to preserve attachments.