We're deploying Field Maps for a client who will access the map and forms while out in the field. The underlying data comes to us via CSV tables and I'm trying to figure out the best way of updating the feature layers in AGO when we get weekly updates from the client. Some assumptions are that not all records need updating and that not all records in AGO should be updated since they're marked as 'in progress'. These 'in progress' records are from users who did not complete the whole form, but will do it at a later time, possibly after a planned data update.
Once thought was that I would filter the base FL to records that have been edited (per Editor Tracking), then use python to append the data updates from the client. But I will also need to accommodate for the records I'm keeping in the FL so that they're not overwritten or duplicated.
I'm curious to hear from others who deploy Field Maps about their data update strategies and ETL process. Data has to be current and there's a constant extract of edited records back to the client and import of new/changed records from the client.
