Search found 91 matches
- August 23rd, 2021, 6:18 pm
- Forum: Synchronization
- Topic: Notes not being synchronized
- Replies: 14
- Views: 5961
Re: Notes not being synchronized
Yes. The entire api log just contains this one line.
- August 23rd, 2021, 1:50 pm
- Forum: Synchronization
- Topic: Notes not being synchronized
- Replies: 14
- Views: 5961
Re: Notes not being synchronized
The api log file says about the latest synchronization:
[2021-08-23 14:06:20] app.ERROR: Debugging build time issue 2021-08-21T13:49:40Z [] []
[2021-08-23 14:06:20] app.ERROR: Debugging build time issue 2021-08-21T13:49:40Z [] []
- August 23rd, 2021, 12:21 pm
- Forum: Synchronization
- Topic: Notes not being synchronized
- Replies: 14
- Views: 5961
Re: Notes not being synchronized
The Note is in the .csdb file on the tablet, but not in the .csdb file downloaded from the server by Data Viewer.
So it seems the error occurs during synchronization.
So it seems the error occurs during synchronization.
- August 23rd, 2021, 11:39 am
- Forum: Synchronization
- Topic: Notes not being synchronized
- Replies: 14
- Views: 5961
Re: Notes not being synchronized
Hi Gregory, Thank you for your reply. Perhaps I should have been more detailed. In the case I am talking about, the Note does not show in the Data Viewer, even after multiple sincronizations. I tried editing the note itself as well as making changes to some of the anwers, but nothing makes the Note ...
- August 21st, 2021, 10:26 am
- Forum: Synchronization
- Topic: Notes not being synchronized
- Replies: 14
- Views: 5961
Notes not being synchronized
Hi,
I just discovered that Notes added to cases by interviewers are nog always synchronized to the server.
We are using CSEntry 7.6.2.
I have not found out when they are and when they are not synchronized.
Has anybody got the same experience?
I just discovered that Notes added to cases by interviewers are nog always synchronized to the server.
We are using CSEntry 7.6.2.
I have not found out when they are and when they are not synchronized.
Has anybody got the same experience?
- August 13th, 2021, 4:17 am
- Forum: Synchronization
- Topic: Updating installed application not working on tablet
- Replies: 12
- Views: 5361
Re: Updating installed application not working on tablet
I just want to let you all know that this problem has been solved.
The latest version of CSEntry (7.6.2) works fine on all our tablets.
Many thanks to all the different people at CSPro who spent time to help us.
The latest version of CSEntry (7.6.2) works fine on all our tablets.
Many thanks to all the different people at CSPro who spent time to help us.
- June 24th, 2021, 5:28 pm
- Forum: Synchronization
- Topic: Updating installed application not working on tablet
- Replies: 12
- Views: 5361
Re: Updating installed application not working on tablet
Hi aaronw,
The updated app is downloading correctly to my Samsung Galaxy S8, with Android version 9.
It does not work on Samsung Galaxy Tab E, with Android version 4.4.4.
The updated app is downloading correctly to my Samsung Galaxy S8, with Android version 9.
It does not work on Samsung Galaxy Tab E, with Android version 4.4.4.
- June 24th, 2021, 2:48 am
- Forum: Synchronization
- Topic: Updating installed application not working on tablet
- Replies: 12
- Views: 5361
Re: Updating installed application not working on tablet
Thank you very much for your help.
I sent you the app by PM.
I sent you the app by PM.
- June 23rd, 2021, 4:29 pm
- Forum: Synchronization
- Topic: Updating installed application not working on tablet
- Replies: 12
- Views: 5361
Re: Updating installed application not working on tablet
Yes, CSWeb and CSEntry are both 7.6.
- June 23rd, 2021, 3:31 pm
- Forum: Synchronization
- Topic: Updating installed application not working on tablet
- Replies: 12
- Views: 5361
Re: Updating installed application not working on tablet
Deleted the Packages folder on the tablet, and then tried to install the application again.
Got the same error message and the sync.log was identical to the one I posted earlier.
Got the same error message and the sync.log was identical to the one I posted earlier.