Skip to main content

I wrote a python script to download and parse boards information from monday using ‘API-Version’ : ‘2024-01’. In this script i always used this general query:


query {{

boards(ids: {board_id}) {{

items_count

items_page(limit: {items}{cursor_part}) {{

cursor

items {{

id

name

column_values {columns_part}{{

column {{

title

}}

type

text

value

__typename

…on MirrorValue{{

display_value

}}

… on BoardRelationValue{{

display_value

}}

}}

}}

}}

}}

}}

‘’’

And it have worked fine for more than a year. Note that with this query I can dinamically change number of items to extract, use pagination and also select columns if needed. But in default it brings the whole board with 500 items.


Currently the issue is that if I try to return a board using limit=500 it will return the board informaiton but some Connected Boards info will return as null, even though I am using the disoplay value.


Already tested if the issue is the parser script, and no, I made a review on the direct export from the API and there is some items that are correctly returning the connected boards info and some that return as null. When returning into a csv. would look like


Name, Leader, Status, Activity (connected_board)

Project1, Mr.X, Active, Jump

Project2, Mr.Y, Active, Jump

Project3, Mr.ZActive,“”

Project4, Mr.X,Active,“”

Project5, Mr.AA,Active, Jump


And when reviewing the pulse Project3, for example, in reality “Activity” is not empty.


Feel free to ask questions and thank you in advance!

Getting very similar error! Good to know we’re not the only ones. Seems like a recent update has broken something


Hi @juholaan1,


Can you please confirm what API version you are using? You mentioned 2024-01, but that is deprecated.


Best,

Rachel


I was able to resolve this issue by updating my API to 2024-10.


The latest version of the API has updated linkedPulseIDs to be collected in a new way. This is a really big change that drastically alters a lot of our logic, it took me a while to figure out what was going on.


It seems I might need to update my API version then, other than that the issue has been solved, according to monday support:



also have done some testing and it is working perfectly,


Thank you all


Hi @juholaan1,


Thanks for coming back to provide the update. Glad it is working for you!


Best,

Rachel


Reply