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 ... Vis mer

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     ... Vis mer

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. ... Vis mer

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 ... Vis mer

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   ... Vis mer

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 ... Vis mer

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 ... Vis mer

  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 ... Vis mer

Release date for 8.91.0 version has been planned as 05/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 The performance of the GET Inventory endpoint improved 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 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, ISV's are encouraged to increase their pagesize on this endpoint so that they can fetch more data in one go. 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. Error when changing project ID in Project management Earlier, when changing the project ID in the Project management workspace, the integration sync was stopping and an error was displayed. This has now been fixed. 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. Postponed to: May 01, 2022   ... Vis mer

Release date for 8.89.0 version has been planned as 22/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 Improved performance on GET ALL Supplier endpoint The performance of the GET ALL Supplier endpoint has been improved. The pilot testing phase is now completed, the improvement which has been deployed under a feature toggle is now enabled for all customers in production. Change in MaxPageSize for the GET Inventory endpoint MaxPageSize for GET Inventory will be set to 5000 from 1 April 2022. Validate syntax of provided webhook address in API request with erp-api-background Earlier, the webhook address provided in the erp-api-background request header has not been validated, therefore, it was causing an exception if a bad URL was provided. This has now been fixed. Possible to insert invalid value in "type" when using PUT Inventory endpoint and make the item invalid Earlier, it was possible to insert an invalid value in "type" when using the PUT Inventory endpoint. This has now been fixed. Account and subaccount combination in restriction groups not working via API SupplierInvoice endpoint (POST) Earlier, creating a document via the API SupplierInvoice endpoint (POST) using an account and subaccount combination existing in a restriction group configured within Visma.net ERP was not possible. This has now been fixed. 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. Allow purchaseReceipt action addPurchaseOrder to add purchase orders of type drop-ship Earlier, you were not able to add drop-shipments to Poreceipt through POST/controller/api/v1/PurchaseReceipt/{receiptNumber}/action/addpurchaseorder. This has now been fixed by adding orderType to the JSON-file: {   "purchaseOrders": [     {       "orderNbr": "string",       "orderType": "RegularOrder"     }   ] } OrderType needed to be changed to DropShip to get drop-shipments to work.   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 Location endpoint for PUT operation PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found. Apr 05, 2022 Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be 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. Apr 01, 2022 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. Apr 01, 2022   ... Vis mer

Release Notes Documentation New Background API functionality Now all API endpoints available at Visma.net ERP API documentation can be invoked in asynchronous mode by using the new “Background API” functionality. Documentation can be found here. Improved performance on GET ALL CustomerPayment endpoint The performance of the CustomerPayment endpoint has been improved.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Location endpoint for PUT operation PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found. Apr 05, 2022 Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be 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. Apr 01, 2022 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. Apr 01, 2022 ... Vis mer

We’ve implemented a new feature that API Endpoints available at Visma.net ERP API Documentation, can be invoked in an asynchronous mode by using the new “Background API” functionality. (Version: 8.88.0)  This can be achieved by adding an extra request header “erp-api-background: “WebhookURL”  to your request.   If this additional “request header” is provided in your request, our servers  will "intercept" the API request before it reaches the Endpoint. The request will be persisted in our backend. All our application web servers will regularly pull queued requests and process them in the background. This processing is not taking place in a web context, and therefore it is not prone to web exceptions like timeouts etc.    In this way, with this new feature, potentially long-running operations can be performed more effectively.    Once the request has been processed, the API Client will be notified with the webhook notification if “erp-api-background” request header had been provided with “webhookURL” value in your request.   This webhook notification will contain information about, “stateLocation” of the operation(status of the background operation) and “ContentLocation”  that where the response can be picked up, in other word, where the API Client can GET the result of the request that has recently been made.(if it has any content aka ResponseBody)   If the “erp-api-background” request header value set as “none” Webhook notification will not be invoked.  In any case, every queued API request will be assigned an ID that will be present in the immediate “202-Accepted” response to the client.  This response also contains a "stateLocation" address that the client can call at any time to check what is the status of the background operation.  "contentLocation" address that points to the readily formatted and stored response body of the operation if it has any content to be returned.   If the endpoint today is asynchronous,  meaning that if it is immediately returning a “202-Accepted” HTTP response and starts the actual job in the background, such as “Action” based operations. (Endpoint URL: …/action/…),     Currently,  the new "Background API" system is also unable to receive the state of the document when the action based request invoked. Therefore, we’re unable to determine whether the “action” based process succeeded or the state of the document changed without making an additional GET request to see the actual status of the document. However, this topic is already in our development plan. (Endpoint logic should be "synchronous" so that, waiting for the actual job to be done, to inform the client accordingly.)   Example request: "Request Headers erp-api-background : yourWebhookURL" Key  Value ipp-application-type Visma.net Financials ipp-company-id "ERP CompanyID" Content-Type application/json Authorization "yourToken" erp-api-background "yourWebhookURL"   GET: "Customer  Invoice" Request URL: /api/v1/customerinvoice?pageNumber=1&pageSize=100 HTTP Response: “202-Accepted” Response Body: Received Webhook Notification: GET: "stateLocation" Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body: GET: "contentLocation" Request URL: api/v1/background/{id}/content HTTP Response: ” 200-OK” Response Body: Contains the “GET - CustomerInvoice” data. --------------------------------------------------------------------------------------------------------------------------------------- POST: “Customer Invoice” Request URL: “/api/v2/customerinvoice” HTTP Response: “202-Accepted” Response Body: Contains request “ID” and “stateLocation” Received Webhook Notification: GET: "stateLocation" Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body:  --------------------------------------------------------------------------------------------------------------------------------------- PUT: "Customer Invoice" Request URL: /api/v1/customerinvoice/{invoiceNumber} HTTP Response: “202-Accepted” Response Body: Contains request “ID” and “stateLocation” Received Webhook Notification: GET: “stateLocation” Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body: --------------------------------------------------------------------------------------------------------------------------------------- "Request Headers erp-api-background : None" Key Value ipp-application-type Visma.net Financials ipp-company-id "ERP CompanyID" Content-Type application/json Authorization "yourToken" erp-api-background "None"     ℹ️ Webhook notification will not be invoked, State & Content Location logic will be the same as request examples shared above.  ---------------------------------------------------------------------------------------------------------------------------------------   Please feel free to contact us (Financials ERP API Support) if you need any further information. ... Vis mer

Release date for 8.88.0 version has been planned as 15/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 New “Background API” functionality Now all API endpoints available at Visma.net ERP API documentation can be invoked in asynchronous mode by using the new “Background API” functionality. Documentation can be found here. Improved performance on GET ALL CustomerPayment endpoint The performance of the CustomerPayment endpoint has been improved.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Location endpoint for PUT operation PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found. Apr 05, 2022 Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be 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. Apr 01, 2022 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. Apr 01, 2022 ... Vis mer