I’m wondering if I’m doing something wrong here in relation to the note field on draftOrder.
If you look at my screenshot below you see:
The GraphiQL docs…
and the autocomplete function in the editor tell me there is a field called note2 on draftOrder, not note.
In my input however, I need to specify note, without the 2. Using note2 will show an error
In the result, I get a field called note2 as requested, buy as you can see the value is the value I just passed as note, without the 2.
Is this an error, or am I missing something?
Also, possibly related:
When I update the note2 for an open draftOrder and then check the order in the admin interface I see my new note. But when I update the note2 for a completed draftOrder, GraphiQL tells me the note was updated succesfully, and I can retrieve the updated note2 succesfully using GraphiQL as well, but the admin page will still show the old note as it was when the order was completed.
If you use note in the body of the mutation instead of note2 - does this fail? ie: you should be using note in both the input variables and the actual mutation.
Hi @Liam-Shopify
Yes, it fails; the editor shows draftorder.note doesn’t exist, and the response confirms Field 'note' doesn't exist on type DraftOrder.
It seems draftOrder uses note2, but draftOrderInput uses note, so it is impossible to set either of them this way.
From connecting with our internal team, it does seem that you’re actually running this mutation correctly in your original post. You should use note on the input and request note2 on the response.
I’m unsure exactly why this is the current behaviour, but we’ll clarify this on the docs and the product team have added this to their backlog to address.
