Skip to main content

FormulaValue display_value no longer working via API

  • January 22, 2025
  • 4 replies
  • 65 views

  • Participating Frequently

This query works fine in the Playground.

{
items(ids: [123456789]) {
id
name
column_values(ids: [“date”, “label”, “formula”]) {
id
text
column {
title
}
… on FormulaValue{
display_value
}
}
}
}

But once I send it via the API I get an error about the display_value.

Body being sent:

{“query”: “{ items(ids: [123456789]) { id name column_values(ids: ["date", "label", "formula"]) { id text column { title } … on FormulaValue { display_value } } } }” }

Error Received:

{“errors”:[{“message”:“Cannot query field \\“display_value\\” on type \\“FormulaValue\\”.”,“locations”:[{“line”:1,“column”:144}]}]}

Anyone have any idea what’s going on here and how to fix it? To my knowledge, the FormulaValue display_value option is the only way to get the result of a formula out of Monday.com.

Thanks,
Eric

4 replies

dvdsmpsn
Forum|alt.badge.img+1
  • Participating Frequently
  • January 22, 2025

Specify the api version to be 2025-01 ?


  • Author
  • Participating Frequently
  • January 23, 2025

No, I’m not specifying a version in my API call, so it’s using the current one.

One more clarification, the item with the formula is a subitem and that subitem DOES have the “formula__1” column. I could see this error occurring if no Formula column was present. I can confirm in this case, there is a Formula column.

Thanks,
Eric


  • Author
  • Participating Frequently
  • January 26, 2025

My work around was to recreate the formula in a Zapier Code block, since I had all the information to do that already. However, this is bad practice, because now that formula is in multiple locations that have to both be updated if it needs to change.

I have confirmed that this problem does NOT happen in version 2025-01.


  • New Participant
  • April 1, 2025

I ran into a similar problem, where I was able to get it to work on the API Playground, but when I queried the API directly, I ran into the same issue and my API version is specified at 2024-04