NodeJS: Can't bind Sort/Order parameters in my state manager (query or session)

Wappler General Need Help
1

Hey guys,

I'm new to NodeJS and I'm kind ENJOYING its benefits, but there are moments that I fill like a "fish out of the water"...
So, now I hit on a wall trying to add a state manager on a bootstrap5 table generator in a content page.
I have in my layout page:

  • a session manager and defined its schema (handling various filtering variables)
  • the serverconnect fetching data (users)
  • a dataview based on the above SC
  • a datadetails based on the above dataview
  • a query manager and defined its schema (handling my users table Sortabe Headers) .

All well...
Now I wanted in my content page to add a bs5 table (generator) listing the users.
So, I tried to add it and I can define the state manager (the query manager from my layout page) BUT I cannot bind the Sort/Order parameters because the dropdwon list is empty. Allthough, I can see the variables of my query manager in my binding panel but in the specific dropdown list of Sort or Order parameters it is empty...

I hopeI made it clear...

image
image1824×1051 48.4 KB

image
image1754×610 19.6 KB

Now,
If I add the query manager in the content page it works and can bind the Sort/Order Parameters for my Sortable Headers but:

  1. of course I have 2 query managers
  2. no matter which one I select (the layout's or content's page one) always the query manager defined from the lauout page is selected

image
image1483×458 14.7 KB

image
image1356×386 13 KB

Wappler 6.1.2

Anybody have an idea on that one?

Thanks in advance

2

Try changing your APP ID to match that of your Layout page (you will have to do this for all Content pages using the Layout specific values). If the ID's do not match then the Content page will not display the values defined in the Layout. Likewise for Cookies and Data Store etc. Am sure that is what is causing the issue...

There are MANY MANY benefits to Node over PHP! @JonL 'The Baptist' converted me.

:slight_smile:

2 Likes
4

Thanks Buddy!!

Yes, that worked for me. I really have to get used to using the same APP-ID on related pages.
I' was just confused because the layout's query/session manager were present in the binding panel of my content page EXCEPT from the case of the Sort/Order Parameters.

I mark your suggestion as the solution my friend because it solved my problem.
Obviously Teodor saw something and assigned it to George, so I don't know if if we will have any other suggestion or update on this matter.

The only concern for me switching to NodeJS is the server setup and security... It is handled in a different way. I suppose nothing tragic as long as anyone do it a couple of times and get used to it! :thinking:
I'm working locally now... IF THE MOMENT OF DEPLOYEMENT COMES I WILL NEED HELP :cold_face:

*By the way, thank you @JonL for your contribution and everything you have offered in here mate!

1 Like
5

Docker makes it all so easy to manage your Node application (and Digital Ocean are GREAT hosts, I'd very highly recommend them). Resource Manager is working great for us now after the most recent release. We use Wazuh for monitoring our environment. Allows us to control and respond to threats. Has a learning curve. Great thing is the ability to create rules and automate responses. Docker Deployment is simple. Essentially one click once set-up. We made the switch to Docker/Node for all of our Projects and haven't looked back since.

You'll be fine. Just about every scenario has been covered within the Community!

:slight_smile:

1 Like