I am preparing some historic data to migrate from data entry and storage in MS Access to Survey123.
My historic data are in a single, flat feature class. We want to share the data with a partner organization, but our data sharing agreement stipulates that we "fuzzy" the location data to three decimal places. We also want to filter the shared data to a particular time range, and filter to certain records. This seemed like a job for a hosted feature class view layer.
I can set up a new survey from my feature class, using the historic data to create the appropriate fields and field types in Survey123 Connect. I created a hidden repeat within my survey to create a child layer that contains a rounded geopoint, and copies the fields I want to share from my parent feature class. This is great - I can then create a hosted feature class view layer from the child layer, filter to the time and records I want, and share this with our partners.
The only hiccup is that I can't figure out how to populate the child layer with existing historic data. I can create the child layer separately in Pro, but when I try to append the child layer to the parent layer in AGOL, the two are not linked the same way new survey entries are.
Any ideas for how to append the historic data in the child layer? Maybe there is a way to force the feature class to recalculate any fields that are caculations? Or - how to do this a different way? I could simply use a feature layer view of the original feature class if only I could add a calculation on the geopoint feature!
Here's a screenshot of my test Survey's xlsx form. Maybe there is a way to force the child layer's data to re-calculate? The child layer will only ever have copies or calculations of fields that exist in the parent layer.
Solved! Go to Solution.
Nice write up. Note you can just use the append tool in Pro to the hosted AGOL layer. No need to zip up the files and use update data. Pro can use a AGOL layer just like a GDB now. This makes it easier to do your calcs also. Always make a backup first.
@DougBrowning I did try that but kept getting errors for some reason. It would have been helpful - I see there is an option there in the Environments tab to preserve GlobalIDs!!
Yes that one is new but I heard there are a number of issues with it. I think if you try to export then reimport it does not work out but not sure.