V2 Mutations are poorly documented

monday Apps & Developers
1

Have Head Butted for a few hours how to change column values.

this is the most frequent change and the most annoying.

I get all the Query stuff and creating items seems to behave as well.

Is Anyone else using Insomnia to do their trial and Error.

Can someone share working examples for

mutation {
change_column_value(

it’s the only one I can’t make work. I just need to see valid examples without the JSON.Stringify abstraction.

2

Hey @nathank! Try something like this:

mutation {
 change_column_value(item_id:110125607, column_id:"status",board_id:110123920,value:"{\"label\" : \"Done\"}") {
   name
   column_values{
     id
     value
   }
 }
}

Let me know if that helps!

3

Thanks for that. Simple fields like date and text are behaving

it’s the quirks of the special columns now that are quite frustrating.

mutation {
  change_column_value(item_id: 272273710, column_id: "due_date4", board_id: 272273672, value: "{\"date\": \"2019-06-19\"}") {
    name
    column_values {
      id
      value
    }
  }
}

works fine but for email/link type fields I don’t seem to be able to get the strings happy.

How can the Phone field be Unsupported in the API ?

I like the Monday.com product but if an API is this weak it’s almost impossible to round trip and Sync Data from foreign tools.

4

Here’s an example string for the email column:
"{"email": "me@me.com", “\text": "its my email"}”

the link field is very similar, only with url instead of email like so:
"{"url": "monday.com", “\text": "go to monday.com"}”

we are working on the phone column, will be added soon

5

I miss the simplicity of XML, JSON made by and for hipsters working only with JavaScript. Lots of people actively dislike Javascript and JSON.

The Syntax is a Nightmare why make it this hard to enclose a Value Pair.

How long until V1 is turned off will happily abandon V2 if you will support V1 for at least a year.

Anything that parses generates a 500 Server Error at Best you get a 400 error invalid value or it won’t even parse. Has anyone got a truly working complete line of text that can be cut n pasted into Insomnia Client and worked.

mutation {
  change_column_value(item_id: 272273710, column_id: "email", board_id: 272273672, value: "{email: \"fake@alias.com\", \"\text:\": \"my email\"}") {
    name
    column_values {
      id
      value
    }
  }
}
6

Hey Nathan! Thanks for your feedback.

Looks like the JSON string you were sending in the value parameter was missing some escaped quotation marks and contained “text:” instead of “text”:

Try this and let me know if it works instead:

mutation {
  change_column_value(item_id: 162169283, column_id: "email", board_id: 162169280, 
    value: "{\"email\": \"fake@alias.com\", \"text\": \"my email\"}") {
    name
    column_values {
      id
      value
    }
  }
}

I definitely hear you in terms of adding those escape characters and trying to keep your JSON valid. What are you using to make the requests in your application? Happy to help you find a library that will help turn the JSON into strings and vice versa.

1 Like
7

How Do I give you a Lollipop or Beer that’s the winning Syntax.

8

Thanks Nathan! An emoji will do: :beers: :beers: :beer: :lollipop: