Release Notes Documentation Inner exception and stack trace displayed when receiving error on GET Customer with attribute filter Previously, when filtering on attributes on the GET Customer API endpoint, you could in some scenarios get an inner exception displayed in the response. This has now been fixed. In addition, the Swagger documentation for the GET Customer, GET Inventory and GET CustomerContract endpoints, related to filtering on attributes, has been improved. POST V2/salesorder/{salesOrderNbr}/action/createShipment always results in a customer ledger document of the Credit note type Earlier, for shipments created via the POST V2/salesorder/{salesOrderNbr}/action/createShipment endpoint, the Prepare invoice action always created invoices for the type Credit note. This has now been fixed. Wrong "Location" URL returned after successful POST CustomerCreditNoteV2 request Earlier, the wrong "Location" URL was returned after a successful POST CustomerCreditNoteV2 request. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023 ... View more

  Release Notes Documentation "Same as main" incorrectly set in Suppliers window for suppliers created via API Earlier, the Same as main option was incorrectly set in the Suppliers (AP303000) window for suppliers created via API. This has now been fixed. The solution will be deployed in production under a feature toggle.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01,2023 ... View more

Release Notes Documentation Not able to set termStartDate and termEndDate for prebooked invoice via  Supplier Invoice API Previously, you were not able to set termStartDate and termEndDate for prebooked purchase invoices (P301000) via PUT - SupplierInvoice endpoint. This has now been fixed. Due dates for breaking changes Documentation Due The following flags on the Branch endpoint will be set to false by default, starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023     ... View more

Release Notes Documentation Allocation for purchase receipt with lot/serial numbers Earlier, you got an error message when adding a purchase order or purchase order lines to a receipt with the POST/action and if Lot/serial class had the Automatically generate next option unchecked and when received. This has now been fixed. The field KitItem not exposed in the Inventory DTO Earlier, the field KitItem was not exposed in the Inventory DTO. This has now been fixed. Cost property added to customerInvoice, customerDebitNote, customerCreditNote and customerOverdueCharge lines The GET and GET range customerInvoice, customerDebitNote, customerCreditNote and customerOverdueCharge now include Cost property for the lines. This value reflects the total cost for the line in the base currency, when the document is released. This enables you to calculate profit and margin for the line, when compared with the line’s Amount. Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default, starting from 13th of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 202 ... View more

Release Notes Documentation New endpoints for LotSerialClass There are new endpoints for GET api/v1/lotserialclass/[classId] and GET api/v1/lotserialclass. Not possible for any sales order to create two shipments from two different warehouses Earlier, for any sales order, it was not possible to create two shipments to be sent from two different warehouses. This has now been fixed. API JournalTransactionV2 now accepting subaccount segments containing spaces Earlier, the JournalTransactionV2 did not accept Subaccount segments containing a space. This has now been fixed so that you can use "1" or "1 " if you have a segment with length 2, but it contains only one character It also works with a default sub containing a space. If you have a segment value starting with a space, that will not be accepted in the API or in the UI.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default, starting from 13th September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01,  ... View more

Release Notes Documentation GET customerPayment endpoint (All & Specific) does not retrieve the Balance write-off value  Earlier, the GET customerPayment endpoint (All & Specific) did not retrieve the Balance write-off value. This has now been fixed. GET item range does not return lot/serial class IDs Earlier, GET item range did not return lot/serial class IDs. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default, starting from 13th  September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01 ... View more

Release Notes Documentation Breaking change on Inventory endpoint GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 9.01.0, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE2' not found"} Sales order replaces customer values for Invoice contact and Delivery address contact with "string" Earlier, sales orders replaced the customer's values for Invoice contact and Delivery address contact with "string", when using endpoint POST api/v2/salesorder, when payload included "string" in values. This has now been fixed.     Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default, starting 13th of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023 ... View more

Release date for 9.01.0 version has been planned as  14/06/2022 Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.   Release Notes Documentation Breaking change on Inventory endpoint for GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 9.01.0, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE2' not found"} Sales order replaces customer values for Invoice contact and Delivery address contact with "string" Earlier, sales orders replaced the customer's values for Invoice contact and Delivery address contact with "string", when using endpoint POST api/v2/salesorder, when payload included "string" in values. This has now been fixed.     Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default, starting 13th of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01   ... View more

Hello,  during the end of Q3/Q4 -  2022, Visma.net ERP will change the data centre provider for Visma.net Financials ERP. Customer's data will be transferred from AWS Europe (Stockholm) Region to Microsoft Azure West Europe (Netherlands). Data will also be stored in Microsoft Azure Sweden Central and Microsoft Azure Norway East. The move will be carried out in a planned service window. The application will be unavailable for users when data is transferred between data centres. The actual date for the relocation to Microsoft azure  will be announced soon.  What is the reason for Visma to change the data centre ? We believe Microsoft Azure is the best data centre for Visma.net ERP to support the growth of the application. Visma.net ERP is a Microsoft technology based application, and Microsoft Azure will give us possibilities to support stability and scalability in a good way.  Why are you receiving this information ?  In Terms Of Service for Visma.net, Visma undertakes to inform you of a change of Sub processor, this information is sent to you because you are registered as our primary contact for Visma.net Erp. We have a data processing agreement in place with Microsoft  to fulfil the obligations set out in the agreement and terms of service.   We recommend you to follow (This thread) & Visma.net Financials ERP communication channels (Partner Service from your country) where Visma.net ERP continuously provide relevant information related to this topic. If you want to know more about how Visma stores and processes customer data, you can read more at Visma Trust centre.   If you have any questions, feel free to contact us. ... View more

Release Notes Documentation New SupplierInvoice endpoint, enabling sending invoices to Approval There is a new SupplierInvoice endpoint: /controller/api/v1/supplierInvoice/{documentType}/{invoiceNumber}/action/sendtoapproval that enables sending documents to Visma.net Approval via API. Performance of Branch API improved  The API for Branch has been changed so that it is possible to select fewer data in the result set and by that get better performance. The following flags are implemented with True/False             expandAddress             expandContact             expandCurrency             expandVatZone             expandLedger             expandIndustryCode             expandDeliveryAddress             expandDeliveryContact             expandDefaultCountry             expandBankSettings (old) Their default value will be true until 13th of September 2022 and after that they will be turned to false. The "Order by" in this endpoint was by BranchCD by default, and since this is relaying on the code behind, it has been changed to a dropdown containing orderBy options (Id, Number, Name, OrganizationId, LastModifiedDateTime). Pagination has been removed from this endpoint, as it has been marked as obsolete for two years.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Breaking change on Inventory endpoint for GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 9.01.0, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} Jun 14, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023 ... View more

Release date for 9.00.0 version has been planned as  07/06/2022 Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.   Release Notes Documentation Performance of Branch API improved The API for Branch has been changed so that it is possible to select fewer data in the result set and by that get better performance. The following flags are implemented with True/False             expandAddress             expandContact             expandCurrency             expandVatZone             expandLedger             expandIndustryCode             expandDeliveryAddress             expandDeliveryContact             expandDefaultCountry             expandBankSettings (old) Their default value will be true until 13th of September 2022 and after that they will be turned to false. The "Order by" in this endpoint was by BranchCD by default, and since this is relaying on the code behind, it has been changed to a dropdown containing orderBy options (Id, Number, Name, OrganizationId, LastModifiedDateTime). Pagination has been removed from this endpoint, as it has been marked as obsolete for two years.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on Branch endpoint will be set to false by default starting 13 of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Breaking change on Inventory endpoint for GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 9.01.0, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} Jun 14, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023   ... View more

Status: https://status.visma.com/incidents/vx11gtw6kv61 We're working on this as a matter of priority to identify the root cause. We will provide further updates as more information is available.   Update: Regarding Incident with invalidated tokens 1/6-2022 ... View more

Release Notes Documentation GET inventory range and GET inventory specific endpoints now have support for returning LotSerialClass Added support for returning LotSerialClass in GET api/v1/inventory/{inventoryNumber} and GET api/v1/inventory endpoints Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. This change will be enforced starting the 30th of August 2022. The ones willing to switch to this new approach earlier can contact the partner service, support, or development team. The same applies for the ones wanting to keep the old approach after the 30th of August 2022. Feature toggle for allocations showing an extra row (/erp/api/v1/purchasereceipt endpoint) The issue with allocations that show an extra row has been fixed under a feature toggle. This occurs when a purchase receipt is created with POST Purchase receipt. The fix is only for the /erp/api/v1/purchasereceipt endpoint   Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 8.97, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} Jun 07, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023 ... View more

Release Notes Documentation Breaking change on Project endpoint for GET operation Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation - better error handling In the current solution, if you try to filter on an attribute on inventory which does not exits, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 8.97, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} May 31, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html     ... View more

Release Notes Documentation Error when creating purchase receipt from API when Default Receipt To location not allowing receipts Earlier, POST PurchaseReceipt with Default Receipt TO location gave an error message if the stock item had Default receipt to set to a location that does not allow receipts. This has now been fixed. Filtering on attributes not working via GET Supplier endpoint Filtering on attributes via the GET Supplier endpoint had stopped working after the latest improvement implemented to improve the performance. This has now been fixed. ... View more