Deprecated features
The features listed in this section are deprecated and will be removed in future versions of the API.
Deprecated features
Sorting order argument
The sortOrder
argument has been replaced by the orderBy
argument. The orderBy
argument is similar to sortOrder
, except that it is an array of objects instead of a single object. For more details see Sorting.
This feature will not be available after February 1, 2026.
Suggesting argument
The suggest
argument has been replaced with passing null
to values or using the field_suggest_interval
fields. For more details see Suggesting values.
This feature will not be available after February 1, 2026.
Aggregates
The schema section that enables fetching of some aggregate values is obsolete and has been replaced with a more complex reading using grouping. For more details see Grouping.
This feature will not be available after February 1, 2026.
Deprecation warning
Every time a deprecated feature is used in a query or mutation, a warning will be included in the response, as part of the extensions
. The response data
is not affected. The warning includes a message explaining what is deprecated and what should be used instead, as well as the path to the deprecated feature in the query or mutation.
Here is an example:
query read($cid : Int)
{
useCompany(no: $cid)
{
generalLedgerAccount(first:2,
sortOrder : {accountNo : ASC})
{
items
{
accountNo
name
}
}
}
}
{
"data": {
"useCompany": {
"generalLedgerAccount": {
"items": [
{
"accountNo": 1000,
"name": "Forskning og utvikling"
},
{
"accountNo": 1020,
"name": "Konsesjoner"
}
]
}
}
},
"extensions": {
"warnings": [
{
"message": "The argument 'sortOrder' is deprecated and will be removed. Use 'orderBy' instead.",
"path": [
"useCompany",
"generalLedgerAccount"
]
}
],
"vbnxt-trace-id": "83bcb079fb2c8..."
}
}