CSPro Users Forum

Given what I wrote before you could make a change to the function CreateUniqueZipPath, so it returns just the file name. This will make constructing the destination path for the zip straightforward. function string CreateUniqueZipName() CreateUniqueZipName = maketext ( "DataBackup-%d.zip" ...

If you were synchronizing to a server, I would rather leverage synchronization to backup and restore data. However, I have written logic to backup and delete data files locally in the past. To restore the data you'd need more of less reverse the process. // ------------------ // ------------------ B...

I could imagine a couple different approaches that each require an additional post-data collection step. Idea 1: Remove the decimal from the value sets, and add it back later. (Did not do activity) | 0.00 15 minutes | 25 20 minutes | 33 25 minutes | 33 Then the additional post-data collection step i...

Just wanted to give you a quick update. When I used the your data and extracted dictionary I start to zoom in on Timor-Leste (or at least that part of the world) and then the view jumps to Africa. I've passed on this report for a closer look. Thanks for your patience.

I was able to reproduce the issue and will need to look into it further. My suggestion is to store the values as whole numbers and then take an additional step to convert them to their decimal value.

Sure. If you're already sync'ing to an FTP server. How about downloading the data using a utility application.

syncconnect: https://www.csprousers.org/help/CSPro/s ... n_ftp.html
syncdata: https://www.csprousers.org/help/CSPro/s ... ction.html

That makes sense. The current version of CSWeb does not support PHP 8.0. We are working on that currently.

When I tried to open the CSDS I couldn't. It complained about the datetime, so I the made the following edit to the csds (swapped periods for colons): "buildTime": "2022-12-06T08.00.44Z", to "buildTime": "2022-12-06T08:00:44Z", and I was able to open the file....

Can you attach the sync log? Also, the app package newly built and deployed after the new installation?

0x0A is a newline character which isn't allowed in the header. It's possible it needs to be stripped before sending. We'll look into it, but hopefully this is just a one-off-issue for you. Thanks for reporting the issue.