About Kanyar Mahmoud

Kanyar Mahmoud · ‎24-04-2024

Hi We tested both of these endpoints: https://salesorder.visma.net/api/v3/SalesOrders https://integration.visma.net/API/controller/api/v2/salesorder

Kanyar Mahmoud · ‎23-04-2024

Hello We have a customer that uses the credit check functionality in Visma.net ERP. If the customer has an invoice that is overdue x amount of days, it should not be possible to process the order (make a shipment etc.). In the GUI this works fine. You can create the order, but as soon as the order is not on hold and you click on save the credit hold box is activated, and you cannot further process the order. However when we create an order with this customer through the salesorder API, the checkbox for credit hold does not activate. You are also able to further process the order which should not be possible. Is this a known bug? And do you know when it can be fixed? Our customer has a lot of customers and orders, and checking every order that comes in through the API takes a lot of time.

Kanyar Mahmoud · ‎16-02-2024

I see, my bad. I mixed up the backslash with the / character. You are correct, it is not possible to use backslash in GUI either. Thank you for the help 🙂

Kanyar Mahmoud · ‎16-02-2024

Hi Suzdar As far as i can see this is possible in the UI: Also these subaccounts are created in another system, and is being transferred over to Visma.net through an integration. And the users there use / in the descriptions, but it should be possible to follow the JSON standards of escaping the / and get it in the description. However it is not working in this case. Can you confirm it's a bug?

Kanyar Mahmoud · ‎15-02-2024

Hi Suzdar! I'm trying to create a subaccount.

Kanyar Mahmoud · ‎15-02-2024

Hello The problem was noticed while accessing the following URL: https://integration.visma.net/API/controller/api/v1/dimension/SUBACCOUNT/3 The API returned the following error message: { "message": "VismaId: 49dda245-6508-47ea-9936-b58f6bb1e86f. Error: An error in processing of field Description value taaaa \\ daaaaaaa This field can only contain plain text." } As per the error message, it seems that the description field is rejecting certain characters, specifically backslashes, even though they are properly escaped. This behavior is unexpected and prevents the correct processing of data. When we remove the // from the description it goes through without a problem. Here is the JSON: { "dimensionId": "SUBACCOUNT", "segmentId": 3, "description": { "value": "This is to test subsccount update" }, "segmentvalues": [ { "operation": "Insert", "value": "10640", "description": { "value": "testing \\ description" }, "active": { "value": true } } ] }

Kanyar Mahmoud · ‎04-07-2023

Do you have an estimate to when this could get implemented?

Kanyar Mahmoud · ‎03-07-2023

Hello We are trying to create a sales order through the new salesorder API, but we are having problems with marking the order lines as drop shipment. We cannot find any documentation on it in the swagger documentation. In the old swagger for SalesOrderV2 it was documented how to do this: But when we try something similar with the new SalesOrder API it doesn't work. We also tried to get a salesorder from Visma.net ERP where the line was marked for drop shipment, but we could not find any related fields we could use in the post. Can we get an example of how the JSON is supposed to look like if we want to mark an orderline for drop shipment? Or at least tell us which fields to use. Regards Kanyar

Kanyar Mahmoud · ‎24-03-2023

Hello, Sorry for the late reply, i never got a notification that you replied. Yes your assumption is correct. And i don't think it's related to consecutive requests because it is the first JT we try to create that fails. The next one gets created instantly (after 6 ms) right after without failing. So we have no delay between the creation of the JT's, but it is the first one that fails so consecutive requests shouldn't be the problem.

Kanyar Mahmoud · ‎02-03-2023

Hello, We have an integration made for our customer so that they can import the contents of an excel file as a journal transaction in Visma.net. Sometimes the customer gets this error message from the API: {"message":"VismaId: f203b1a2-120c-4d9c-bb33-af9f53d729c3. Error creating journal transaction. Data received not recognized as JournalTransactionUpdateDto\r\nValue cannot be null.\r\nParameter name: JournalTransaction"} The weird part about this is that when they try again with the exact same file and no changes it goes through without the error. So apparently this has happened quite a few times and solves itself by retrying. What is the cause of this error, is it a bug in the API? Regards Kanyar

Kanyar Mahmoud · ‎02-01-2023

Hello, When trying to add a JournalTransactionLine, the VatCodeId from the account is being used. We want to avoid this, so we tried: "vatCodeId": { "value": null }, This works, but we still get VatCodeId from the account. Also tried: "vatCodeId": { "value": ‘’ }, "vatCodeId": { "value": ‘ ‘ }, But these are rejected with an error message. The purpose is getting no vat code on the journal transaction lines that has no vat.

Kanyar Mahmoud · ‎26-11-2020

There are settings in SO101000 that decide if issues automatically gets updated or if you manually have to update them. As you can see in the attachment this is set to automatically. An issue is created at different times based on the settings you use. In this case the issue is created when an invoice goes from status balanced to open. These invoices are related to a sales order or shipment. When the invoice status changes to open, the issue is created and automatically gets released based on the settings in SO101000. The issue essentialy releases the stock items from the inventory. So the problem here is when the API is used to do this process, the issues do not automatically release. When done from the UI manually by a user it isn't a problem. However this was a known problem 2 patches ago, but has been fixed. Hopefully you understand the problem a bit better 🙂

Kanyar Mahmoud · ‎26-11-2020

Hello! We have a customer that uses an integration between their webshop and Visma.net ERP. As you can see in the attachment, the issues (IN3020PL) that are created by the integration user (created through the API) does not automatically get released, like the ones created manually by the user Anne. This was a known issue last month that got fixed, but it seems like it still occurs when using the API. This is a problem because they have to manually release these or their inventory will not be accurate. Regards Kanyar

Kanyar Mahmoud · ‎17-11-2020

Hi! I have a couple of questions regarding webhooks. Is it possible to use webhooks to get notified on changes made to a sales order and invoice? Which changes to a sales order and invoice will trigger the webhook? Is it the checkbox on the customer that decides if webhooks on a sales order/invoice is active? Thanks in advance 🙂 Kanyar

Re: Credit hold on sales order not working

Credit hold on sales order not working

Re: 500 internal server error - backslash in descr...

Re: 500 internal server error - backslash in descr...

Re: 500 internal server error - backslash in descr...

500 internal server error - backslash in descripti...

Re: Drop shipment on new SalesOrder

Drop shipment on new SalesOrder

Re: Error creating journal transaction

Error creating journal transaction

JournalTransactionLine without VatCode

Re: Issues not automatically released through API

Issues not automatically released through API

Questions regarding webhooks and sales order/invoi...

Useful pages

About Visma

Contact us

Follow us