4.1.1 loadData call is causing unsaved data to be saved

Classic Servoy
1

Hi all- in a little bit of a bind here with version 4.1.1 and wondering if anyone else has had similar issues/experiences.

Our production application with the following scenario works in 4.1.0 and lower, but not in 4.1.1. Is this now the desired behavior, and if so, how do we get it to still work the way it used to?

  1. We have ‘autoSave’ set to false.
  2. We create a new row in a found set on form A.
  3. The user enters data in the columns of the new row on form A.
  4. We have a valid relationship on the new row to another table.
  5. We use the relationship to do a loadData(relationship) on another form B.
  6. We allow the user to enter data on the related rows on form B.
  7. The user hits a save button to save the new row on form A and the related rows on form B.

In version 4.1.1 as soon as we execute the loadData line the new row is saved.
We cannot have it do that until the user finishes on form B and decides they want to save the data because they can change their mind and cancel the transaction.
We have a button to rollback the transaction that is in memory.

Any input or suggestions would be greatly appreciated! :D

Regards, Tony

2

Hi Anthony,

Servoy 4.1.1 introduced an issue with autosave. Servoy 4.1.2 (just released) solves this issue.

[fix] case 197352 Despite that databaseManager.autoSave = false, a new record is written to the database

See viewtopic.php?f=16&t=12096&p=61188#p61188 and
viewtopic.php?f=16&t=12294

Hope this helps.

3

ROCLASI:
Hi Anthony,

Servoy 4.1.1 introduced an issue with autosave. Servoy 4.1.2 (just released) solves this issue.

[fix] case 197352 Despite that databaseManager.autoSave = false, a new record is written to the database

See viewtopic.php?f=16&t=12096&p=61188#p61188 and
viewtopic.php?f=16&t=12294

Hope this helps.

Robert- thank you so much! I missed the post on the problem- thanks for pointing to me it. This most definitely helps- much appreciated.

:D

Regards, Tony