Observation with AutoSync

[Detlev Ott]

Dear all,

Observation: AutoSync is activated (Cloud+, sync period 15 sec). If different records are changed continuously, several entries are not stored to the database but remain with the previous values. The last experience today was a set of 37 records (only 3 simple text fields per record), 9 were changed with the result that 3 were updated correctly while 6 remained unchanged. This occurrence was revealed after the database was opened some time later.

I do not want to update the records one by one and double-check directly afterwards whether or not the data has been stored correctly to the database.

The present workaround is to disable AutoSync which was not used for the changes described above as I did not expect this behavior in such simple updates. I can imagine that in complex datasets with several calculations and cross references there might be hick-ups while syncing but here…??

Does anyone else have same observation? What can I do?

Thank you very much for your ideas.

Best regards,
Detlev

[Brendan]

Hi Detlev,

Were these existing records or new records you created that didn’t save? Which view were you typing into? Multi-Column list view? Default Layout? A Custom Layout? Or a Universal Layout? Or was it in a Table field or a Link to Form field?

So are you saying then that by disabling AutoSync, you’re not seeing this issue?

Thanks,

Brendan

[Detlev Ott]

Hi Brendan,

Thank you very much for digging into this matter.

It was both, existing and new records but the most occurrences were with new records. You can see in the attached screenshot that I was using a Universal layout in a One-Column list view. The data was changed in the two text fields “Kennzeichen” and “Art”.

Yes, while disabling AutoSync this issue was not seen.

Thanks for your support.

Best regards,
Detlev

Attachments:

You must be logged in to view attached files.

[Brendan]

Could you try this on the Default Layout with auto-sync on to see if you find the issue? It could possibly be something with the Universal Layout causing this issue.

Thanks,

Brendan

[Detlev Ott]

I made some changes in both, Default and Universal Layout but unfortunately could not reproduce this behavior. After changing 15 record back and forth it could be observed that on Default Layout it took 2-4 seconds before the text field was ready to allow the next change. In other words: it was not possible to make some changes prior to waiting this time period to get focus bcc on this data field.

Thanks,

Detlev

[Brendan]

Oh that’s very strange. I’ve never seen that or heard of that issue before. Do you have any Calculation or Script fields that may be running when a value in your field is changed? That could definitely be causing some performance issues depending on the formula or script.

[Detlev Ott]

No, there are no calculations, scripts or any other type of logic behind. The database document contains roughly 20.000 records but most of the forms are just a collection of text fields. The whole document is for reference only – without any calculation or other high performance demanding stuff.

1 form with 500 records contains icons but this form has no relation to the form that was updated. There are only 2 forms that are linked (n:m) but they are not effected by the changes.

Does every change in one form lead to recalculation in all other forms of the same document? If so perhaps the number of records causes the issue.

[Brendan]

No, Tap Forms will only run a calculation or script for the currently viewed record when you make a change to a field that’s referenced by a calculation or script field.

Why it’s taking 2 – 4 seconds before it allows you to make another change is a mystery.

If you’d like me to do a performance evaluation on your document, you can send a backup file to support@tapforms.com and I’ll take a look at it.

[Detlev Ott]

Thank you very much for your response, Brendan.

The backup file was sent to you some moments ago. Hope this may clarify the situation.

Again, thanks a lot for your support!!

[Brendan]

In case anyone else sees this post, the solution was to run the Re-build Search Index function under the Tools menu. That allows the database file to become optimized and improves the speed.

Thanks,

Brendan

[Author]

Posts