Text field results for mirror/connect boards

monday Apps & Developers
, ,
1

Hello,

One of the breaking changes for the API is: “Text field returns empty results for mirror, dependency, and connect boards columns when querying through column_values”

When I am running this query on the new API version 2023-10:

{
  boards(ids: id) {
    items_page(query_params:{ids: id}) {
      items {
        column_values(ids:"mirror") {
          text
        }
      }
    }
  }
}

It seems that in the new version, the text values are still being returned, and they are not showing as null or empty results.

The question is whether this behavior will persist, or should we anticipate that in the near future, it will no longer return a value?

Thank you

2

hi @Roy
In another topic I saw a reply from the monday team stating it was an error that it still returns the text. You need to add Fragments to your query to keep getting the data in the near future

1 Like
4

Hello @Roy,

Tomorrow after a deployment, the text field will return null for board_relation , dependency and mirror . Instead, you will have to use a different field: display_value - explicitly for each of these three

1 Like
5

will the fragment method still work?

6

Hi @Matias.Monday ,

It seems that display_value is still unavailable.
Is there an ETA when this change will apply?

Thanks

7

Hello @Roy,

This will be implemented today.

Cheers,
Matias

1 Like
8

Hello @Matias.Monday,
Could you please elaborate on the reason behind display_value instead of text? That is, why make text null and then introduce a new variable?
Because now, we’ll have to check for both text for those that still use text like status columns and then also for display_value instead of just text, adding to the load of work needed to do to support the new API.

Also, I didn’t find any information about this new display_value in the documentation. I stumbled upon it in the community.

9

Hello there @kolaai,

I will speak with the team and let you know what they say about this :grin:

I will also request for this to be added to the docs.

Cheers,
Matias

1 Like
11

Hello again @kolaai,

I heard back from the team.

The change was made in order to improve performance. The evaluation of the “text” field in mirror columns takes a long time and lots of resources and a single query could result in the loading of hundreds of items. We now limit it and allow it only where it is needed explicitly.

For technical reasons, it was decided that it would not be called “text”.

I have requested this to be added to the docs :grin:

Cheers,
Matias

1 Like