problem with Datasource with PRE-Execution pgm

[ThierryC]

When launching an app that is used by a downstream supplier for showing stock.. i've been using a pre-execution pgm for the Data source..

(basically used for applying logic so he can only see stock items where he's allowed to look at.- by creating a temp file)


However, people using the app, reported that they see the same records 4 times (must have been there already quite some time but was never reported)

I've added some debugging and i see that the 'getData' action is launched 4 times .. almost simultaneously within a few milliseconds.. causing also 4 threads.


i can 't see why this is being called 4 times .??

is there anything i'm doing wrong?
2024-12-16 11 30 10 (2).png 2024-12-16 11 30 10.png 2024-12-16 11 30 10 (3).png 2024-12-16 11 30 10 (4).png 2024-12-16 11 30 10 (5).png 2024-12-16 11 30 10 (2).png

[sean.lanktree]

Based on the payload, I assume that the widget attached to this data source does NOT have any user filters, correct? What widget type is this data source attached to? How are you loading the widget (filter widget, app variables, execute script, etc...)?

[ThierryC]

The Datasource is used in a grid widget and then also the same in 3 other Form widgets?

The forms are called via a row optin menu from the grid..


2024-12-16 17 28 04 (3).png 2024-12-16 17 28 04.png 2024-12-16 17 28 04 (2).png

[ThierryC]

this is already an app that was couple of years ago,...

in the Data source the pre-execution pgm is defined ...

no user filters are active


, i guess what happensn is that the pre-excution gets called for every time it is defined on a widget, and not on the creation event itself from the grid widget.


is there workaround for this? of how would you guys typically solve this?

[sean.lanktree]

OK, that explains it. It sounds like your form widgets must be set to "Autoload". I would suggest turning autoload off on each of your forms since you only want to load them upon clicking a grid row.

[ThierryC]

Perfect.. indeed didn't know that the solution could be that simple

.. your tip solves my issue and app became a lot faster now.