Release date for 8.95.0 version has been planned as  05/03/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 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. "Attributes" filtering doesn't work 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.   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 Jun 01, 2023 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. May 17, 2022 ... View more

Release Notes Documentation ProjectTransaction Endpoint(PUT/POST) with several lines sets the last occurring financialPeriod on all lines In previous versions, when using the Project transaction endpoint to create or update a project transaction with multiple transaction lines that have different financial periods, the project transaction was not taking into account the specified financial periods. This has now been fixed. Account and subaccount combination in restriction groups not working via API Customer creditNote V2 endpoint (POST) Earlier, it was not possible to create a document via the API Customer Credit note V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP. This has now been fixed. Account and subaccount combination in restriction groups not working via API Customer Invoice V2 endpoint (POST) Earlier, it was not possible to create a document via the API Customer Invoice V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation - better errorhandling 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, we will start returning 400 Bad Request for this operation, and give an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} May 17, 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 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. May 01, 2022   ... View more

Release date for 8.92.0 version has been planned as 12/04/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 ProjectTransaction Endpoint(PUT/POST) with several lines sets the last occurring financialPeriod on all lines In previous versions, when using the Project transaction endpoint to create or update a project transaction with multiple transaction lines that have different financial periods, the project transaction was not taking into account the specified financial periods. This has now been fixed. Account and subaccount combination in restriction groups not working via API Customer Invoice V2 endpoint (POST) Earlier, it was not possible to create a document via the API Customer Invoice V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP. This has now been fixed. Account and subaccount combination in restriction groups not working via API Customer creditNote V2 endpoint (POST) Earlier, it was not possible to create a document via the API Customer Credit note V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP. This has now been fixed.     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, we will start returning 400 Bad Request for this operation, and give an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"} May 17, 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 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. May 01, 2022 ... View more

Release Notes Documentation Filter on attributes which did not exist, gave an error message. (For details of the issue) After the release of 8.91, if you tried to filter on attributes on inventory which did not exist, you got an error message. This was a breaking change. We have now removed the error message. The functionality will now work as before and return 200 OK, with no data. the performance improvement on inventory endpoint, has been enabled, again, which was initially introduced with 8.91. Due dates for breaking change Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation - better errorhandling 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, we will start returning 400 Bad Request for this operation, and give an error message that the value you are trying to filter on does not exist - Example: {"message":"Attribute 'ACTIVE' not found"} May 17, 2022 ... View more

  Release Notes Documentation The performance of the GET Inventory endpoint improved - For details The performance of the GET Inventory endpoint has been improved, leading to quicker response time. This has been in pilot testing for several weeks now and will be enabled for all customers with version 8.91.0 of Visma.net ERP. Breaking change on Inventory endpoint for GET operation - For details Paging has been enforced on Inventory endpoint. The default page size is set to 5000. If you do not specify a page size, you will get 5000 records, and if you try to specify a higher number, you will only get 5000 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 5000 records only. With this improvement, pagesize can be increased to  5000 on this endpoint so that clients can fetch more data in a single request. Error when changing project ID in Project management Earlier, when changing the project ID in Visma.net Project Management service, the integration sync with Visma.net ERP was stopping, and an error was displayed. This has now been fixed. New handling of subaccount segments in Post JournalTransactionsV2 In the Post JournalTransactionsV2 it is now possible to provide subsets of the subaccount segments. The omitted segments will be assigned the default values as specified in the General ledger preferences (GL102000) window. For transaction lines including a cash account, the default subaccount as specified in the Cash accounts (CA202000) will be applied. PUT Location Endpoint returns HTTP "400" Bad request instead of "404" Not found when the asset is not found PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found.   Due dates for breaking changes Release Notes Documentation Due 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 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. May 01, 2022 ... View more