You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We found an unexpected case in the accounts API. If the displayName contains a / the POST request will fail and the provider will show an error event like this: API Error: Request payload is invalid, Code 11000. What exactly was the problem we could only find by debugging the issue in dev mode. The raw response from the API contained more details on what the issue exactly is.
Describe the solution you'd like
Reflect that more precise error in the responses as well. See snippet below for how the structure exactly is.
Make sure the implementation is able to use the additional details where specified, but falls back to a more general error otherwise. Needs to be tested with other known errors like 409 for naming conflicts to make sure old errors properly convert as well. Also ideally this solution should be applied to any accounts api request where it can be expected (not just POST).
We can't know for sure, but this details section in the response probably is new. Ideally we should use this occasion to raise a support ticket to update the documentation to reflect the proper schema: https://api.sap.com/api/APIAccountsService/path/createSubaccount
The details is contained there, but the overall structure is incorrect, which we internally modified in the generated client to compensate for that.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We found an unexpected case in the accounts API. If the
displayName
contains a/
the POST request will fail and the provider will show an error event like this:API Error: Request payload is invalid, Code 11000
. What exactly was the problem we could only find by debugging the issue in dev mode. The raw response from the API contained more details on what the issue exactly is.Describe the solution you'd like
Reflect that more precise error in the responses as well. See snippet below for how the structure exactly is.
Make sure the implementation is able to use the additional details where specified, but falls back to a more general error otherwise. Needs to be tested with other known errors like 409 for naming conflicts to make sure old errors properly convert as well. Also ideally this solution should be applied to any accounts api request where it can be expected (not just POST).
Additional context
Example raw response:
We can't know for sure, but this
details
section in the response probably is new. Ideally we should use this occasion to raise a support ticket to update the documentation to reflect the proper schema: https://api.sap.com/api/APIAccountsService/path/createSubaccountThe
details
is contained there, but the overall structure is incorrect, which we internally modified in the generated client to compensate for that.The text was updated successfully, but these errors were encountered: