Servoy V5.2 omitRecord without influencing next search

Classic Servoy
1

I’m moving an application from Servoy 3.5 to Servoy 5.2 and I got the following error:
Can’t find method com.servoy.j2db.FormController$JSForm.js_omitRecord(boolean). (C:\Documents and Settings\Administrator\servoy52full_workspace\gsMagz_movim\forms\mgMOVIMG01.js#482)
at C:\Documents and Settings\Administrator\servoy52full_workspace\gsMagz_movim\forms\mgMOVIMG01.js:482 (commit)
at C:\Documents and Settings\Administrator\servoy52full_workspace\gsKernel\forms\MENQRY00.js:358 (form_store)

In this method it is used the following instruction:
var success = controller.omitRecord(false);
I’ve tried to change the instruction taking out the ‘false’ parameter and it is accepted…but in this way the functionality of my application is changed!

It seems that omitRecord is not accepting anymore a ‘false’ parameter that is forcing the record to be omitted in the current search only without influencing following searches.
This behaviour was documented in the Servoy 3.1-3.5 timeframe in this thread:
viewtopic.php?f=13&t=7998&p=39360&hilit=omitRecord#p39360

Questions:
Is omitRecord() default scope (without parameter) changed in Servoy 5.2?
Is available any workaround in Servoy 5.2 to force omitRecord() to be related only to current search?
…or should I file a bug?

Happy 2011 to all readers! :)
Gianni

2

Gianni,

Prehistoric excavation in the Servoy sources did not show any proof of early existence of controller.omitRecord(boolean).
The forum thread listed a feature request that afaik was never implemented.

foundset.clear() /loadAllrecords() removes the omit-records condition from the foundset.

Rob

3

@rgansevles

uau! Prehistoric Servoy…I didn’t think to be this old!!!

Anyway, also if it worked before…I’ll revise my code to implement it properly.

Tnks 4 the quick answer,
Gianni