[SAP-MDK] CallFunction action (or rule) sends data as null at second request

[miqueias_maia]

Hey experts, what's new?

We're developing a feature in our application that needs to send to the backend an email and an ID.

We are using a rule to send that data using the clientAPI method 'callFunction', as you can see below. For this moment, we're hardcoding the data just to see it on the server logs.

At first, the data is sent and we can get it on the backend, but in the second or more time, the data is sent as null.

We are sending attached some screenshots that you can use to understand better.

But, to simplify, we are just clicking on a button that triggers the function 'sendEmail' and this function calls the callFunction method and, then, the action that sends the queue to the server.

Is this unexpected behavior a bug or this is, in truth, expected?

P.S.: we've tried also with callFunction action.

captura-de-tela-2022-12-16-as-180030.pngmicrosoftteams-image-6.png

[javier_castro98]

Hello, I wanted to check if you found a solution regarding this, as I am experiencing the same issue and I don't understand why or what I should change. It would be very helpful. Thank you.

[bill_froelich]

I would suggest you turn on Mobile Network Tracing in Mobile Services and capture the message header and message body for both requests to confirm what was actually sent. You can also turn on tracing in the MDK client to capture more detailed logs as well.