Known Issue: Some Endpoints started to return "Bad request for URI" error after 8.55 version

[Yıldırım]

We've identified that undocumented Swagger Change released with Visma.net Financials ERP 8.55 version (29-06-2021) has caused an issue with some endpoints.

Following Endpoints started to return:

"Bad request for URI: /api/v1/{EndpointName}"/{ID} with HTTP operation: PUT with token scope: financialstasks"

Operation	Endpoint
PUT	api/v1/timecard/{referencenumber}
PUT	api/v1/expenseclaim/{expenseclaimnbr}
POST	api/v1/projecttask/{internalprojectid}

We're currently investigating the issue and checking that whether there are another endpoints are affected or not. Once the case analysed, we'll be able to share information in detail about this in the community.

We are sorry for the standstill this may have caused in your integrations.

[Yıldırım · Accepted solution]

Status:  Issue has now been resolved. We will continue to monitor the situation. Please let us know if you encounter any problems.

[Yıldırım]

Status: Although the issue had been resolved after the 8.55 hotfix yesterday, we've noticed that the "Bad request for URI error" is recurring on the following Operations

1. PUT  > api/v1/expenseclaim/{expenseclaimnbr}
2. PUT > api/v1/timecard/{referencenumber}

Note:  POST > api/v1/projecttask/{internalprojectid} is OK

We're currently investigating this.

[Yıldırım]

Status: Visma.net ERP 8.55 hotfix has successfully been released. Fix has been verified. Please let us know if you encounter any issues.

[Yıldırım]

Status: Fix has been planned to be deployed today, after working hours. No users will be affected since this is going to be a zero-downtime release.

[Yıldırım]

Status:  Issues have been addressed. We're currently working on a fix. We'll inform you about the planned fix deployment date once the development plan has been finalized.