About AllanEgebjerg

Suzdar Ibrahim · ‎10-07-2024

Hi Allan! I see that there has been some small changes on the two latest releases, but I'm not sure if it is the reason why your customers are suddenly experiencing more issues. I've checked with our developer team and only that comes in mind to have smaller updates in the PUT request. Unfortunately there is no 100% guarantee that this will work. You could also try to do this manually in the UI until the next release. - Suzdar

AllanEgebjerg · ‎13-05-2024

@Magnus Johnsen Does this apply for the salesorder /api/v1/salesorder andpoint as well?

David Tandberg-Johansen · ‎06-10-2023

Thank you

AllanEgebjerg · ‎16-08-2023

Working with integration from WMS, and we are trying to report the correct lot/batch/usebydate that has been picked in the warehouse, back to Visma orderline. When creating new stock, the stock is correctly created with the serial/usebydate noted on the orderline. But when we report an usage back to an orderline and sets serial/usebydate/finishNow, the information is stored correctly in the transaction, but the decrease in quantity is not done on the stock with similar serial/usebydate. Looks like Visma is using FIFO on the stocks in this regard. How do we get Visma to select the correct lot (serial/usebydate)?

omelhus · ‎21-07-2023

Would be cool if batch operations were executed in parallel, since they won’t share any data between them. And if you need something executed sequentially you could use the “inline batch”.

Marius Bancila · ‎20-07-2023

We have added support for batching requests. See documentation: https://docs.business.visma.net/docs/features/batches

Marius Bancila · ‎07-07-2023

I don't think you can close topics. You can mark them as resolved though. But I didn't quite understand: did you realize what you were doing wrong? Or what you misunderstood the way the API is supposed to work?

Yıldırım · ‎24-11-2022

Hello Allan, we've completed the investigation and this case has now been conveyed to our infrastructure team to check what can be done to improve the performance in Shipment Endpoint. We'll keep you updated.

Yıldırım · ‎18-11-2022

Hello, the request is still in the backlog, and currently it has not been prioritized. We will provide further updates as more information is available.

AllanEgebjerg · ‎20-01-2022

Working with TR orders in the API, we are looking for a way to perform the "Update IN" on a shipment, that is possible from the shipment window (W(10002))) or alternatively from the from the Process Shipments window: To make TR orderflow work from external system (WMS) we would need to be able to UPDATE IN on a TR shipment from the webapi.

Magnus Johnsen · ‎17-01-2022

Hi, This action is currently not exposed. If this action is something you have a need for, we recommend that you create a post in the "Ideas" part of the forum. This allows other users to vote for your suggestion, which in turn influences the assessment and implementation process of the development team. Please describe what you would like to have exposed and your business need as detailed as possible. Thank you.

Stefan Hult · ‎29-11-2021

Hi Allan The only solution we found was to wait for the shipping, there you can find both the IN och UT warehouses. /Stefan

Yıldırım · ‎29-06-2021

Hello, those operations are not exposed via the currently available API. If you'd like to raise an improvement request for the development, please register this at the ideas section of the community by specifying the UI details / Business case. Thank you.

AllanEgebjerg · ‎04-02-2021

Det kaldes "lotSerialNumber" i "allocations", vs"lotSerialNbr" i "shipmentDetailLines"

AllanEgebjerg · ‎04-02-2021

Ahh, now I see the error. It is called "lotSerialNbr" in "shipmentDetailLines", but "lotSerialNumber" in "allocations" Thanks a lot 🙂

Re: KitAssembly Update - Error: 'tstamp' cannot be...

Re: Inventory Get SortOrder

Re: Filter documentType not when also filtering on...

Using correct stock when working with serial(lot/b...

Re: API Updates

Sv: Updating orderlines on order in one api call

Re: OrderLine_update fails to update line

Re: Slow request to confirmShipment

Sv: AddressLine3 on Shipment endpoint

Expose endpoint to UPDATE IN

Re: UPDATE IN

Re: Missing warehouse on Transfer order

Re: Complete or cancel purchase order from api

Sv: Kan ikke oppdatere serienummeret på allokering...

Sv: Cannot update lotSerialNbr on shipment allocat...

Useful pages

About Visma

Contact us

Follow us