@okenk While updating commercial 2022 values in commit d085cc3 I noticed some issues with read_sheet.
If we enter in a google sheet id as the long http address (e.g. https://docs.google.com/spreadsheets/d/17.........) and then we update that file, the id still points to the old data sheet, even if it was overwritten in google drive. Thus, we aren't reading in any recent changes.
My solution is to use the file name within googledrive::drive_get() as the id (see here) , which allows reading of the new data automatically. I tried to change this in any script Ive used, but I notice it in canary_surveys_workup. I suggest changing those to ensure any new data has been pulled properly.
@okenk While updating commercial 2022 values in commit d085cc3 I noticed some issues with read_sheet.
If we enter in a google sheet id as the long http address (e.g. https://docs.google.com/spreadsheets/d/17.........) and then we update that file, the id still points to the old data sheet, even if it was overwritten in google drive. Thus, we aren't reading in any recent changes.
My solution is to use the file name within googledrive::drive_get() as the id (see here) , which allows reading of the new data automatically. I tried to change this in any script Ive used, but I notice it in canary_surveys_workup. I suggest changing those to ensure any new data has been pulled properly.