Hi, Could you please include the ScreenID and we'll have a look to see if it is exposed. Thank you.  ... View more

Hi, We can confirm that when sending multiple lines via POST, only the last financialPeriod is used on all lines. The same seems to be true for PUT as well, sending multiple lines with financialPeriods will update all lines to the last occurring period. We'll open a case with the development team. Thank you.    ... View more

Hi, A fix for this has been planned for version 8.87.0:  Visma.net Financials API updates for version 8.87.0 (March 2022) Release date for 8.87.0 version has been planned as 08/03/2022. ... View more

Hi, We're not able to reproduce this issue, could you please try the operation via for example Swagger? When trying on our end we receive the subAccount object back, but with no segments that have been modified: ... View more

Already exposed via the PurchaseReceipt endpoint. ... View more

Hi, Are you having issues with this endpoint? You should be able to set the type to "TransferReceipt" when posting: ... View more

Hi, The paymentMethod field is not available for the POST customerCreditNote endpoint, neither in V1 or V2. If this is functionality you need, we recommend that you create a post in the "Ideas" part for the forum. Thank you.  ... View more

Hi, You need to set "Validate document details on entry" to true in Supplier ledger preferences(ScreenId=AP101000) to send the "amount" field:   ... View more

Hi, Unfortunately, we can't give you a answer on how the entries should be made on the API team. You should check this with your partner service, or ask your client regarding how the entries should be made. You can check what ledgers the company you are targeting has via the ledger endpoint: And what accounts they have via the account endpoint:   ... View more

Hi, Could you please send us a screenshot of the ledger(802000) used from the UI(ScreenId=GL201500): Also, is it correct that you use ledger: "802000", send a debit to account: "802000" and a credit to the same account: "802000"? As far as we know this would not do anything else than create a entry that in effect does nothing. ... View more

Hi, Could you please send us the full JSON and we'll try to replicate it in our enviroment. Thank you.  ... View more

Hi, On the API team we are unable to help you with this, your partner service is your contact point for issues regarding the company's setup. Currently we have no way to do this via the API. Please contact your partner service for this. Thank you.  ... View more

Hi, It's currently not possible to filter on the supplier, it sounds like you can rework the current workflow to minimize the amounts of calls that you make but just getting all documents modified since the last time you checked and the work with the result set on your end. the "lastModifiedDateTime" should be ">" not "Greater than". Please try to correct this. ... View more

Hi, As this is not currently available via the API, you can read here how to set "Send to Approval" to default in FInancials: Override Send to Approval as the default action   ... View more

Hi, If you call the supplierInvoice endpoint with the parameters for createdDateTime or lastModifiedDateTime & conditions you should be able to do checks for this for the scenario you want. The example and values for the parameters works for the "createdDateTime" & "createdDateTimeCondition" pair as well. Depending on exactly what you might want to do, you might prefer one over the other. Update the dateTime to when you last checked if you had any new values. Example of usage with parameters Query parameters: lastModifiedDateTime=YYYY-MM-DD As of today Filtering Parameters does not accept certain characters such as W-Z These are the formats for Filtering *2001-01-01 *2001-01-01 13:13:13 *2001-01-01 13:13:13.133   lastModifiedDateTimeCondition=Operator Supported comparative operators for LastModifiedDateTime Conditions on filtering  > - Greater than < - Less than <= - Less than or equal to >= - Greater than or equal to ... View more

The neXtGen salesOrder inventory endpoint is a lot faster in our example company, for the data set we have in our test company it's about 2-4 times faster, so it might be a solution that would be worth having a look at for you.  We are also working on improvements for the current Inventory endpoint, unfortunately the latest improvement had caused some issues and needed to be rolled back for now.  ... View more

Hi, What is your current workflow?  Is there any information you are looking for in the inventory endpoint except, Internal ID -> External ID? If not, storing the connection might be a good idea, and then just updating that record with newly added inventory items.   ... View more

Hi, We have asked the development team for an update. Thank you for your patience.  ... View more

Hi, Please send the fields like this, as per the Swagger documentation: "subaccount": [ { "segmentId": 1, "segmentValue": 064 } ] ... View more

Hi, We can see that there are some error that popped up from about 9.30-40, but seems to have calmed down. Are you still having issues? ... View more

Hi, Could you please elaborate on how you do, what you would like to do today via the UI? Please include screenshots as well as screenId's and we'll take a look at it. Thank you. ... View more

Hi, So far what we have tested does not seem to be causing any issues. Are you still having issues? Please send us the full URL / timestamp so that we can share this with the development team if needed. Thank you. ... View more