Idea - Optimize data action request payload

Optimize data action request payload

Not right now

Frontend (App Interfaces)

As confirmed by OutSystems in this forum topic , data fetch actions are not optimized and instead passing all screen data in every request payload. Even if the parameters are not used anywhere in the data action.

Please optimize this.

23 Nov 2022

Breno Nico

We have a registered problem (RPM-1819) since 24 Nov 2021 about this subject/issue, on cs_portal, and it's "Waiting for Investigation" thenceforth. We have some applications with large forms that we are controlling the number of variables on the client side, and at this moment our biggest limitation is our firewall, which is very strict with the size of the requests (payload).

29 Nov 2022

James Vaughan

Indeed, this is hampering go-live of one of our products protected by a WAF. Will try to workaround with a Server Action, but man...this has been painful to figure out.

07 Apr 2023

Miguel Freitas

Staff

Changed the status to

Not right now

As stated in the public documentation, the reported behavior is the expected one. The optimization only works from the server to the client and not the other way around.

Currently, OutSystems strategy and priorities do not include the development of a new feature in the O11 roadmap.

14 Dec 2023

Nuno Guedes

Ok, but now that O11 features are back, and O11 will not loose support, when would be a propper time to implement this?

Effectively sending all the screen variables to the data actions are causing a huge overhead in some screens tht we have.

Thanks.

30 Oct 2025