Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
AllanEgebjerg
29
Posts
4
Kudos
0
Solutions
10-07-2024
11:33
Did you just do something within the last few days. We have multiple customers experiencing this issue right now. It is quite critical.
... View more
10-07-2024
11:30
So what does the customer do untill then. Right now it is not possible to do goods reception through the api 😞
Do you know what the issue is and is there is a workaround?
... View more
10-07-2024
11:18
Hi Suzdar.
Is there any update on this issue? We are also getting the same error message when calling PUT https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/XXXXXX Do you know the reason for the error and when it will be resolved?
... View more
13-05-2024
13:46
@Magnus Johnsen Does this apply for the salesorder /api/v1/salesorder andpoint as well?
... View more
12-09-2023
12:01
We just deployed an integration towards a live customer. Everything is working on the test customer, but when querying on the live customer, and filtering on changedDateTime after 1/8 when it looks like that the other filters are ignored: query ImportPurchaseOrder($cid: Int, $recordsPerPage: Int, $afterCursorValue: String, $TimeForLastExecution: DateTime) {
useCompany(no: $cid) {
orderDocument(
first: $recordsPerPage,
after: $afterCursorValue,
filter: {_and: [{documentType: {_eq: 7}},{transactionType: {_eq: 6}},{changedDateTime: {_gt: $TimeForLastExecution}}]}
) {
totalCount
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
items {
orderDocumentNo
documentType
transactionType
changedDateTime
documentDateAsDate
orderNo
}
}
}
} variables: {
"cid": 44737...,
"recordsPerPage": 20,
"TimeForLastExecution": "2023-08-01T13:15:06Z",
"afterCursorValue": null
} Whenever I set changedDateTime filter to a date after 1/8 when all documentTypes/transactionTypes are returned. If I set changedDateTime filter to a date before 1/8 then all filters are applied. If I run the same query on a test customer, then all filters are also applied. This is really strange, and I hope someone can come up with an explanation and solution? So far I have to filter the response clientside, but that was really not what was looking for.
... View more
Categories:
- Categories:
-
Filters
16-08-2023
15:44
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)?
... View more
Categories:
- Categories:
-
Integrasjon
05-07-2023
09:32
Thank you so much for taking time in your holiday to help 🙂 Looks like I can get this to work. I was hoping that it would be possible to input an array of orderlines in the variables and then somehow pass this array to orderLine_update, including 'filter' and 'value'. But it doesn't look like orderLine_update can take an array as input?
... View more
03-07-2023
14:35
Thanks. Could you post an example for that? Updating one orderline is not a problem, using variable, but when we have a variable number or orderlines that should be updated.
... View more
03-07-2023
12:08
As part of an integration from WMS to Visma Business NXT, we want to update orderlines when they have finished picking, so we can set FinishNow, grouped by useByDate and/or serial. So what we are looking for is a way to update all orderlines in one api call, wither in one mutation or by batch mutations. Batch mutations does not seem to work as intented. It seems like only one mutation is performed, and looks random witch one of the mutations that is performed. How do we approach this issue?
... View more
Categories:
- Categories:
-
Orderline
03-07-2023
11:51
Can't find a place to close this subject again. But looks like it works as intended.
... View more
27-06-2023
11:08
Hello I have been trying to update an OrderLine using the message structure below. However even though no error message is returned and syntax should be correct - this requests fails to update the orderline. Can someone help me with what i am doing wrong?
... View more
Categories:
- Categories:
-
Orderline
18-11-2022
15:37
The responce is generally slow on the endpoint (7-10 sec) and then on some calls during the day they go beond 10 sec and even up to 30-40 sec. I've sent an email to developersupport@visma.com
... View more
15-11-2022
17:12
In our integration we call /controller/api/v1/shipment/<shipment number>/action/confirmShipment when a shipment has been shipped out of the warehouse. But we the responce times on these calls are quite often very slow > 10 seconds and sometimes even 20-30 seconds. After confirming the shipment, we use /controller/api/v1/shipment/<shipment number>/printShipmentConfirmation to fetch and print the shipment note, and therefore the user often experiences to be wating a long time for the shipment note to be printet. Do you have any idea why the confirmShipment endpoint is so slow, and if there is anything the customer can do to optimice the performance for the endpoint?
... View more
15-11-2022
16:53
Any update on this?
... View more
09-02-2022
15:34
Any news on this? I see it has been 2 years since the question was asked. But AddressLine3 is still not available in deliveryAddress.AddressLine3, even though the swagger documentations says it should be there.
... View more
20-01-2022
16:26
3 Kudos
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.
... View more
17-01-2022
10:11
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: I have been looking through the api, but I haven't found any endpoints that are able to do these tasks. So I am hoping that someone can guide me in the right direction?
... View more
26-11-2021
21:04
Any solution for this issue? We have the same issue, where we are not able to see the destination warehouse on the orderlines on TR orders.
... View more
29-06-2021
10:30
In the api, I see endpounts to create and update a purchase order, but I don't see endpoints for complting or canceling the order, as it is possible in the UI. How could this be done from the api?
... View more
04-02-2021
15:27
1 Kudo
Det kaldes "lotSerialNumber" i "allocations", vs"lotSerialNbr" i "shipmentDetailLines"
... View more
04-02-2021
15:17
Ahh, now I see the error. It is called "lotSerialNbr" in "shipmentDetailLines", but "lotSerialNumber" in "allocations" Thanks a lot 🙂
... View more
04-02-2021
12:19
SalesOrder and Shipment is created manually from the Financials UI. Shipment is created from the Sales Order screen.
... View more
04-02-2021
11:25
Correction: (Had updated shippedQty on the last GET shipment output. When shippedQty=0 it looks like this, with no allocations) {
"shipmentNumber": "000005",
"shipmentType": "Issue",
"status": "Open",
"hold": false,
"operation": "Issue",
"shipmentDate": "2020-12-30T00:00:00",
"customer": {
"internalId": 2846,
"number": "10000",
"name": "Allan"
},
"location": {
"id": "HOVED",
"name": "Hovedlokasjon"
},
"fromWarehouse": {
"id": "1",
"description": "Hovedlager"
},
"currencyId": "DKK",
"shippedQuantity": 0,
"shippedWeight": 0,
"shippedVolume": 0,
"packagesWeight": 0,
"controlQuantity": 0,
"deliveryAddress": {
"overrideAddress": false,
"addressId": 23,
"country": {
"id": "DK",
"name": "DANMARK"
}
},
"deliveryContact": {
"overrideContact": false,
"contactId": 24,
"name": "Allan",
"email": "alm@apportsystems.com"
},
"residentialDelivery": false,
"saturdayDelivery": false,
"useCustomerAccount": false,
"insurance": false,
"freightCost": 0,
"freightAmt": 0,
"transactionType": {
"id": 0,
"description": "Ingen (unntatt)"
},
"modeOfTrasport": {
"id": 10,
"description": "Unknown"
},
"container": false,
"shipmentDetailLines": [
{
"lineNumber": 1,
"orderType": "SO",
"orderNbr": "000004",
"inventoryNumber": "333333",
"freeItem": false,
"warehouse": {
"id": "1",
"description": "Hovedlager"
},
"location": {
"id": "1",
"name": "Standard"
},
"uom": "STK",
"shippedQty": 0,
"orderedQty": 3,
"openQty": 3,
"lotSerialNbr": "",
"description": "Testvare 3",
"orderLineNbr": 1
}
],
"shipmentOrderLines": [
{
"orderType": "SO",
"orderNbr": "000004",
"shippedQty": 0,
"shippedWeight": 0,
"shippedVolume": 0,
"note": ""
}
],
"lastModifiedDateTime": "2021-02-04T11:22:24.373",
"note": "",
"metadata": {
"totalCount": 1,
"maxPageSize": 1000
}
}
... View more
04-02-2021
09:58
Screen shot of lot/serial class is attached. About the allocation lines. That is another wierd thing. If I look in the UI there are no allocation lines before, but if I fetch the shipment in the api, there are some allocation lines already. But if I try to update the allocations, using the lineNbr, it returns an error, indicating that it can't find the allocation line. Here is the result from GET shipment {
"shipmentNumber": "000005",
"shipmentType": "Issue",
"status": "Open",
"hold": false,
"operation": "Issue",
"shipmentDate": "2020-12-30T00:00:00",
"customer": {
"internalId": 2846,
"number": "10000",
"name": "Allan"
},
"location": {
"id": "HOVED",
"name": "Hovedlokasjon"
},
"fromWarehouse": {
"id": "1",
"description": "Hovedlager"
},
"currencyId": "DKK",
"shippedQuantity": 3,
"shippedWeight": 0,
"shippedVolume": 0,
"packagesWeight": 0,
"controlQuantity": 3,
"deliveryAddress": {
"overrideAddress": false,
"addressId": 23,
"country": {
"id": "DK",
"name": "DANMARK"
}
},
"deliveryContact": {
"overrideContact": false,
"contactId": 24,
"name": "Allan",
"email": "alm@apportsystems.com"
},
"residentialDelivery": false,
"saturdayDelivery": false,
"useCustomerAccount": false,
"insurance": false,
"freightCost": 0,
"freightAmt": 0,
"transactionType": {
"id": 0,
"description": "Ingen (unntatt)"
},
"modeOfTrasport": {
"id": 10,
"description": "Unknown"
},
"container": false,
"shipmentDetailLines": [
{
"lineNumber": 1,
"orderType": "SO",
"orderNbr": "000004",
"inventoryNumber": "333333",
"freeItem": false,
"warehouse": {
"id": "1",
"description": "Hovedlager"
},
"location": {
"id": "1",
"name": "Standard"
},
"uom": "STK",
"shippedQty": 3,
"orderedQty": 3,
"openQty": 0,
"lotSerialNbr": "",
"description": "Testvare 3",
"allocations": [
{
"lineNbr": 20,
"itemId": "333333",
"location": {
"id": "1",
"name": "Standard"
},
"lotSerialNumber": "",
"quantity": 1,
"uom": "STK",
"description": "Testvare 3"
},
{
"lineNbr": 21,
"itemId": "333333",
"location": {
"id": "1",
"name": "Standard"
},
"lotSerialNumber": "",
"quantity": 1,
"uom": "STK",
"description": "Testvare 3"
},
{
"lineNbr": 22,
"itemId": "333333",
"location": {
"id": "1",
"name": "Standard"
},
"lotSerialNumber": "",
"quantity": 1,
"uom": "STK",
"description": "Testvare 3"
}
],
"orderLineNbr": 1
}
],
"shipmentOrderLines": [
{
"orderType": "SO",
"orderNbr": "000004",
"shippedQty": 3,
"shippedWeight": 0,
"shippedVolume": 0,
"note": ""
}
],
"lastModifiedDateTime": "2021-02-04T09:48:52.5",
"note": "",
"metadata": {
"totalCount": 1,
"maxPageSize": 1000
}
}
... View more
04-02-2021
09:02
I am trying to update a shipment via [PUT] /controller/api/v1/shipment/{shipmentNbr} The inventory is set to "Tracking track serial numbers", and I am via Financials UI, allowed to make allocations and update serial numbers on each allocation. But when I try to do the same via api, the allocations are created, but are not updated with the serial numbers I specify. Instead, all the lines are set with the serial number specified on shipmentDetailLines, if I set it there. If I omit it there, it is simply not set on the allocations. Here is my request content {
"shipmentType": {
"value": "Issue"
},
"operation": {
"value": "Issue"
},
"shipmentDate": {
"value": "2020-12-30T15:41:38.044Z"
},
"shipmentDetailLines": [
{
"operation": "Update",
"lineNumber": {
"value": 1
},
"shippedQty":{
"value": 3
},
"allocations": [
{
"operation": "Insert",
"lineNbr": {
"value": 10
},
"lotSerialNbr": {
"value": "1234510"
},
"quantity": {
"value": "1"
}
},
{
"operation": "Insert",
"lineNbr": {
"value": 11
},
"lotSerialNbr": {
"value": "1234511"
},
"quantity": {
"value": "1"
}
},
{
"operation": "Insert",
"lineNbr": {
"value": 12
},
"lotSerialNbr": {
"value": "1234512"
},
"quantity": {
"value": "1"
}
}
]
}
]
} The result on the shiment allocation UI in Financials UI, can be seen in the attachment. Company id: 3011577 Shipment 000005
... View more
02-02-2021
09:11
Hvorfor oppdateres ikke Lot / Serienummer på allokeringerne mine som angitt i api kaldet? De overtar ganske enkelt innholdet fra $.shipmentDetailLines.lotSerialNbr?
... View more
01-02-2021
10:11
Jeg prøver å oppdatere en levering via [PUT] /api/controller/api/v1/shipment/{shipmentNbr} Varen er satt til "Sporing spor serienumre", og jeg kan via Financials fint få lov til å lage tildelinger og koble serienummer på. Men når jeg prøver å gjøre det samme via api, blir ikke allokeringene oppdatert med serienumrene jeg spesifiserer. I stedet er alle linjene satt med serienummeret som er spesifisert på shipmentDetailLines (jeg har ikke lov til å utelate serienummeret på shipmentDetailLines) Her er hva jeg prøver: {
"shipmentType": {
"value": "Issue"
},
"operation": {
"value": "Issue"
},
"shipmentDate": {
"value": "2020-12-30T15:41:38.044Z"
},
"shipmentDetailLines": [
{
"operation": "Update",
"lineNumber": {
"value": 1
},
"lotSerialNbr": {
"value": ""
},
"allocations": [
{
"operation": "Insert",
"lineNbr": {
"value": 5
},
"lotSerialNbr": {
"value": "123452"
},
"quantity": {
"value": "1"
}
},
{
"operation": "Update",
"lineNbr": {
"value": 6
},
"lotSerialNbr": {
"value": "123453"
},
"quantity": {
"value": "1"
}
},
{
"operation": "Update",
"lineNbr": {
"value": 7
},
"lotSerialNbr": {
"value": "123454"
},
"quantity": {
"value": "1"
}
}
]
}
]
} Resultat i Financials
... View more
Categories:
- Categories:
-
API:Shipment
Activity Feed for AllanEgebjerg
- Posted Re: KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 10-07-2024 11:33
- Posted Re: KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 10-07-2024 11:30
- Posted Re: KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 10-07-2024 11:18
- Posted Re: Inventory Get SortOrder on Forum in Developers Visma.net. 13-05-2024 13:46
- Kudoed Sv: Filter documentType not when also filtering on changedDate after 1/8?? for Florian Haase. 27-09-2023 09:27
- Posted Filter documentType not when also filtering on changedDate after 1/8?? on Diskusjon. 12-09-2023 12:01
- Posted Using correct stock when working with serial(lot/batch) and usebydate on Diskusjon. 16-08-2023 15:44
- Posted Re: Updating orderlines on order in one api call on Diskusjon. 05-07-2023 09:55
- Posted Sv: Updating orderlines on order in one api call on Diskusjon. 05-07-2023 09:32
- Posted Sv: Updating orderlines on order in one api call on Diskusjon. 03-07-2023 14:35
- Posted Updating orderlines on order in one api call on Diskusjon. 03-07-2023 12:08
- Posted Re: OrderLine_update fails to update line on Diskusjon. 03-07-2023 11:51
- Posted Re: API Updates on Diskusjon. 30-06-2023 14:48
- Posted OrderLine_update fails to update line on Diskusjon. 27-06-2023 11:08
- Tagged OrderLine_update fails to update line on Diskusjon. 27-06-2023 11:08
- Tagged OrderLine_update fails to update line on Diskusjon. 27-06-2023 11:08
- Kudoed Re: Slow request to confirmShipment for Yıldırım. 28-11-2022 09:42
- Posted Re: Slow request to confirmShipment on Forum in Developers Visma.net. 18-11-2022 15:37
- Posted Slow request to confirmShipment on Forum in Developers Visma.net. 15-11-2022 17:12
- Posted Sv: AddressLine3 on Shipment endpoint on Forum in Developers Visma.net. 15-11-2022 16:53
Kudos from
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America