De volgende melding treedt op bij ophalen van de GLAccountClassificationMappings
op twee Exact Online administraties:
itgenoda055
Request timeout.
Please consider reducing the scope of your request or retry to send the message.
The remote server returned an error:
(408) Request Time-out.
De gebruikte OData4-URL is:
/acme-exact-online-15/odata4/ExactOnlineREST.Financial.GLAccountClassificationMappings@eol?$filter=%28Division%20eq%203186747%20or%20Division%20eq%203180620%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%20or%20Division%20eq%20null%29%20and%20GLSchemeCode%20eq%20%271%27
Omgezet door Bridge Online in SQL luidt die:
select t.*
from ExactOnlineREST.Financial.GLAccountClassificationMappings@eol t
where (((((((((((((((((((Division in (:w1, :w2)) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) or ([Division] is null )) and ([GLSchemeCode] = :w3))
De uiteindelijke API-call die faalt is:
De foutmelding treedt regelmatig op (meerdere malen per nacht) en op meerdere databases.
De foutmelding is ook consistent op te wekken met de volgende query in de web SQL Editor:
select /*+ http_disk_cache(false) http_memory_cache(false) */ *
from ExactOnlineREST.Financial.GLAccountClassificationMappings@eol t
where GLSchemeCode = '1'
Deze query met toevoeging limit 5
is na 18.697 ms klaar, terwijl dit maar 1 API-call behelst. Dit is ook terug te zien in de SessionIOs@DataDictionary
:
Het eigenaardige is dat API-calls zonder een GLSchemeCode
mee te geven circa 100x sneller klaar zijn:
Het verwachte resultaat is 958 rijen met GLSchemeCode 1 uit een totale inhoud voor deze twee administraties van 4508 rijen.