We had deleted one submission, and when we exported the excel data, we found that the data in the excel export still had that deleted submission. We are not able to export the latest data in the excel format, however when we exported in csv format the data were the latest (without the deleted submission).
Any help as to why the data in excel export is not getting updated? The help regarding this will always be appreciated, thanks.
Could you share with us the screenshot of the difference between the csv export and the xls export. It should help us better understand your situation. Would you also mind letting us know the server you are using.
We have kobo installed on our own server.
Also the difference is of the number of submissions, e.g. lets say I have a form with 2 submissions, when I delete a submission and download the excel it still shows 2 submissions. But when a day later, i try the same export, it has the updated data with 1 submission.
There must be some sync issue that persists of which we are unaware of?
Thanks.
Hi @Kal_Lam, we checked the installation, and we couldnât find anything in the installation that might be causing this issue.
Also we found that a xls folder is created under the exports folder in kobo_media_uploads in .vols folder, we tried deleting the existing file, and then too the URL didnt work, we are using this url to export data â â{kc_base}/api/v1/data/{formid}â.xlsâ
We tried exporting again using the Kobo REST api - https://{kobo_domain}/api/v1/data/31.xls
Here we found that the data in the newly exported excel file is still the same, it did not change
Due to this, we are still getting the stale data, no new excel file gets added here, and every time we export the data using REST excel, we get the same stale data.
We also found when we delete the existing excel in the âExcel Export in the Legacy Projectâ page, the new export works properly.
We also found that this issue exists only when the submission is deleted, if the submissions are added, or updated the newly exported excel actually contains the updated data.
These were how the issue was replicatedâŚ
Just wanted to know if we are missing anything here? Thanks!
Any Help would always be appreciated.
This is probably how the API is designed (or it might be a bug). The best way to proceed in this case would be to use Power Query in excel to pull the data from /api/v1/data/31 and load it as a table.
Thanks for suggesting this, but we tried this too, and the result was the same, because the source is not getting updated anyway. So it didnât work either.
I am using this on a daily basis and I can confirm that it works for me. If I remove a submission from kf, it does not get pulled to the excel sheet after update.