Hi, Could you please send us the JSON file for the request and a screen print of the Supplier from the UI? Please send this to you local support: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710  Kind regards Sandra Anté ... Skatīt vairāk

Hi, We would recommend that you create a post in the Ideas part of the forum if this is functionality that you wish to have available. We don't have a exact reason this whas not implemented in the first version, the API does not cover all functionality of the UI. ... Skatīt vairāk

Yes, it seems like it.   But then the question here might be why it seems like the input for financialPeriod seem to get scrambled in the backend for the endpoint? I would understand if it answered with "Post period value 12-2020 General ledger error: ..." But now it scrambles it an ends up being "20-1220" ... Skatīt vairāk

We'll have a look, mine does not seem to have a forced dark mode: ... Skatīt vairāk

Would it not make sense that the data that is returned at least looking the same?   A simple example (Endpoint for single SalesOrder): GET /salesorders/SO/000100 In this request, the Status field is an object that looks like this: "status": { "description": "string", "cancelled": true, "hold": true },   But in the request (Endpoint for list of salesOrders): GET /salesorders here the status field is a simple string: "status": "string",   I would have assumed that, at the very least, since it's both a GET that the data that is returned looks the same in both endpoints, even if they don't return the exact same amount of data for the whole salesorder   An option to "expand" on attributes, as is possible for the endpoint for a specific salesorder, seems like something that should exist for the list endpoint as well.         ... Skatīt vairāk

Hello,  this has been reported to the Sales Order Service API team so that it'll be reviewed to determine whether this is working as designed or a bug. ... Skatīt vairāk

The solution was provided above, and it was just an issue with how swagger prints out examples.   If it isn't too breaking of a change. Since subaccount can contain a varying amount of segments, wouldn't it make more sense that it was a list instead? Something like: [ { "id": "string", "value": "string" }, { "id": "string", "value": "string" } ]   ... Skatīt vairāk

Hi,  It depends on what UOMs are defined on the selected Inventory and what is used in the payload.  Unfortunately, there is no error handling in the current SalesOrder POST endpoint what could show you the number of the line which caused the error.  However, in the new Visma.net ERP Sales Order API Endpoint returns the error in detail so that we can see the faulty input based orderLines": [ ] in the response.   ... Skatīt vairāk

Hi, You'll need to encode the inventoryNumber in this case, have a look at this article and try it: Method for getting resources with reserved characters - B64URL Encoding   ... Skatīt vairāk

Thank you,   That is as I figured it was then.  ... Skatīt vairāk

Ok!  ... Skatīt vairāk

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

Thank you, we'll test it and send it on to the development team. ... Skatīt vairāk

This can be inquired via GET > https://integration.visma.net/API/controller/api/v1/customerSalesPrice  based on Sales Prices <ScreenId=AR202000>   "Sales Prices" can be created only with one of the following types,  Price Type Price Code Base Empty (Check ItemID) Customer Customer ID Customer price class Customer Price Class ID   In this way, If the "Price Type" is e.g. "Customer" then the Price Code will be "CustomerID" and it'll be populated together with ItemId & Price etc. in the GET Response.  If the "Price Type" is "Customer Price Class" then the Price Code will be "Customer price class ID" which is referring to <ScreenId=AR208000>  Then, if you'd like to get all the sales prices defined for the inventories, GET .../api/v1/customerSalesPrice without any filtering parameter will return the full list.   In addition to that, if you'd like to get the "Customers" only have "PriceClassID=xxx", unfortunately this is currently not exposed via the GET Customer endpoint. To be able to do that, "PriceClassID" should be added to the Customer endpoint as a filtering parameter.    If this is what you'd like to have, we recommend creating an improvement case in the "Ideas" section in the community. ... Skatīt vairāk

Hello,    EventTypes can be received via the GET >  https://integration.visma.net/API/resources/v1/event Example Request: https://integration.visma.net/API/resources/v1/notification?eventType=arinvoice_changed&dateFrom=2021-10-01 00:00:00&dateTo=2021-10-13 00:00:00   Although we provide the correct parameters, unfortunately, Notification Endpoint is underperforming at the moment. Currently, there are issues with the DB and the amount of data. This has been reported to the team.   An alternative might be getting the data itself  for the range "2021-09-01  to 2021-10-11" from the related endpoint. ... Skatīt vairāk

@Yıldırım  skrev: Hello,   @Snuffsis wrote: We are trying to get all inventory where there has been changes to the quantity in the inventory items warehouses. Can't find any endpoint where it's possible to filter and get only items where the stock has been changed.Is it possible at all, and if not, is it something that might be requested? currently, we don't have a webhook implemented for tracking the "Stock Changes" therefore it's not possible to trigger a specific GET for only fetching the inventories what have been changed.  This improvement has been registered in our backlog.     New implementation requests can be posted and followed at "Ideas" section in the community. Event: Inventory_changed  I see. that is good to hear.     @Snuffsis wrote: We don't really want to get the entire inventory stock for certain customers, as some can have thousands and thousands of items. Which would take a long time. In this case, if you'd like to search through all Inventories based on activity instead of a specific one (Inventory Summary) then the most relevant endpoint would be "Inventory" for the required operation.    Endpoint: GET /controller/api/v1/inventory e.g: GET https://integration.visma.net/API/co.../v1/inventory? availabilityLastModifiedDateTime=2021-05-07&   (YYYY-MM-DD HH:MM) availabilityLastModifiedDateTimeCondition=> Supported comparative operators > < <= >= This query parameter should return the inventory items which have had Inventory issue & Inventory Receipt activity based on the released documents in the UI. The updated field should be [warehouseDetails] "lastModifiedDateTime in the Inventory Endpoint GET response "warehouseDetails": [ { "isDefault": true, "warehouse": "1", "quantityOnHand": 174, "available": -290, "availableForShipment": -4, "lastModifiedDateTime": "2019-05-08T10:17:33.92" } ] Oh this one i completely glossed over and it it exactly what we want. Thank you!  ... Skatīt vairāk

Was that financials ERP company or user recently created and roles had been modified ?  ... Skatīt vairāk