On the same servoy server there is a batchprocessor that will add records to tables that are also shown in the Erp solution.
I notice that when the table is shown on a form in the Erp solution, I still have to do " show all records" to make records added by
the batchprocessor visible.
Is it possible to see new records without the user having to push " show all records" ??
From an option in my solution the SHC is invoked and adds some records to a table. After that the user goes to the option where those records can be treated and they are not there until he navigates to next record.
I have the opposite need: I’d like to turn off databroadcast when an HC performs some rows insert, is this possible? I’d like to avoid 100+ clients receiving the databroadcast notifications, especially the client that triggered the operation.
because for none related it can be anything… you can have find criteria that are very hard to do.
For related it is a fixed set, that we quickly test and if we do think, ok this one could (and i stress here could we don’t know it for sure!) we do a re query.
That is quite hard to do for a normal foundset then we constantly have to refresh them, quite a performance penalty
jcompagner:
That is quite hard to do for a normal foundset then we constantly have to refresh them, quite a performance penalty
This is really true. For updates the data broadcasting is working, and in some cases I would even like NOT to have data broadcasting.
[attachment=0]Capture.JPG[/attachment]
Calculate the nr of hours that the system is refreshing.
As you can see that this refresh operation already has a very bad influence on the performance.
The avg time to refresh is significant higher than a normal operation.
I’m even going to rewrite some forms (forms based on datasets in stead of foundsets) to avoid this data broadcasting
ngervasi:
I have the opposite need: I’d like to turn off databroadcast when an HC performs some rows insert, is this possible? I’d like to avoid 100+ clients receiving the databroadcast notifications, especially the client that triggered the operation.
+1
I already asked that earlier, but it seemed to be very difficult.
Maybe the easiest way for Servoy would be a setting on table level if data broadcasting must be ignored.
In that case it would be system wide and perhaps easier to implement.