Getting Details of the Logged In User

[web-works]

After the introduction of Globals (which I appreciate very much) some things go wrong like getting details of logged in user.
Steps taken:

1. Security restrict
   

   

2. Database query
   

   

3. Server Connect
   

   

4. Data Bind
   

   

5. Result (ZERO)
   

   

Been struggling with this for two days now, but can’t get it done.
What have I done wrong here?

[Teodor]

In step 2 where do you get the identity value from?

[web-works]

From the Security Provider

[Teodor]

Please make your security provider a global option:

Setting up Site Security Settings

Using the Security Provider you can define the security settings for the whole project and reuse them on all of your pages. We will go through each of the available options - from single user to database users and explain how to set them up. Setting Up Security Provider The Security Settings you create are globally available for all your server actions across your project. You need to setup your Security Provider once, and then you can reuse it in all the steps which require any kind of secur…

then use the identify step:

Using Globals in Server Connect

Overview We added new Global options in the Server Connect panel. The Globals allow you to define and re-use Database Connections and other Settings (1), Variables / Input Parameters (2) and API Action Steps (3) across all your API Actions in the project: [Screenshot_1] So it’s no longer needed to add these Database Connection or Mailer Setup steps in every server action you need to use a database connection or send an email. Defining Global Variables / Input Parameters You can easily def…

and use this identify step in the query filters.
Remove the security provider step form the server action as well. Security provider should no longer be used as a step in your server action.

[web-works]

Wow, totally different approach, but working now.
Thanks Teodor

[Teodor]

@web-works

totally different approach

Right, but it saves you a lot of additional steps. You only define the provider and the identify steps and they are available in all the server actions.

[web-works]

Yes it does save a lot of steps. Still happy with Globals. Would have liked finding the “How To’s” a bit sooner though.