OData: Option to only send PrimaryKey(s) during Call External Action - Mendix Forum

OData: Option to only send PrimaryKey(s) during Call External Action

0

I've implemented BulkInsert/BulkDelete actions in an OData service that I control and it's worked well so far. However, I've hit a wall in that the Mendix runtime will either send null for associations during a call external action (if the checkbox is unchecked), or it performs a full retrieve on the objects in question, even if I only need to send in the ID. This results in 100s to 1000s of extra queries to my OData API server when the runtime itself should be able to make a smarter choice. Here is an example screenshot:

 

image.png

asked
1 answers

I now have an even more expensive request that will completely blow out the memory usage of the Mendix runtime server. It would be really nice if the runtime server was able to handle this without having to check these boxes (and it doing a retrieve for every association). My only workaround I can find so far is only viable because I wrote the OData API implementation. I'll have to allow the client to write to the equivalent of foreign keys. Then I also l lose type safety.

 

image.png

Created