Set Value Issue

[s.alpaslan]

Wappler Version : wappler 3.5.1
Operating System : Windows 10
PHP

I discovered bug that occurred in 3.5.1. In screenshot 1 I created a few values. I have assigned a few static to these values. but I realized that the first value created, “a”, is displayed on the screen and it works as it should, but when I want to use the value “a” in other steps in server connect, I cannot use it and I cannot get a screen output of this value.

screenshot 1

Output
the output that should be seems wrong.

also . I tried to use the token that I created during the Paypal api connection in another step and the result was the same.
So I think the error is not just about defining value, the problem is in a different place. I would be glad if you give information with a temporary or permanent solution.

I can’t continue my project right now.

[s.alpaslan]

@patrick Will there be an early update for this issue?

[patrick]

Please test following file, unzip in dmxConnectLib/lib.

App.zip (2.1 KB)

[s.alpaslan]

thank you so much @patrick … fixed

[mebeingken]

Any chance you can post a node version @patrick ?

[patrick]

For node, unzip in lib/core.

app.zip (3.4 KB)

[mebeingken]

Thanks @patrick

I was hoping that would solve my issue of the Security Provider identity not working, but no luck. Maybe something different? As soon as I take the security provider off, and rely on the Global security provider, my query action is unable to properly lookup a value using the security id in a condition.

[patrick]

If you want to use the security id then you will need the security provider, when using just restrict / login or logout then you can just point it to the global defined provider. You could add it as a global step, select Globals and add the security provider there, it will then be available under all server actions. We are still investigating on how to improve this.

[Teodor]

Fixed in Wappler 3.5.2