You cannot use server actions in client function actions. So what you need is to use that server action in a data action and do all the calls for that action or function on the server-side. That way it will work.

https://success.outsystems.com/Documentation/11/Developing_an_Application/Implement_Application_Logic/Actions_in_Reactive_Web_and_Mobile_Apps?_gl=1*1uv32xx*_ga*MTY4ODA4MDcwNC4xNjMzMDc3Njgw*_ga_ZD4DTMHWR2*MTY0NjIxMTA1Mi4xLjEuMTY0NjIyODkzNi42MA..

Kind Regards,

Márcio

I already said. Use a data action on your screen, put as  output a boolean that will return the result from that server action. Then you can use the output of the data action on that if.

Kind Regards,

Márcio

I think okan wants a client action, not a screen action, that does this. And the simple answer is: that is just not possible. Of course, what you could do, is change the login logic to retrieve the user office ID, and put it in a Client Variable. Afaik that can be used inside a function.

Yeah, I understand, that is another way of doing and I think you will just do that once, so I think that's the best course of action. My idea was to call every time you need that info to call the server to get the office id. It's not wrong, but you can avoid those multiple calls by putting just once inside of a client variable as you said when you do login. :)

And what about this?

Do you think saving an id in a client variable is the best thing?

Yes I do. The alternative is to have every screen where the Id is needed retrieve the Id and store it in a local variable. Of course, I'm assuming the ID isn't top secret, and can't be abused.

Yeah, I don't know, from past experience I was taught that that is not the best thing, at least it should have another layer of security like a token. But of course, Okan is learning and I don't know how good is to push all this information. For that, I would advise @okan yucel to do at least the training to know all these terms and get some practice before starting something more "complex".

I'm only using this operation to hide or show buttons. Sensitive part is done on the server side logic so this shouldn't be a problem

So you should go with @Kilian Hekhuis's answer by using client variables. :)

When you do log in, after doing login, on the login action you should call that info and assign the value to the client variable.

You don't need a data action, you can also have a screen aggregate. But then still, you'd need that in every screen. My solution above would allow you to only retrieve it once.

No, Client Variables are equivalent to the Traditional Web's Session Variables. They can be found on the Data tab, between Structures and Site Properties. If you create a new Reactive App, Service Studio automatically creates a Username Client Variable that it sets in the Common/UserInfo Block. It's something similar what you can do with the office ID.

So you need to call the server action that retrieves the officeId and with that output, you assign the value to the client variable.

What I did here was put everything in a server action and retrieve all the data I want.

Now you need to figure it out by doing step by step.

1- get the office id

2- call the action that retrieves the office id upon login

3-assign the officeid to the client variable

You're most welcome, happy coding!