Hi, Could you send us an example JSON? Does it happen to contain any items that are kits or parts of kits? ... View more

Did you test the same but with a normal TR order? We have not been able to reproduce the issue so far.  ... View more

Hi, We have still not received any updates regarding the case. If you have any concerns regarding the solution/implementation time of this case, we recommend that you get in contact with your partner service. Thank you.  ... View more

Hi, Please send us the results from the query to developersupport@visma.com and we'll have a look at it and raise it with the development team.  Thank you.  ... View more

Hi, Are you getting pages with a lower count than 159, and if so are you getting any result from the next page? How are you handling it on your end and how are you counting the duplicates? Thank you.  ... View more

We were not able to reproduce the same issue:   Have you tried this before with the custom SO type?  ... View more

Hi Erik, It sounds like this issue behaves in a similiar way of entering a purchaseOrder via line to a purchaseReceipt, in which case the recommended way to do this would be to first create an empty receipt first and the put the lines after. We'll test it and get back to you shortly. ... View more

You should probably set up more priceclasses for what you are looking for, for more information on how to best do this I recommend that you get in contact with partner service, they will have better understanding of how to set things up in the ERP for the workflow that you have. ... View more

From what I've tested, creating a new price worksheet and releasing it it sets the previous price to have an expiration date if not set to be until the last day before the new pending price that you have set for the codes is taken into effect: So creating a new price sheet sets the new prices in the salesPrice window, in effect at the date you choose, so essentialy for every combination with the same data on the rest of the row, it will create a new entry with the new price. There is no history or origin field available, and only one combination with the same data can be active at the same time.  ... View more

As far as I know the prices from the price worksheet(Prisavtal) enters a new line in the customerSalePrice window. In your screenshot form the price work sheet, it has been setup to overwrite overlapping prices, and has been setup with a expiration date, I'm guessing this is the issue, or am I misunderstanding what you want to do?    The price itself does not come from the price code, the price code is just an indication on what it will be applied to, in this case customers that have been setup to use prices connected to customer price class 2. If you need extra information for where/how this discount was created it as you said need to be posted in the ideas part of the forum to extend this endpoint with some sort of history field. ... View more

Hi, The customerSalesPrice endpoint should provide the same information that can be found in ScreenId=Ar202000:   Could you send us the result JSON and screenshots of where this information is mismatched? ... View more

Thank you, we'll test it and send it on to the development team. ... View more

Hi, So would you say that the original issue in this thread is solved or is this still causing an issue for you? 1. Shipping address causes CustomerVatZone to be omitted. 2. Ship via causes CustomerVatZone to be omitted. Are both these issues true for you? ... View more

Hi, You don't need to delete the whole discount, only the line that you wanted to update originally. Do this with the line operator "delete" via a put call. The numbering when inserting is omitted, as with other endpoints as well, it is only taken into account when you are using "Update" or "Delete" operators.  The series value gets set according to your settings in the discount code window, if it's set to autonumbering and the conditions of the discount is different from the other series it will be autogenerated: ... View more

Hi, As far as we can see, this was not included in V1/CustomerCreditNote either, if this is a field you need to have available for POST V2/CustomerCreditNote and PUT V1/CustomerCreditnote we recommend that you create a post in the Ideas section of the forum. Thank you.  ... View more

Hi, It is still in the backlog, we have asked the development team for an update. ... View more

Hi, We can confirm that there seems to be an issue using the line operator "Update", we will report this to the development team. On our end we are not having any issues using the "Insert" operator, below example works, and until fixed the workaround would be to insert a new line and delete the old line if needed: {   "discountCode": {     "value": "1"   },   "series": {     "value": "10001"   },  "discountBreakpoints": [     {       "operation": "Update",       "lineNbr": {         "value": 1       },       "pendingBreakAmount": {         "value": 5       },       "pendingDate": {         "value": "2022-04-25T06:40:34.062Z"       },       "pendingDiscountPercent": {         "value": 10       }     }   ] } ... View more

Could you please send us the company Id as well and we'll check if we can see any duplicates on our end. Thank you.  ... View more

Hi, Could you please check in the UI under the "Webhook notification" tab if the confirmed event shows up twice? Have you seen any patterns to what events are sent twice? ... View more

Hi, We can confirm this is not currently included. You'd have to determine if it's domestic or international by the description of the zone if you try to determine it via the API. Generally we recommend handling VAT automatically in the ERP when using the API. If you need the functionality of seeing the Vat Id's under the VatZone endpoint, we recommend that you make a post in the Ideas part of the forum. Thank you.  ... View more

Hi, Yes that should give you the correct VatId "01" since it is in both lists.  ... View more

Hi, The Vat ID(and the Vat rate) can be the same for several Vat categories. If you look up the customers Vat Zone(ScreenId=TX206000) in this case 01: And then the invoiceLines / inventoryItems Vat category(ScreenId=TX2055PL) in this case 3: The Vat Id applied will be in both of those lists(ScreenId=TX205000) in this case 3: The Vat rate can be seen under Vat Id -> Vat schedule:   Example of how the invoice has it applied in the UI:     Support in this part of the forum is in English as this is an international forum. If you need more help with how to determine correct Vat settings or information on how to find it, we recommend that you speak to an ERP consultant or write in the ERP forum for your market: Contacting Visma Partner Service / Visma.net ERP Support ... View more

There was a fix relating to rounding difference when you do not specify Vat details that was released in 8.89.0, this is under a feature toggle which we could activate for you. But the limit on decimals was introduced in 8.16.0. As far as we can see, these are the only changes made to currency rounding differences.  Release notes 8.16.0: Decimal precision for base currency Purchase invoices (AP301000) The decimal precision for the base currency setting is now set to max. 2 decimals.   Release note 8.89.0: RoundingDifference omitted when using SupplierInvoice endpoint (POST) Earlier, in some circumstances, the RoundingDifference amount was omitted when creating an invoice via the SupplierInvoice endpoint (POST). This has now been fixed, and the solution is under a feature toggle. ... View more

Hi, My mistake, you need to: 1. Check the customers Vat Zone - Get /controller/api/v1/customer/{customerNumber} 2. Get the Vat zones applicable Vat Id's -Get /controller/api/v1/vatZone/{vatZoneId} 3. Get the invoice lines Vat categories applicable Vat Id's -Get /controller/api/v1/vatCategory/{taxCategoryId} 4. The Vat Id needs to be a value found in both lists. - Get /controller/api/v1/vat/{vatId} For more information on how Financials handles handles Vat we recommend that you check with the ERP support.  ... View more

Hi, Visma.Net Financials does not support 3 decimals in the rounding difference, it supports a maximum of 2 decimals. This has been true since at least version 8.16.00.    ... View more

Hi, You should be able to find the same information in the UI as via the API: Simply check the VatId on the line and get it via /controller/api/v1/vat/{vatId} If you want to know how the VAT is applied in Financials, you can read some more in this article: TaxID '01' cannot be found in the system ... View more

Hi, Yes the case is currently waiting to be picked up for from the developers. We'll inform when we have more information. Thank you.  ... View more

Sure, we can have a look and see if it is related at least. This case does not seem to be solely API related as well, since the same issue occurs when trying to do it via the UI as well.  ... View more