Trying another endpoint (TotalSepaFileByPayrollRunId) I get a similiar response. Is this also not implemented yet?
Response:
itgensgr045
The table ‘LoketNlRest.PayrollRunDownloads.TotalSepaFileByPayrollRunId’ must produce data in at least one of the supported MIME-types: application/json, application/pdf, text/plain, text/csv.
Use another table or contact Invantive regarding extension on supported MIME-types.
What is the status on: LoketNlRest.PayrollRunDownloadsSepaFileBySepaFileId. Would that also be needing development first?
The message code itgensgr045 signals that the Loket API specification provides the data on TotalSepaFileByPayrollRunId in a format not yet supported. Currently the following formats are supported:
application/json
application/pdf
text/plain
text/csv
However, the message does not yet clearly display what the possible formats are. A change has been released that displays the formats that can be produced with itgensgr045. It is probably text/xml with the content wrapping another API-specification, but better to be sure.
Please reproduce the error on February 15, 2022 or later. Include the new extended error message as an answer.
Please also include the SQL-statement used to generate the message.
Can you illustrate what the exact error is with the other table PayrollRunDownloadsSepaFileBySepaFileId? Please include the SQL-statement too.
select *
from LoketNlRest.PayrollRunDownloads.TotalSepaFileByPayrollRunId('{validPayrollRunId}'
, 'Salary', 'BtchBookgTrue', '2019-08-24')
limit 1000
Response:
The table ‘LoketNlRest.PayrollRunDownloads.TotalSepaFileByPayrollRunId’ must produce data in at least one of the supported MIME-types: application/json, application/pdf, text/plain, text/csv.
Use another table or contact Invantive regarding extension on supported MIME-types to include at least one of application/xml.
But an error was returned due to missing scopes assigned to the Invantive client ID:
itgenlnr005
Insufficient rights for this request, reason: “Client does not have access to activity.”.
The remote server returned an error: (403) Forbidden.
The following query indicates the actual Loket API call made:
select url
, error_message
from sessionios@datadictionary
where successful = false
The issue can not be reproduced yet due to missing scopes on the Invantive client ID. A ticket was created with Loket (#216341) to acquire additional scopes. Once completed, this ticket will be updated.
But the metadata of Loket specifies that the payload should be named DOCUMENT in this specific case. An alternation has been implemented for this.
Currently, the metadata also specifies a BLOB and not a CLOB. This is subject to further research. However, research is currently awaiting additional scopes being assigned to the client IDs.
The maintenance of the Loket scopes is quite a burden due to the work needed and the number of individual scopes to be requested one-by-one. Therefore a policy change was introduced; changes to the standard Invantive client scopes can only be handled against a surcharge. Please contact sales@invantive.com for pricing. As an alternative, you might want to reach out to Loket and acquire a client ID.
There is a metadata issue on the Loket specification for XML-documents. Currently an error will occur on binary XML (itgenrst004). Once the metadata is corrected, the query will work. There are no plans to implement a workaround. A manual workaround would be to use NativeScalarRequests to construct the request in code and workaround the format issue.