strange characters in webbhook uri ?

[Gabriella Hennings]

Hi 

When we are using the weeb hooks for inventory, but the Uri which is returned in the weeb hooks message looks quite strange and will be diffult to work with. And it seems like it's only from the Uri where we can extract the inventorynumber? 

(when we check in the visma.net gui there is no extra characters in the inventory numer apart from the matter that it looks like visma is adding alot of spaces after the number. 

 

[Yıldırım]

Hello, 
based on financials company segment / numbering setup white & trailing spaces are encoded to "+" character in the "relativeResourceUri" & "resourceUri" after the inventory id. 

We have an improvement case registered in our backlog. However, this is currently not prioritized, we'll update the case and emphasize the issue once again.

• Trim trailing spaces on the server side before sending the webhook notification.
• Alternatively, return b64(xxxx) encoded values in the "relativeResourceUri" & "resourceUri" for the objects that contains reserved characters / White & Trailing spaces.

Currently, handling the trim method on the client side appears to be the only way to cope with the case.