Reoccuring import sync removals?
complete
Franco Valdes
marked this post as
complete
Franco Valdes
marked this post as
in progress
Franco Valdes
marked this post as
planned
Franco Valdes
marked this post as
in progress
Carisa Bailey
ah, excellent point. I forgot about the manual additions/removals. The benefit of a reoccurring import for me is to maintain a single source of truth, so if data doesn't write back and forth it is really just a bulk upload. Is there a way to export map markers/boundries to CSV to help keep the reoccuring import more current and account for manual additions and removals? an active field would make more sense in that case for the export file. I see how this can get complicated.
Franco Valdes
Carisa Bailey: I can create a separate roadmap item to handle exports. I will say that exporting boundaries will not be possible in CSV format since boundaries are in geojson format.
This may also become a complicated task but worth doing further research.
Franco Valdes
To avoid deleting locations that were maybe added manually, outside the import process, I think the best solution will be to also include an "active" field mapping. This way, the user can toggle the active value (true or false) in the google sheet to remove it from the map.
Would like to hear your thoughts on this approach.
Franco Valdes
marked this post as
under review