QuickCapture Failed to Send some of the records on two separate devices

[kmsmikrud]

Hello,

We have been using QuickCapture for a number of years for the same project and can't remember any issues for uploading data points after being offline since 2020. Today however 2 of the surveyors are having issues. One of them still has 39 records on the device and the other has 272 records. The one with 39 remaining had most of them go thru and upload to AGOL. The other with 272 remaining only had a few send to AGOL.

They have tried to use the email option which fails on the iOS device (iPad and an iPhone), so they used iTunes to download the .qcr -> .zip -> .sqllite files but now we are stuck. I am viewing in ArcGIS Pro but I'm not seeing any geometry. I am able to view the table and see the missing 39 records in the case below. In some cases there is an error code: 1003, description: Operation rolled back and other records unknown error.

I've been searching for how to get these records upload to AGOL but could use some help. It would be really great to also know the cause of the errors.

Thanks in advance!,

Kathy

I

[kmsmikrud]

Hi, 

I also started a tech support case to assist with this issue and in the interim continued to search on how to recover data from QuickCapture that failed to send. I did find a similar post from @SFM_TravisBott who had luck just accessing the data directly from the .qcr file using ArcGIS Pro. Is this still possible with ArcGIS Pro 3.2.x? When I look in the Catalog pane for the .qcr file its like ArcGIS Pro doesn't even see it. I tried to use an ArcGIS Pro 2.9 and it does show the .qcr file but that is on an old computer that is having some issues, but it does actually recognize it.

We will keep trying on our end, but if anyone had info from QuickCapture data recoveries recently that would be much appreciated. 

Thanks,

Kathy

[JohnathanHasthorpe]

Hi Kathy

The .QCR file requires an add-in for ArcGIS Pro, and this add-in is no longer supported.

The current recovery steps are documented here: https://doc.arcgis.com/en/quickcapture/help/troubleshoot-capture.htm

The workflow involves using sending the records from the Windows version of the application.

Could you email your .QCR files to QuickCapture@esri.com ? happy to review them for you.

Thanks

John

[kmsmikrud]

Hi John,

Thanks for the information on the .QCR files and recovery steps link. For some reason in all the searching I didn't land on that page.

My coworker was able to use the recovery method and submit 39 records using the QuickCapture Field app windows version. However they were not able to get the 272 records from the other device to send successfully. I did send the sqllite files to the QuickCapture@esri.com email earlier this week. Thanks so much in advance for assistance. It would be great to figure out the issue that is prohibiting the records from sending. 

Thanks,

Kathy

[kmsmikrud · Accepted solution]

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 QuickCapture@esri.com 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