Suggest values failes today

[Florian Haase]

Hi,

I get feedback here internally that the following mutation worked yesterday  but not today:

mutation {   useCompany(no: 3542724) {   associate_create(values: [{name: "Mark Ward", addressLine1: "Test Rd 1", shortName: "Mark", customerNo: null, supplierNo: null, employeeNo_suggest_interval: {   from: 500,   to: 1000 }}, {associateNo: 1203, name: "Ron Johnson", addressLine1: "Test Rd 1", shortName: "Ron", customerNo: null, supplierNo: null, employeeNo_suggest_interval: {   from: 500,   to: 1000 }}])   {     affectedRows     items {       associateNo, customerNo, supplierNo, employeeNo, name, shortName     }    }   } }

Results in following error-messages today:

{

    "errors": [

        {

            "message": "Error: SQL command no. 2413 failed.Error: Database error.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "Error: SQL command no. 2413 failed.Error: Database error.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "Error: SQL command no. 2413 failed.Error: Database error.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "Error: With multiple account no series and use of account no series activated, use SuggestValueInInterval instead.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "Error: SQL command no. 2413 failed.Error: Database error.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "Error: SQL command no. 2413 failed.Error: Database error.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 0

                }

            }

        },

        {

            "message": "A record with the same primary key already exists.",

            "path": [

                "useCompany",

                "associate_create",

                "values/1"

            ],

            "extensions": {

                "data": {

                    "status": 3

                }

            }

        }

    ],

    "data": {

        "useCompany": {

            "associate_create": {

                "affectedRows": 0,

                "items": null

            }

        }

    },

    "extensions": {

        "vbnxt-trace-id": "00000000000000009f8bb9cc66e8e794"

    }

}

[Øyvind Årseth]

To follow the status: https://status.visma.com/incidents/dhqjdnqv4g0w

[Florian Haase]

Sorry it's not 100% confirmed here that the GraphQL has not changed since yesterday. Not sure that it is related to the upgrade. 

But following more simple example does not work either:

mutation {

  useCompany(no: 3542724) {

  associate_create(values: [{associateNo: null, name: "tommy1"}])

  {

    affectedRows

    items {

      associateNo, name, shortName

    }

   }

  }

}

Is something wrong with our GraphQL here?

"errors": [

        {

            "message": "A record with the same primary key already exists.",

            "path": [

                "useCompany",

                "associate_create",

                "values/0"

            ],

            "extensions": {

                "data": {

                    "status": 3

                }

            }

        }

    ],

Florian

[Øyvind Årseth]

Hi Florian

Pretty sure you've run into an unfinished database upgrade causing the SQL-errors.
We've had issues on some dbs during the upgrade following today's deployment, so it is still in progress. 

Øyvind