Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

offline-synchronization #7236

Open
Chris-Karona opened this issue Feb 6, 2024 · 1 comment
Open

offline-synchronization #7236

Chris-Karona opened this issue Feb 6, 2024 · 1 comment
Assignees

Comments

@Chris-Karona
Copy link

Please use the form below, leaving the prefilled data to help us. Thank you.

Page link: offline-synchronization

Document link: synchronization.md

My Issue/Suggestion

Hi. This page is very important and helpful in dealing with some of the more complex situations that can arise on a large scale native app.

In section 2.6.1 it says: "From Studio Pro 8.18 and above this process is optimized and the server will not commit the same changes because they have been applied before."

This states that the next time a sync is performed the server does not commit any changes - but is it correct to assume that the download phase will run and download the current state of the obejcts to the client? Could you please state this explicitly.

Also what if the objects have been changed again on the client since the failed sync? Presumably the sync runs in full?

You will understand that these situations are hard to replicate and understanding what has happened by looking at the SynchronizationError entity and the logs is complex, so we need as much information here as possible please.

Many thanks

Chris

@ConnorLand
Copy link
Collaborator

Hi @Chris-Karona ,

I'm in talks with devs now about how we can enhance docs on this point. I will reply back in this thread when I have more answers.

Thank you for contributing to the Mendix documentation,

Connor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants