About SitterIT

SitterIT · ‎25-08-2023

I have that. Creating new token, works well to create new invoice, read customers, suppliers and more. I can also create the payment, but the action release will not work Still get error 403 - Forbidden message=Scope requirement not met

SitterIT · ‎25-08-2023

When doing a POST https://integration.visma.net/API/controller/api/v1/customerpayment/400013/action/release with body like : { "type": { "Value": "Payment" } } I get error 403 - Forbidden If I just change to the old static token the same request works fine. All scopes are allowed in the app.

SitterIT · ‎01-06-2023

{ "type": "AI", "date": "2023-06-01T00:00:00+02:00", "requestOn": "2023-06-02T00:00:00+02:00", "description": "Gävle sjukhus, Förråd Arbetsterapi", "customer": { "id": "L1460", "order": "LGX001054325", "refNo": "Öhneskog, Pia" }, "print": {}, "shipping": {}, "orderLines": [ { "inventoryId": "8126", "unitOfMeasure": "STYCK", "quantity": 1.0, "discountPercent": 0.0, "discountAmount": 0.0, "hasManualDiscount": false, "operation": "Issue" }, { "inventoryId": "42003", "unitOfMeasure": "KRT", "quantity": 1.0, "discountPercent": 0.0, "discountAmount": 0.0, "hasManualDiscount": false, "operation": "Issue" } ], "salesPersonID": "P401" }

SitterIT · ‎01-06-2023

It's urgent. All orders fail on import if one sets this value. Please don't shut down the old endpoint yet. Extend the grace period due to these types of errors. We had rollback to old version of the integration due to this.

SitterIT · ‎01-06-2023

When trying to send salespersonid creating an order in V3, I recieve error 400 - bad request. This Id exists in Vn and works great using the old endpoint. (https://integration.visma.net/API-index/) I've tried with some of the other salespersons, but getting the same error.

SitterIT · ‎25-04-2023

Seems to be related to the test company . id: 2840609

SitterIT · ‎25-04-2023

just tried it again and get the same . Trying to create an order.

SitterIT · ‎13-04-2023

The performance is inconsistent and very slow. Almost 30 sec to create trying the exact same post moments later getting a 503 - service unavaliable

SitterIT · ‎13-04-2023

So the SalesOrder endpoint in v2 will still have some of its functionality after June 1st? And it's only the get/put/post of salesorder that's affected? This meaning that we have to use both salesorder v2 and salesorder v3 in combination?

SitterIT · ‎12-04-2023

What is the replacement for /controller/api/v1/salesorder/orderType/{orderType}/{orderNumber}/attachment in salesorder.visma.net api ?

SitterIT · ‎21-03-2023

When adding new orderlines to a existing salesorder, it seems to require the ETag header also. In the swagger documentation, this is as I can see only this documented on the PATCH /api/v3/SalesOrders/{type}/{orderId}/lines and PATCH /api/v3/SalesOrders/{type}/{orderId} Is this as it should be or should it not be required on POST /api/v3/SalesOrders/{type}/{orderId}/lines (adding new lines to the salesorder)

SitterIT · ‎21-02-2023

Now it works as it should. Thanks.

SitterIT · ‎08-02-2023

Hi, I'm using client 2106142 with the request posted earlier

SitterIT · ‎02-02-2023

Hi, this is still not fixed. I just tried with this: { "type": "SO" , "customer": { "id": "10001" }, "orderLines": [ { "inventoryId": "105","quantity": 1,"unitPrice": 100} ] } However, If one includes the subaccount, then it works: { "type": "SO", "customer": { "id": "10001" }, "orderLines": [ {"inventoryId": "105","quantity": 1,"unitPrice": 100,"subaccount":{ "1": "00", "2": "000", "3": "0000"}} ] } So we still need to provide subaccount when creating the salesorder.

SitterIT · ‎19-01-2023

Hi, do you know when this issue is fixed?

SitterIT · ‎20-12-2022

Great! So that means that this will work in SalesOrder API just as it works in the integration.visma.net . And that we do not need to provide subaccount in the post-command.

SitterIT · ‎09-12-2022

Adding the visma.net erp scope solved it.

SitterIT · ‎09-12-2022

I see that visma.net erp is released. I'll try this.

SitterIT · ‎09-12-2022

How can you use the same authentication on both api's ? SalesOrder requires an token generated from https://connect.visma.com/connect/token and access provided through the dev portal. And the integration.visma.net uses ipp-company-id, ipp-application-type as headers, and also the "old" accesstoken. This means that you have to have 2 different settings as far as I can see. But please share idées if you have solved this.

SitterIT · ‎09-12-2022

In the new SalesOrder api, I face the same issue as in the case described here , having to provide the correct subaccount array on orderlines. If we look at the "old" integration.visma.net api, there is no need to include subaccount on orderlines. This should still be optional in the new api, and when omited, the orderline should inherrit the the default subaccont set on that inventroy in Visma.net. Just like it works today. From what I can see today, one have to either : - specify the subaccount in a settings-file or such. This will fail as soon as one changes the subaccount dimentions in Visma.net - do a GET on inventory to get the subaccount of an inventory to set on orderlines - do a GET using the integration.visma.net api to get subaccount from there. It's not always one wish to set subaccount, and thats why I still want it to be optional.

SitterIT · ‎08-12-2022

Ok, hope this is high on the list to improve. Having to use both the integration.visma.net api and the new salesorder-api in one solution to achieve the same thing that we get from integration.visma.net api today is not really a good solution. And hope that the new salesorder-api will be extended with all the other endpoints that exists in the integration-api so we dont have to handle 2 different api's with different models and authentication methods. But have to say that the speed on the new salesorder-api is impressive. Thats very good.

SitterIT · ‎29-11-2022

I'm starting my first app here now. When using GET /inventory it only returns stock-items. I can't see how to get non-stock items. How do I get all inventory items, both stock and non-stock items at the same time. Also, I can't see the attribute in the model that states whether it's a stock or non-stock item

SitterIT · ‎26-01-2022

It could also be an idé to extend the InventorySummary endpoint to return a list of inventory with detailed info. And filter possibility just like on the Inventory endpoint.

SitterIT · ‎18-01-2022

On ScreenId IN202500 and WarehouseDetails one can see all the warehouses and locations for the article. If one can expose IssueFrom and ReceiptTo to the warehouseDetails section it would be great.

SitterIT · ‎01-07-2021

On CustomerOrder we have taxDetails[] avaliable but this do not exist on CashSales. Please implement this on the CashSale-endpoint.

SitterIT · ‎01-07-2021

The property externalReference is missing in the endpoint cashsale. It's avaliable on CustomerInvoice. Needs to be avaliable also on the cashsales endpoint.

SitterIT · ‎16-06-2021

Would be greate if one could get/set warehouse on customer Sometimes it's empty on the customer, and if one do not set the warehouse property on SalesOrder, it will fail. So to be able to do internal controlls if warehouse is set on customer before trying to add an salesorder would eliminate this issuse. Screenid AR303000 - Warehouse prop under Deliveryinfo

SitterIT · ‎16-06-2021

Would be greate if one could get/set warehouse on customer Sometimes it's empty on the customer, and if one do not set the warehouse property on SalesOrder, it will fail. So to be able to do internal controlls if warehouse is set on customer before trying to add an salesorder would eliminate this issuse. Screenid AR303000 - Warehouse prop under Deliveryinfo

SitterIT · ‎21-05-2021

One can retrieve a customerpricelist through customerSalesPrice endpoint. What's the equivalent for supplier prices ? I can't find the endpoint / method for creating/updating customerpricelists ?

SitterIT · ‎22-04-2021

In the GUI one can create an inventoryitem with spaces in the inventorynumber. And it's also possible to get them through the API. However when trying to create a new inventoryitem through the API, it fails with an error 400 - "Error creating inventory. New inventory must have a number that can not contain spaces" How can one create an inventroyitem with spaces in the inventroynumber through the API? Sending in %20 instead of a space does not help.

Svar: Cant release customer payment with new token

Cant release customer payment with new token

Svar: Error setting SalesPersonId when creating ne...

Svar: Error setting SalesPersonId when creating ne...

Error setting SalesPersonId when creating new Sale...

Svar: Performance salesorder v3

Svar: Performance salesorder v3

Performance salesorder v3

Svar: Salesorder V3 attachment

Salesorder V3 attachment

Adding new lines to exsisting order V3

Re: SalesOrder api subaccount issue mandatory

Re: SalesOrder api subaccount issue mandatory

Svar: SalesOrder api subaccount issue mandatory

Re: SalesOrder api subaccount issue mandatory

Svar: SalesOrder api subaccount issue mandatory

Re: Sales Order Api Inventory

Re: Sales Order Api Inventory

Re: Sales Order Api Inventory

SalesOrder api subaccount issue mandatory

Re: Sales Order Api Inventory

Sales Order Api Inventory

Svar: Expose Warehouse details on inventory

Expose Warehouse details on inventory

taxDetails on CashSale

Make externalReference on cashsale avaliable

Get / Set Warehouse on CustomerDTO

Get / Set Warehouse on CustomerDTO

Create supplier and customer pricelists

Create Inventory with space in number

Useful pages

About Visma

Contact us

Follow us