hasRecordChanges

Hi guys,

databaseManager.hasRecordChanges(foundset) returns false when one of the records in the foundset clearly has edited data.
Same command with the index of the edited record returns the expected true.

Cheers,
Maria

maria.kyselova:
Hi guys,

databaseManager.hasRecordChanges(foundset) returns false when one of the records in the foundset clearly has edited data.
Same command with the index of the edited record returns the expected true.

Update: just thought the issue might be because I pass a foundset created from databaseManager.convertFoundSet(fs, related).
Well, I’ll say it’s still a foundset and I want to check for changes in it, otherwise I’ll have to loop through all related foundsets manually :?

Consider it’s a bug or expected thing?

Cheers,
Maria

Hi Maria,

recently I ran into a similar situation in an existing solution from one of my customers.
At first I also thought of a bug, but after close inspection of the code I found out a new foundset was queried from the server.

So, the foundset that you check must be exactly the same as the one you edited.
if you do a ‘convertFoundSet’, Servoy will fire a query in the background.
This will bring in a fresh, separate foundset from the server which obviously can’t have changes.

Hope this helps tracking down this situation.

mboegem:
Hi Maria,

recently I ran into a similar situation in an existing solution from one of my customers.
At first I also thought of a bug, but after close inspection of the code I found out a new foundset was queried from the server.

So, the foundset that you check must be exactly the same as the one you edited.
if you do a ‘convertFoundSet’, Servoy will fire a query in the background.
This will bring in a fresh, separate foundset from the server which obviously can’t have changes.

Hope this helps tracking down this situation.

Yep, I figured there was something like that.
Case dismissed :)

Cheers,
Maria