I am attempting to retrieve all the content from a Monday board that has recently been shared with me. My task is to write this board to a Google sheet and to Google BigQuery on a daily basis. I do not seem to have editing permissions but I can view the board.
It may be that my lack of permissions are preventing me from retrieving column values for each item. Here is the query and the results:
Note the presence of only null values. Here is the actual table as to confirm that it does not actually contain null values at these fields:
Please help me figure out why I keep getting nulls for my column values. Perhaps an issue in my query or the lack or permissions.
Welcome to the community! It looks some of the columns are mirror columns (or board relation columns) and those do not return anything unless explicitly asked for in a fragment
Good day @basdebruin
Thank you very much for this useful explanation and link to the solution. It turns out that the board I am working with is constructed from 7 other boards which it mirrors.
I tried using the display_value field once conditioning on … MirrorValue. Unfortunately, it does not always work. I have attached the below query and error response. My guess is that display_value must return text but is unable to.
The following seems to work though but is very slow:
I suppose the next best thing is to query each original table separately as these queries will be less complex such that queries don’t crash.
Reach out to email@example.com about the first error.
Display_value definitely works so there must be further issue and its not with your query.
A couple bits of advice, always include the
column_value because while
title is the nice name it is not immutable.
id is immutable so you can be assured you can reference it in the future.
type so you know when its a mirror or not, and can know when to pull
As @codyfrisch said, you can send us an email to firstname.lastname@example.org and we will be happy to take a look into it
Thank you for your reply and supporting the query not to be incorrect. I also appreciate the additional advice to use in future queries; this will most certainly prove useful.
Good day @Matias.Monday.
I have reached out to the support team. They have been very friendly and helpful. Unfortunately, a permanent solution has not been reached yet. It seems that the issue lies with the 2023-10 API being slow. The 2023-07 API has no issue extracting mirrored text values (my goal). The old API also seems much more simple to use and requires less code and concepts. I am sure that it addresses limitations of the old API but at the moment it would seem to be an inferior API. Hopefully, the new API’s issues are addresses soon so that we can appreciate it.
Hello again @DylanSolms,
I know the team is investigating some cases of slow API responses and working on that, so hopefully you will get some good news soon in the email thread you have with us
This is excellent news; I wish them much success.
I somewhat agree and am concerned the final deprecation of 2023-07 is premature, as 2023-10 does not seem stable yet in several areas. I know 2023-10 will be immediately deprecated on January 15th 2024 in favor of 2024-01 becoming the stable default as well. I don’t suspect that 2024-01 is going to magically fix things on release - as the issues here are probably common to both.
I don’t think the new API requires significantly more code anywhere (unless you consider one line in a query a lot), except maybe dealing with moving display_value to text (this is how I am doing it, I’m running a quick iteration of columns, and on mirror columns, copying display_value to text so that I don’t have to treat it any different in other code.)
To me, working with some of the things I do, is requires significantly less actually. I’ve been able to eliminate one and even two queries when working with linked items.