Visma.net Financials API updates for version 8.38.0 (February 2021) ... View more

Hello,  to our knowledge there have not been any changes or modifications in design or structure of the endpoint. If there is any value (alternateType) , by default, CrossReference is returned otherwise you can also try to set  parameter "expandCrossReference=true" https://integration.visma.net/API/controller/api/v1/inventory?expandCrossReference=true    I'd also recommend double-checking that specific inventory in the UI which you expect to see a value with via the GET. ... View more

Hello Suzdar,  GET:SalesOrderDto data model is for reading the data from Sales Order Endpoint that is corresponding with Sales Order Module (ScreenId=SO301000) in the Financials ERP UI. For POST operations and its DTO, you should look at POST : saleOrderUpdateDto  We'd recommend you first checking the Sales Order document in the Financials ERP UI to determine what field you'd like to interact via the API then you can build your API payload based on transaction need. You should only include the fields in the JSON that you'd like to set a value otherwise please exclude those fields from your payload. Here is an example POST Sales Order JSON:    { "orderType": { "value": "SO" }, "hold": { "value": false }, "date": { "value": "2020-02-17" }, "customerRefNo": { "value": "AAA#6111" }, "customer": { "value": "10023" }, "currency": { "value": "NOK" }, "lines": [ { "operation": "Insert", "lineNbr": { "value": 1 }, "inventoryId": { "value": "5" }, "warehouse": { "value": "1" }, "uom": { "value": "STK" }, "quantity": { "value": 1 }, "unitPrice": { "value": 111.2 }, "lineDescription": { "value": "TEST SO" } } ] }   ... View more

The issue regarding filtering with Attributes while using Pagination,  The problem is the same as for inventory and supplier endpoint. (Attributes & Pagination) The reason for the error is that the endpoints are implemented with "join" in memory - fetched first all attributes based on the filter and then skipped all inventories, customers and supplier which are not connected to the selected attributes. This operation is done by first getting all inventories, customer or supplier based on pagination information and then joined in memory (instead of joining attributes to the specific tables)   The solution for the problem is to create new endpoints (v2) for inventory , customer and supplier where SQL is used to join attributes. So we're still waiting for the roadmap to be finalized before announcing when this can be fixed.  @Trygve Storrønningen1 wrote: Honestly I personally feel more like a child trying to get the attention of grown up Visma to tell how painful this is for our integrations, customers and business, but after 5 months still not enough attention and priority to be solved. I believe everyone is aware of the problem, yours and other ISVs feedback have been obviously heard, conveyed and recognized. This is, as I mentioned above, a matter of roadmap planning.  If you would like to emphasize this problem once again , you can contact Partner Service from your market (Product Managers) or share your opinion in the #ext-visma-partner-info that you're a guest-member. Thanks. ... View more

Hello,    Query refactoring for GET:Customer - Pagination has been revoked (11:50CET). That was the only change has been applied to the Customer Endpoint with 8.36. Errors started right after the deployment around 17:30 CET , so this should be the root cause of the error you've been receiving while trying to POST Customer. Can you please monitor the situation of your integration and inform us accordingly ?  ... View more

Hello,  Query refactoring for GET:Customer - Pagination has been revoked. Now, TotalCount is included in the Payload again. Performance Improvement will be reviewed once the metaData issue resolved.   Please inform us if you still don't receive the metadata while using the pagination. ... View more