API change today related to updating checkbox columns

Hey there,

Looks like there was an api change today or recently where providing true and not “true” for checkbox column “checked” property stopped working when using a boolean and not a string. If anybody else experienced the same issue, here the fix:

{ checked: "true" } // instead of { checked: true }


Hey @rbabayoff :wave:

That sounds quite odd!

As far as I understand, you would always have to send the value you are trying to update as a JSON string, even if it is a boolean or a number. Can you clarify whether the way you were trying to update this previously had worked for you? It would also be really helpful if you could provide the exact query you were using before.

I’ll also check on this with the team on my end to see if there had been any updates here.


Hey Alex,

Yes, it worked for me before using a boolean. Since it’s an eazyform submission, the values are decided dynamically, so I don’t think the graphql mutation would help much, but here it is:

mutation CreateItem($boardId: Int!, $itemName: String!, $columnValues: JSON!) {
  create_item(board_id: $boardId, item_name: $itemName, column_values: $columnValues) {

If we’re already on the expected types subject, note that a graphql boards query returns the board id as a string and then when I’m trying to use the returned value in a mutation or another query as an input variable as you see above, the api complains that it’s a string and not a number. That is something that took me half a day to figure out in previous version of sdk, since I didn’t get errors back then.



Thank you for getting back to me on this!

Turns out, there was, in fact, an update here that has should make using some of our queries that work with updating column values and sending column values in general easier. Now, you can use change_simple_column_value to send values as strings, and not as JSON. We’ve now also applied this logic to the change_multiple_column_values, create_item, and create_sub_item so they accept those “simple” values as well - we’re now working hard to update the documentation on our end. Seems like this is the reason the behavior changed for you just recently.

What do you think?

Thanks for letting me know about the board ID being a string - that definitely sounds a little odd. I’ll pass that as feedback to the team as well.


1 Like

Awesome update @AlexSavchuk, finally an end to my annoying typos :smiley:

1 Like


Haha that’s EXACTLY what I thought too :heart: We are definitely keen on making using our API a little easier, and more updates are coming your way. :slight_smile: