Latest Contributions by kmsmikrud

Update 2  (12/19/2024):  We did hear form the QuickCapture team and had a chance to discuss some of the issues. I'm sure their inbox is quite full and we do so much appreciate hearing from them. thank-you!  Now in reflecting back some of our issues was a combination of the incorrect arcade expression being assigned to a field in the QuickCapture Designer (just accidentally selected the wrong expression) for a few buttons. I've since learned a better way to select all the buttons at the same time and apply the expressions to the fields to reduce user error. I also understand the way records send has also been updated in that the record with an error will not inhibit subsequent records from sending.  In addition, another arcade expression which was a date as text populating in unix format was fixed in the QuickCapture December update. The arcade expressions are great improvement and will save on post-survey processing. The update to not have duplicates allowed is a also a big improvement where our workflows are offline and in some cases when in service and not the best signal for sending data will not have the duplicate records. Thanks QuickCapture team.   Update: We never did hear from [email protected] after sending the data in the email and tech support was not familiar with the recovery process so in terms of time we spent a good deal of time working to recover the data ourselves. Even going thru the process I'm not sure why some of the records did not go thru from the one device. There were clear errors where the wrong arcade expression had been selected for a record and so the field length limited that record, but the other records just showed 'unknown error' or similar.  We were able to finally get the 272 records from the other device into AGOL. This took some time using DB Browser for SQLite to view the records moved from the device (iPad) to computer using iTunes. We then changed the .QCR to .zip, extracted files and viewed the extracted sql lite database in DB Browser for SQLite. In reviewing records updated the records that had the field length error and then changed the status from -1 to 1. We downloaded QuickCapture for Windows and changed the default projects_db.sqlite file in the QuickCapture Windows install director with the corrected database. Opened up QuickCapture in Windows and in loading the project the program would find the records that hadn't been submitted in that project and try to sync. It seemed a number of records would successfully upload, but then a number would not. So then would repeat the process correcting a few records in DB Browser SQL Lite and trying again. This eventually moved all the records, but again some records only had the unknown error and no obvious data error. All I can figure is that the points with the data field length errors stopped the records recorded after from syncing?  I'm wanted to document this in case it happens again. Tech support was great but it was a surprise that they weren't familiar either with the .QCR -> .zip -> .sqlite  process.  I also have to say Field Maps and the the mobile geodatabase and offline recovery seems so much more straightforward at least in my experience. Hopefully this information is useful or will help my own future self. Thanks, Kathy ... View more