Graph QL Variable Error

The_StarLord · 2026-05-19T16:04:48.029+00:00

I am working on integrating a GraphQL query to do a mutation update through a variable. (img 1) I have the mutation working when I hard-code the data into the API call (img 2)I have gone through most of the tutorial videos, but I can't recall anything discussing this. The error reads : "variable '_userId' is declared as 'uuid', but used where 'uuid!' is expected".The second half of that error message makes me think it might be out of my control and on the backend somewhere, but it is hard to tell. Is there a resrouce for Variables in GraphQL I can review in the documentation or a video? Happy to be told I missed something and to study up.

The_StarLord
29 days ago
I am working on integrating a GraphQL query to do a mutation update through a variable. (img 1)

I have the mutation working when I hard-code the data into the API call (img 2)

I have gone through most of the tutorial videos, but I can't recall anything discussing this. The error reads : "variable '_userId' is declared as 'uuid', but used where 'uuid!' is expected".

The second half of that error message makes me think it might be out of my control and on the backend somewhere, but it is hard to tell.

Is there a resrouce for Variables in GraphQL I can review in the documentation or a video? Happy to be told I missed something and to study up.
The_StarLord
29 days ago
Also, more than happy just to hop on a call with someone from the NordCraft team to go over it and answer any customer questions that can help product development. 🫡
The_StarLord
29 days ago
Another deeper dive. Looking at the quest payload, when hardcoded obviously the ID is correct, however when using a variable the data is not getting substituted and instead the variable name is send in the request.

Really not sure if I am just setting this up wrong, or it's a bug 🤷🏻‍♂️ 🪲
Tod
29 days ago
Great job @The_StarLord! Your contribution to the Nordcraft Community just made you advance to Community Level 1! 🌲
Max
29 days ago
Hey! In this call, did you actually bind the variable? It looks like it is not used. Or did you bind a different value in the "variables" tab?
Erik Beuschau
28 days ago
The difference between uuid and uuid! in GraphQL is whether the input can be nullish or not. It seems that the mutation you create uses a uuid where it should be using a uuid! for the variable. I think there's a limitation in the GraphQL editor on our end where it doesn't always include the ! when needed when creating a variable.
I'll see if I can fix that 👍
👍🏻1
@Erik Beuschau
The difference between uuid and uuid! in GraphQL is whether the input can be nullish or not. It seems that the mutation you create uses a uuid where it should be using a uuid! for the variable. I think there's a limitation in the GraphQL editor on our end where it doesn't always include the ! when needed when creating a variable.
I'll see if I can fix that 👍
The_StarLord
28 days ago
Let me know if you push a fix, and I can re-try it.
@Max
Hey! In this call, did you actually bind the variable? It looks like it is not used. Or did you bind a different value in the "variables" tab?
The_StarLord
28 days ago
I have both used hard-coded variables in the "Variables" tab, and also using the global Variables as well. Neither seemed to work. 🤔
Erik Beuschau
28 days ago
Here's what I assume happened on your end:
- You created a variable for something in your mutation with type uuid
- Later, you referenced that variable for a field that should've been uuid!
- When I tested it, I saw that the display type is not always correct, but also that it's possible to pick a uuid variable for a uuid! field (which is invalid)
- You could try removing your variable and adding it again - but adding it on the field of type uuid!

I'm working on a few improvements that should make it more difficult to get in a bad state when working with the GraphQL editor. I'll let you know when they're live 👍
@Erik Beuschau
Here's what I assume happened on your end:
- You created a variable for something in your mutation with type uuid
- Later, you referenced that variable for a field that should've been uuid!
- When I tested it, I saw that the display type is not always correct, but also that it's possible to pick a uuid variable for a uuid! field (which is invalid)
- You could try removing your variable and adding it again - but adding it on the field of type uuid!

I'm working on a few improvements that should make it more difficult to get in a bad state when working with the GraphQL editor. I'll let you know when they're live 👍
The_StarLord
28 days ago
Great to hear.

One question... how can I set the Variable type? I need to do this on the GraphQL provider end correct?
Erik Beuschau
28 days ago
If the schema's type needs to be changed, you would do that in your GraphQL application/schema yes. If you want to change the type of a variable in Nordcraft's GraphQL editor, currently you would need to remove the variable and create it again from a field that supports the type you're looking for.
The_StarLord
28 days ago
mmm alright then, in the Nordcraft editor I am not seeing a uuid! variable option and nor can I add this type in nHost either. 🤔
Erik Beuschau
28 days ago
The type information in the bottom panel would show you when a type is uuid!. In the list of variables, the value would not be shown correctly until my changes are live (currently being reviewed).
So it's a bit tricky for you to validate atm I suppose.
However, if you add a uuid! variable to an input and run the query, you should be able to see the type specified in the mutation in the actual network request to verify.
The_StarLord
28 days ago
Omg, so stupid... I have figured it out.

For some reason the id fields are not the same variable type. I guess I just assumed they were the same, so I just made 1 variable for the GraphQL call to use.

So, I needed to make 2 unique variables and link them both to the Global (Page) userId Variable.

I did not notice this before. My bad! Sometimes we just miss things in front of our faces. 💩
@The_StarLord
Omg, so stupid... I have figured it out.

For some reason the id fields are not the same variable type. I guess I just assumed they were the same, so I just made 1 variable for the GraphQL call to use.

So, I needed to make 2 unique variables and link them both to the Global (Page) userId Variable.

I did not notice this before. My bad! Sometimes we just miss things in front of our faces. 💩
Erik Beuschau
28 days ago
Great that you figured it out. That problem will be fixed with my changes, as you should no longer be able to pick a variable that is of a different type than the one you need for your input.
Thank you for reporting this btw 🙌
💯1

Graph QL Variable Error

The_StarLord

The_StarLord

The_StarLord

Tod

Max

Erik Beuschau

The_StarLord

The_StarLord

Erik Beuschau

The_StarLord

Erik Beuschau

The_StarLord

Erik Beuschau

The_StarLord

Erik Beuschau