My Products
Help
Eivfjeld
CONTRIBUTOR **

generalLedgerPeriodBalance timeout

by Eivfjeld

Hi

Why is the following query using generalLedgerPeriodBalance resulting in a timeout?

 

{ useCompany(no: 3757847) 
{generalLedgerPeriodBalance (first: 10)
{ items  { accountNo, year, period, obDomestic, cbDomestic } } } }
 
{
  "errors": [
    {
      "message": "Error trying to resolve field 'items'.",
      "locations": [
        {
          "line": 5,
          "column": 7
        }
      ],
      "path": [
        "useCompany",
        "generalLedgerPeriodBalance",
        "items"
      ],
      "extensions": {
        "code": "TIMEOUT",
        "codes": [
          "TIMEOUT"
        ]
      }
    }
  ],
  "data": {
    "useCompany": {
      "generalLedgerPeriodBalance": {
        "items": null
      }
    }
  },
  "extensions": {
    "vbnxt-trace-id": "0000000000000000679f71caa1b339f2"
  }
}

{
  "errors": [
    {
      "message": "Error trying to resolve field 'items'.",
      "locations": [
        {
          "line": 5,
          "column": 7
        }
      ],
      "path": [
        "useCompany",
        "generalLedgerPeriodBalance",
        "items"
      ],
      "extensions": {
        "code": "TIMEOUT",
        "codes": [
          "TIMEOUT"
        ]
      }
    }
  ],
  "data": {
    "useCompany": {
      "generalLedgerPeriodBalance": {
        "items": null
      }
    }
  },
  "extensions": {
    "vbnxt-trace-id": "0000000000000000679f71caa1b339f2"
  }
}

 

 

 

 

 

 

 

 

2 REPLIES 2

by Marius Bancila

I can confirm this is due to a bug on our backend that has been already reported with a query for another view. We are investigating the problem.

Here is a link to the other bug report for the same problem that we got: https://community.visma.com/t5/Diskusjon/Outstanding-amount-per-customer/m-p/585629#M291