Optional values in update mutation

[atelierJVA]

Hi,

I am using Hasura Cloud( v2.0.8-cloud.3), and I want to use a single mutation to update a table, depending on what specific values the user changes in the app. One requirement is that it would be used both via Graphql and a corresponding REST endpoint, thus preventing rewriting the operation in the client.

The mutation is:

mutation update_property_by_id($id: Int!, $address: String, $valuation: numeric, $hidden: Boolean) {
  update_properties_by_pk(pk_columns: {id: $id}, _set: {address: $address, hidden: $hidden, valuation: $valuation}) {
    id
    address
    hidden
    valuation
  }
}

and if I pass the following variables:

{"id": 2,
  "address":"6 High St"
}

I get the following error:

{
  "errors": [
    {
      "extensions": {
        "path": "$.selectionSet.update_properties_by_pk.args._set.valuation",
        "code": "validation-failed"
      },
      "message": "unexpected null value for type \"numeric\""
    }
  ]

Is there a way to configure Hasura to ignore missing variables?

Thanks

[stayingcool]

Does the same mutation work in Hasura Console?

[BenoitRanque]

This is due to a change introduced in #704

In short: you should use the parent type as input type, and instead of providing a null value when you wish to omit the field, omit the field from the variable.

Example for your mutation:

mutation update_property_by_id($id: Int!, $setInput: properties_set_input!) {
  update_properties_by_pk(pk_columns: {id: $id}, _set: $setInput}) {
    id
    address
    hidden
    valuation
  }
}

Assuming you only want to update the address field, your variables would then look like this:

{
  "id": 2,
  "setInput": { "address":"6 High St" }
}

[PopBot]

Thank you so much! Spent a lot of time on this issue. It still works as of March 13, 2022.