Hi @Magnus Vadla, sorry for the late reply. The Developer Forum is no longer in use. Please send this question via Discord or through the Support channels. Thank you! ... Meer weergeven

I am also curious about this. It would be useful to be able to show the custom fields (customStr1 etc) in the header section of SO30100S.  ... Meer weergeven

I am also experiencing this on at least one customer today ... Meer weergeven

I don't do that. Everything is rolling as usual now. ... Meer weergeven

Hello, The request worked properly in Postman. I have no idea why the same request does not work from azure logic app. I made a work around through an azure function and that works.   Best regards, Magnus ... Meer weergeven

I have also noticed missing webhooks. Shipment events. ... Meer weergeven

Hello,   We ran into a problem here. The work around we implemented was to delete the original line, and then insert a new one, for example like this: PUT https://integration.visma.net/API/controller/api/v1/purchaseOrder/ { "lines": [ { "operation": "Insert", "project": { "value": "58" }, "projectTask": { "value": "100" }, "warehouse": { "value": "P" }, "account": { "value": "4010" }, "orderQty": { "value": 1 }, "inventory": { "value": "02" } } ] }  The problem is when the nonStock inventoryItem '02' has a default account which is not part of a project accounting group. In that case I get "Error: Inserting 'Purchase order line' record raised at least one error. Please review the errors.\r\nError: 'Project' cannot be empty". Was it always like this? I am pretty sure this worked a couple months ago, but I can't find anything related in the patch notes.   The reason the default account needs to not be project enabled is that otherwise the default project is null which is very frustrating for the user. ... Meer weergeven

Hello, the fix has been applied on [Release Notes] - Visma.Net API 9.67.0 - 17.10.2023 ... Meer weergeven

Hi, Prepare invoice (from sales order) is now available. Does this cover the need in this aswell?   Notice that there is a difference in Prepare invoice in sales order and Prepare invoice in shipments Sales order - Prepare invoice -> Invoice all confirmed shipments related to the sales order Shipment - Prepare invoice -> Invoice only order lines added to the shipment   Thank you.  ... Meer weergeven

For the breaking changes we will follow the same guideline as what is today in the Visma.net ERP API, i.e. latest 3 months before. In the closest roadmap we have not planned to introduce createShipment in V3. Could you elaborate a bit more for why it is highly needed in V3? Is it, for example, for the easier use of the API through the sales process or expectation of better performance in that endpoint etc? ... Meer weergeven

Hi, We recommend that you get in contact with your partnerService for your market as each market can have different procedures for registering/approving apps/integrations in the store/developerportal. As per my knowledge, all markets require that you complete the certification. Contacting Visma Partner Service / Visma.net ERP Support Thank you. ... Meer weergeven

I have a theory as to what might be happening here. Do you validate that the shipment exists before generating the report? That would explain why it works if there happens to exist a shipment with the same number as the receipt we are providing. ... Meer weergeven

Thanks Magnus, this will be reviewed.  ... Meer weergeven

Hi Magnus, it can be related to that hasResponseContent:False depending on the operation. e.g. ... Meer weergeven

Hello Yıldırım, I did another test now and it worked. I am pretty sure I got 403 before even when using the same user credentials for both the initial request and the background status request.  I will try to implement this into my application and post a new reply here if I run into problems. ... Meer weergeven

Will it help if I provide examples of this happening? NotificationID and maybe clientId? ... Meer weergeven

FUI, this is reported earlier and should be a confirmed issue SIGMA-44194 ... Meer weergeven

The last test I did was for companyId 1920520 at 12:26 today. Notification ID 67109a5b-a487-4d8c-83ee-9dcdba3f5b88 ... Meer weergeven