Hi,   We would reccomend that you log the request ID as it helps for us to find the request in our logs. What is the full exception message?   Some timeouts are to be expectred, have you implemented a retry function?   ... View more

Hi,   Could you please share some instances of the timeouts? Timestamps, ipp-request-id, company-id and endpoints.   Do you have a timeout in place on your side? How long time generally passes before a timeout?     ... View more

Hi,   Could you please try to set the "Enable currency overide" on the supplier and try again?   ... View more

Hi,   We sent you an email asking for what customers this happens to, is it still an issue?    Thank you.  ... View more

Try to increase the timeouts and see if it helps.   What you can do to make sure the objects does not exist is to PUT -> If statuscode is 404 POST it, if you receive the exception, retry PUT etc. ... View more

Hi, To some degree this is to be expected, do you have a retry mechanism in place?   How often are you experiencing this rate of exceptions? The error message is for a network connection reset, do you have any timeouts on your end? ... View more

A case has been opened with the developers.   The progress of this case will be reported in this thread.   Thank you.  ... View more

Hi,   Can you please point us to what screen and field from the UI you are refering to? As of now, there does not seem to be anything related to salesCategory exposed in the Inventory endpoint, and I was not able to find the field in the UI ScreenId=IN202500 either.   If it is not available in the UI, it will not be available in the API either.   For suggestions of improvements, we would suggest that you head over to the Ideas section where other community users also can vote for your ideas. This will influence the priority of the case when the developers are deciding which features to include in the updates.   Please let us know if we can assist you with anything else. ... View more

As the API will follow the behaviour of the UI, ultimately, all cases concerning the UI will also affect the API. Are you seeing this issue on all companies or is it only on one?   In my test, I tried the same steps as you as well as saving between each step and the result is the same, when adding a line, my lineNumbers increase.    In this post are the contact details: Contacting the Visma.Net ERP Support / Partner Service ... View more

Hi,   Even when trying this in the UI we are not able to reproduce the issue, please see attached.   As this case is in regards to the UI functionality, we would recommend that you get in contact with the ERP support as we on the development team handle API related cases.  We would agree this is abnormal behaviour, the lineNumber should be incrementing both when deleted/inserted from UI and API. ... View more

Hi,   We can confirm that the customerDocument endpoint does not contain the "applications" field, we will open a case with the developers and get back to you in this thread when we have more information from the developers.  ... View more

Hi, We are not able to reproduce this in our local test.   We tried this with both stock & non-stock items.   Steps taken Stock item lines: Non-stock item lines: SO created with 1 line Item on line 1, allocation on line 2 Item on line 1 PUT line delete Empty Empty PUT insert line Item on line 3, allocation on line 4 Item on line 2   Could you please share the JSON that was used to deleted & insert the lines? ... View more

Hi,   We'll have a look at this and get back to you.  ... View more

Yes, there is a default maxSize, this can be changed at any point, you can see the latest default if you have a look at the news page: Enforcement of pagination on API endpoints and change of maxPagesize - September release (8.25)   We will always try to make sure to share any changes to pagination settings on the news tab.   As of right now, the default maxSize has been changed to 500, as can be seen in the metaData in the response of the request.   This means that you now that unless you provide pageNumber & pageSize that is lower than 500, you will always get a response that contains up to 500 documents from page 1.    So the way that you would know it upfront depends on your integration, are you displaying all documents in one list or do you use pages? If you have a pagination in your integration you would know by sending the parameter with that page size, and you know that if you do not set it, the default size will be 500 as of right now.  ... View more

Alright, so if I understand you correctly, up until now when you have not had the need of presenting the payment date, there has been no problems, but since you've been asked to include this, you have hit a "performance wall"?   Regarding the 10 requests parallel, according to tests made by one of our users, the best performance is reached by running 10 parallel requests, meaning make sure that you do not just have 1 request going at a time, but say that you have 12 pages you need to get, send the request for those first 10, whenever any of the requests are done, send of the next one and so on. ... View more

Hi,   Just to clarify, the only reason you are using the customer/customerNr/documents endpoint is that it is faster that just getting customer/customerNr/invoice, but the only thing you want from the documents endpoint is the invoices?   To reduce the load, we would advise that you use more parameters to limit the amount of data that needs to be fetched, for example using the status and lastModified, depending on the information you need from the result, already paid documents could be stored on your end to limit the data needed to be fetched.   Also, the most optimal way to handle this is to have 10 requests running parallel when talking about time.   As of now, 100 is the default maxPageSize, so unless you specify a lower number, the pageSize will always be 100.   ... View more

Hi,   We have sent you an email in regards to this issue, please have a look at it.   Thank you.  ... View more

Hi,   In the current solution, the release actions for PurchaseReceipt, and other endpoints works by starting the process as a background work, in the same way as when pressing "release" in the UI. As such, if the release actions fails, there will currently not be any error message returned.   There is currently a case in the backlog for implementing an error when the release fails, we will provide more information when the development team has provided us with more information/decided on a date this will be included.   Thank you. ... View more

Hi,   When we have encountered this before it has been due to a corruption in the database.   Please let us know what company-id this is happening for.   Thank you.  ... View more

Hi, Rrgarding ideas for Visma.Net Financials, we have a section where you can post these: Ideas There improvements can be posted and voted on by the community.   As mentioned, for now we are waiting for the development team to have a look at this issue, however the addresses provided in the documentation(attached here again for ease) are still valid. ... View more

While we are waiting for a solution as a sidenote/workaround, you only need to authorize once with your API user as there is no time limit/need to refresh the token in Visma.Net authorization.   If you have authorized once, for all companies the user has access to, it will be valid, as it is written in the documentation that is provided in the ISV certification program. ... View more