Getting same issue on many clients. How can we resolve it? ... View more

Hi, The original cause for the issue posted here should have been resolved. Could you please check the following: "Requested on" date on the header and lines are the same date or earlier than the date you have set for your shipment   Also, please try to release it in the UI, it should show you what the issue is. Thank you! Kind regards Sandra Anté ... View more

Ok this is helpful information. We need to investigate this further, and because it seems really client sensitive, I advise you to seek country specific support. Please take a look at the following on how to get support. Refer to this post in your initial contact.  https://community.visma.com/t5/News-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/ba-p/633804 ... View more

Hei Steinar, I've managed to reproduce the trailing space issue. It appears to be happening with the newly created Warehouses, perhaps something change between the versions. Unfortunately, I don't have information about the exact version / date. However, this has now been reported to the team.  ... View more

Hi, this case has been registered in the backlog and currently there is no information when it can be exposed.  We'll merge the thread with an existing "idea" and keep the topic informed as more information is available.  ... View more

You're welcome 😀 ... View more

Sorry for late reply, missed this message. Yes this is ticked off, both currency and rate override.    ... View more

Hello, we've informed the infrastructure team regarding this. Could you please inform us on the company ID that you receive the mentioned error ?  ... View more

For the breaking changes we will follow the same guideline as what is today in the Visma.net ERP API, i.e. latest 3 months before. In the closest roadmap we have not planned to introduce createShipment in V3. Could you elaborate a bit more for why it is highly needed in V3? Is it, for example, for the easier use of the API through the sales process or expectation of better performance in that endpoint etc? ... View more

Hi, We've been unable to recreate this issue so far. Could you please send us an email with the companyID, details regarding how this was set up? The development team will have to take a look at the company database. Thank you.  ... View more

i Got it working my local cashe where playing a trick on me Ctrl+Shift+R got it working. have u seem my question regarding findings in regards to warehouse and toWarehouse filtes ?  it seems like toWarehouse filter only works if used WITH warehouse and not alone  is this intended ?  ... View more

Hi, we also have a customer that is in need for POST and PUT pending cost. Will this be available anytime soon? ... View more

Hi,   Getting back with more details about the problem from 21st of June.   Around the interval: 2023-06-21T02:10:00.406+03:00 and 2023-06-21T10:38:26.406+03:00 most of the calls to the Sales Order Service API returned 500. We have restarted the cluster of the service and then calls got back to normal.   While investigating the cause of this we noticed that the calls our service makes to another internal service to retrieve information about a tenant are failing with an Unauthorized exception. From the logs it seemed that Authorization header was not included in those calls. Restarting the cluster fixed this problem but we created a task to further investigate why the Authorization header was not included and another case to improve the code to be more resilient when making calls to this internal service.   Another action point for us is to improve the monitoring. The current monitoring detected the errors but we did not have any alarms set for a high rate of them. We will implement a warning when the error rate reaches 20% and a critical alarm for Central Operations when the rate reaches 50%. This will allow us to respond faster when something similar might happen. ... View more

Hello  Steainar, we've informed the team on the importance of the implementation, we'll share information once we receive an update. ... View more

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?   ... View more

Hello,  the error was related to the load balancing and how the requests get distributed when one of the servers have been heavily loaded. We have increased the number of servers, aiming that load will be more evenly distributed. We're currently monitoring the status, and it seems that action helped to resolve the issue. Please let us know if you still receive the error. We're sorry for the standstill this may have caused in your integrations.  ... View more

Is this in the road map? ... View more

Hei Steinar, thanks for the info ! Please let us know if you experience the same issue again, then we can look into that together.  ... View more

Hi Steinar, For the Employee API, you can send your questions to cloud.api.support@visma.com. We have informed them about your questions as well. ... View more

Hello, the request is still in the backlog, and currently it has not been prioritized. We will provide further updates as more information is available.    ... View more

Hi We solved this issue now, the solution was not to send location o the allocation lines.   brgds Steinar ... View more

Is there any progress here? We also do need that.   Florian ... View more

We also need crossReference for POST, in the current API and NextGen.   ... View more

Is this still happening? The development team is looking in to the issue.  ... View more

The feature causing the issue has been toggled of and the fields are now available on post.  ... View more

This does not look like a companyID, could you please doublecheck? ... View more

I did the same test now and it seems to be working as it should and using the correct sales account. I am not able to reproduce the same error,  so I believe that this case is not relevant anymore. Maybe Florian still has the same problem?   ... View more