Nodejs URL Parameters Assistance Needed

[scott]

I seem to always have issues with this and can never remember how to resolve it. I have spent the past two days reviewing the forum trying to find a solution and have not been able to find one that works. I am sure I have missed something very simple, because this is a fundamental thing, but the answer escapes me.

What I would like to do is have either a button or a link on a nodejs page that when clicked takes a user to an edit page but it could also be something that links to a details page, etc.

I have my route set up as /company/edit-national/:id

I have two buttons set up on a page. Both work the same way, but come about it differently.

The first button is an anchor button with the following attributes.

The second is a regular button with the following attributes.

Both buttons function properly and open up the page correctly.

I have created a server action that calls the for the parameter “id”.

On the layout page, I set the query parameter “id”.

On the layout page, I created a simple header that calls for a value from the server action.

On loading the page, no results are found from the server action.

There are no console errors on the page.

If I enter a default value in the server action, results are shown and displayed on the page.

I am sure this is something very simple that I have overlooked, but the solution escapes me.

[Apple]

You did the same mistake as this person:

Server Connect Not inheriting the query param NodeJS

Maybe I’m misunderstanding how it’s supposed to work, but according to this from the documentation, the server connect should automatically see the param on the server side without having to add it as a $_GET variable directly to the server connect, but it never appears server side: It is important to understand that the Server Connect used on the page inherits all the input query parameters or route path parameters of the current page, so it will automatically “see” them in the URL. Here is t…

$_PARAM.id doesn’t exist in the Server Action. You’re calling the server action “/edit”, where’s the param there? You didn’t call the server action like /edit/123

[scott]

Hi @Apple, thanks for the reply. However, I am not clear as to what the solution is here.

I created a server connect route with the parameter on the end, but I am not sure what to do with it from here.

[guptast]

Hi Scott,

To access values of query parameters in Server Actions from Server Connects is via $_GET variables. If you set up a GET variable $_GET.id and replace the query condition with the $_GET.id variable, the query will filter the data based on the pc_id.

[scott]

Thanks @Apple and @guptast, I was able to figure it out!

@TwitchBlade, you might find this helpful.

What I ended up doing. Was this:

In the server action, I used the $_GET variable as recommended above.

I kept the page route the same, but deleted the server connect route as it was not needed.

On the layout page, I kept the query variable under the query params.

Now here is where it got interesting. Under the server connect, the “id” input parameter appeared as was expected.

However, when the lightning bolt is clicked to pick the input parameter for the “id” field, I could not see the variable under the query params.

What I had to do is switch to code view and add query.id between the quotes in the dmx-param:id=" " code.

You would change “id” to whatever you named your variable in the query params.

That made it work for me.

I am a little confused why the query params was not selectable through the picker, but I have made a note of it so will remember in the future and not have this issue again.

[guptast]

Hi Scott,

Glad that it is working now. I think the confusion may be arising from the term dmx-param in Server Connect, required to access the $_GET variables on the front-end.

[Hyperbytes]

Did you try adding “id” to the global parameters of the layout page?
That should make it available to the picker.

[scott]

I tried putting it in the “Define Global Data” with no results in the picker and then removed it.

I left it in the “Define Query Params” under App, but still not available in the picker.

[Hyperbytes]

Tried Global Query parameters?

[Cheese]

@scott

I tried putting it in the “Define Global Data” with no results in the picker and then removed it.

Was your App ID (in the Content page) the same as the Layout page? If not parameters, cookies, and Data Store schema items will not be accessible in the picker…

[scott]

Thanks @Cheese and @Hyperbytes!

As indicated, I had different values in the App ID. Once I changed that, everything works as expected.

[Hyperbytes]

Yes, the significance of appid does not seem well understood.
Feel a video in the making on return!

[TwitchBlade]

Thanks @scott. I have route parameters on server connects working fine and they send the $_GET variable to the server side and I can use them. My issue was I was trying to make the server connect dynamic to where I didn’t have to put a value in an input parameter on the server connect because where I was trying to use the server connect, there’s nowhere to put the parameter. Perhaps I’m still confused on the difference between $_PARAM and $_GET. I know how to use $_GET and $_POST I don’t understand the use case for $_PARAM. I thought it was a way to grab a param from the url on the server side without having to send it via server connect input params.

For instance, I’m trying to get the title, keywords and other meta data from values stored in the database based on the current page. There’s no way to send an id or page identifier to the server side that I can see.

[scott]

@TwitchBlade, what I did was watch @Hyperbytes video here. Videos 26-29 cover using the globals server action to do the SEO tags. Then for page specific data, use the $_GET variable as outlined above.

[TwitchBlade]

Thanks again. I’ll have a look.