Looks like there is one closing curly bracket to many
yes, I have edited this code too much and left one too many in. If you delete it, the code still doesn’t work.
“Doesn’t work” is a little vague 
. Do you get syntax errors, no data, unexpected data?
It works as expected on my side, did you select the correct API version?
And on this other playground site I get the following error:
{
“errors”:
{
“message”: “Unexpected token ‘u’, "upstream r"… is not valid JSON”,
“stack”: “SyntaxError: Unexpected token ‘u’, "upstream r"… is not valid JSON”
}
]
}
There has to be something simple we’re doing wrong?
Looks like a monday issue to me. I recommend to reach out to appsupport@monday.com with this one
Thank you!!! Appreciate your help!
I’ve seen this sort of thing happen when you have a text editor that starts formatting text. Like in your query the ... has been replaced by a single ellipsis … character for the ... on MirrorValue fragment. Or other invisible characters (em space, en space, etc.) get in there (which may be the case) This kind of thing happens if you let MS Word come anywhere near code.
Also from the documentation, the samples have a copy button in them that appears if you mouse over the sample box. If you select and copy its possible to pick up stray invisible characters.
Thank you @basdebruin and @anon29275264,
@Cary if you still have issues with this do send us an email if you haven’t already and we will be happy to take a look!
Cheers,
Matias
Thank you @anon29275264 and @Matias.Monday. We are starting to think it might be because, while we’re only planning on pulling in a few records at a time, the board itself includes a large number of mirrored columns, cast columns, connected boards, etc.
We did reach out to support last night and have started the process today.
Hello again,
We will be happy to help via email then 😁
Actually, @Matias.Monday, we haven’t heard back from anyone in support via email since we added authorization for them to login as me.
We did find the last example Dipro spent a few seconds covering in his presentation last week very helpful and are trying to work through implementing it now.
Hello again @Cary,
I see you are interacting with our team today 😁
I’ll leave you to it over there with Bill!
Cheers,
Matias
Did you get any resolution on this because I have exactly the same error message on a 2023-10 display_value query - and a relatively small table (<100 items)…
We were able to get past this issue. We basically had to limit what we pull to just the fields we needed. Doing this allowed us to grab up to a whopping 5 records at a time (we have a lot of mirrored columns that made the call too complex) and took quite a while.
We ended up using ‘Column Magic’ to recreate the mirrored columns we needed. All this allows us to pull in a very large number of records (I’m not completely sure what the limit is - we have yet to need more 20) very quickly.
This is the query we’re currently using:
query = ‘’’
{
items_page_by_column_values(
limit: 50
board_id: 4304082965
columns: r{column_id: “status9”, column_values: “In Progress”]}]
) {
cursor
items {
id
name
column_values(
ids: a
“text35”, “date”, “dropdown2”, “check2”, “text197”, “text430”, “text99”,
“text948”, “text26”, “long_text7”, “franking_approval__”, “text96”, “text654”,
“status4”, “text65”, “status9”, “label_2”, “status”, “status22”
]
) {
text
… on MirrorValue {
display_value
}
}
}
}
}
‘’’
data = {‘query’: query}
Thanks for using Column Magic! Fortunately, at this time, we’re not as badly affected by this bug since we only get a single mirror at a time. I hope they get it fixed soon.
But the new API does open up some enhancements to Column Magic in the new year!
