Support Forum

I am new to the Mobile together platform and I'm currently evaluating the product.

My requirement is gather data from remote workers who will often have no data connection.

Do you have a worked example where the data is stsored locally on the device until there is a data connection and is then transmited to the server for permanent storage in a database?

thanks for such a prompt reply. I'll have a play around with the files you have sent.

For editing of data, I've made a small modification to the database - I've added an autoincrement ID field. This is important to be able to identify the row you have edited.

I've also done few more changes to the previous "AllAddresses OnDemand" example. First, I've used the context menu "Create OriginalRowSet" for $DB1. With OriginalRows MobileTogether is able to generate INSERT/UPDATE/DELETE statemens for you automatically - all you do is just execute the Save command.

On data reload I'm now saving both RowSet and OriginalRowSet in $PERSISTENT tree. I've modified the table to show Edit Fields instead of Labels so that user can actually edit data. Also I've set the Table Row Group property "Automatic Append/Delete" to "true" - with this MobileTogether shows you + and - for adding rows and deleting them.

At last, I've added "Save to database" button. If your task would not require persistency of data and being able to edit without Internet connection, then everything would be very easy - you would create a dynamic table directly for $DB1 and use the Save command after user has edited it. But in your case user edits the $PERSISTENT tree. To save data to the database, I'm reloading the DB again (because it might have been changed in the meantime by other users), I'm deleting those rows from the DB RowSet which were used originally at the time of last reload. I'm appending all rows which are now available in $PERSISTENT tree. I'm executing Save command which saves the data as described above.

Due to requirement to edit data without Internet connection you have 4 actions to execute instead of 1. But this is it !!!

---

Altova MobileTogether Experts

One note here: in a real live scenario you will probably want to warn user from overwriting data which has been changed in the database since the last reload. I.e. imagine, you have got data 3 days ago, 2 days ago somebody else makes modifications, and today you want to save - the current implementation would simply take all records from your device and overwrite the database. Instead, you probably would want to save some kind of a timestamp in an additional field when the row has changed and use it to warn user or even prohibt him from saving data which has already been modified by another users.