Hello everyone!
I'm a bit recent with outsystems so if you guys can help me on this would be nice. i believe that the solution isnt that sophisticated since I'm sending the data to the service action. My problem, is that, the service action doesnt do nothing with that data. I have really simple scenario, so this print might be enough.
even with that break on the service action, the debugger doesnt stop there
Hi,
Service Actions run in a different thread. If you set the entry module to your frontend module for debugging you will never hit the service action. You have two options
Start the debugger with (this module) in the module where you created the service action. In another instance of service studio start the debugger in the frontend module. This way you can debug both - the frontend module and the service action module at the same time.
Another approach is two use SERVER actions with your business logic during development time and then switch to a SERVICE action (which in turn wraps your server action) once you are happy with the result.
Best
Stefan
A side note. Your client action in the first screenshot contains multiple service action calls. You should consider wrap that logic in a server action or service action.
Hi João Espinheira ,
First of all if you are new to platform then Welcome, and for your question i can say that in a best practice do not use server actions in loop or many times in client side actions,
As well as for service action there is some specific scenario to use them so if you can do these operations from server actions or client actions itself try to avoid screen actions.
You can learn more about Service Actions in this guide.
I hope it'll help you,
Thanks
Deep
Hi Jaoa,
Try debugging the server action by setting the consumer module, I am sure you will be able to figure it out.
Refer this link,
https://success.outsystems.com/documentation/11/developing_an_application/troubleshooting_applications/debugging_applications/debugging_producer_modules/
Thanks AWL!
thank you guys, after i got it on the debuger i was able to solve this out. the solution was restart the service studio, for some reason wasnt runing the service action. Stefan thank you for the tips, they were usefull.