Hi,   In our app we have requested the scope vismanet_erp_service_api:create:   For most of our clients this works as expected. However for one client we are unable to POST https://connect.visma.com/connect/token   For the failing client the response we get says: { "error": "invalid_scope" }   I have narrowed it done to be caused by the scope vismanet_erp_service_api:create.   The following body works grant_type=client_credentials&scope=visma.net.erp.salesorder:read visma.net.erp.salesorder:write vismanet_erp_service_api:delete vismanet_erp_service_api:read vismanet_erp_service_api:update&client_id=<client id>&client_secret=<client secret>&tenant_id=<tenant id>   But when I add the scope for vismanet_erp_service_api:create the request fails with { "error": "invalid_scope" }   The client says that they have activated all the requested permissions by the integration.   What can I do to find out why the create scope fails?   /Ronny ... View more

Hi,   This is similar to the error described in https://community.visma.com/t5/Forum-in-Developers-Visma-net/Unable-to-perform-action-confirmShipment/td-p/345129.   I have a problem now where we fail to perform the action /controller/api/v1/shipment/{shipmentNumber}/action/confirmShipment.   The response we get is { "message": "Error confirming shipment: Object reference not set to an instance of an object." }   It works for other customers except this one, but I cannot see what it different here.   The full call that we make is POST https://integration.visma.net/API/controller/api/v1/shipment/4723828/action/confirmShipment   Can you see if there is something wrong with that call?   When the user performs the action manually in the Visma UI it works as expected, i.e. the shipment delivery update status to "Bekräftad".   /Ronny ... View more

Hi,   We have an integration that is attempting to trigger the action /confirmShipment. For one of our customers we have recently been getting an error message with the following info while performing that action: > "Error confirming shipment: Error: Updating 'ROT/RUT' record raised at least one error. Please review the errors."   I have trouble getting in contact with the customer, so I was hoping someone can tell me why this error occurs.   The shipment is connected to a sales order where the field isRotRutDeductible is set to true, however the isRotRutDeductible field on every order line is set to false. Don't know if this affects anything but for orders where the order field isRotRutDeductible is set to false the integration seem to be able to perform the confirmShipment action.   Best regards Ronny ... View more

Hi, Have you made any changes to the logic regarding updating shipmentDetailLines recently? We used to be able to update the lotSerialNumber of an allocation previously, but that is no longer possible. We experience this to have changed sometime between 2023-01-31 10:44:34 and 2023-07-02 14:29:48.   For example, if the shipmentDetailLine looks like this: { "shipmentDetailLines": [ { "lineNumber": 1, "orderType": "SU", "orderNbr": "003104", "inventoryNumber": "ZM000776", "freeItem": false, "warehouse": { "id": "1 ", "description": "Hovedlager Westcontroll" }, "location": { "id": "1", "name": "Standard" }, "uom": "STK", "shippedQty": 1.0, "orderedQty": 1.0, "openQty": 0.0, "lotSerialNbr": "ZPR215126", "description": "Zaptec Pro", "allocations": [ { "lineNbr": 3, "itemId": "ZM000776", "location": { "id": "1", "name": "Standard" }, "lotSerialNumber": "ZPR215126", "quantity": 1.0, "uom": "STK", "description": "Zaptec Pro" } ], "orderLineNbr": 1 } ] } We want to modify the lotSerialNumber. We used to be able to do that using the following data: { "shipmentDetailLines": [ { "operation": "Update", "lineNumber": { "value": 1 }, "shippedQty": { "value": 1.0 }, "allocations": [ { "operation": "Update", "lineNbr": { "value": 3 }, "lotSerialNumber": { "value": "ZPR215126X" }, "quantity": { "value": 1.0 } } ] } ] } When we send that data now we get the response: { "message": "Error: Updating 'Shipment line split' record raised at least one error. Please review the errors.\r\n" }  Has anything changed recently regarding this?   Best regards Ronny ... View more

Hi,   I am trying to create an inventory issue, and since there are some items with lot/serialno I need to provide that as well.   I am trying to post the following data: { "issueLines": [ { "warehouseId": { "value": "1" }, "tranType": { "value": "Issue" }, "operation": "Insert", "inventoryNumber": { "value": "ZM000736" }, "locationId": { "value": "1" }, "quantity": { "value": 3.0 }, "reasonCode": { "value": "2" }, "description": { "value": "" }, "allocations": [ { "operation": "Insert", "lineNbr": { "value": 1 }, "location": { "value": "1" }, "lotSerialNumber": { "value": "SVE98765" }, "quantity": { "value": -1.0 } }, { "operation": "Insert", "lineNbr": { "value": 2 }, "location": { "value": "1" }, "lotSerialNumber": { "value": "SVE98766" }, "quantity": { "value": -1.0 } }, { "operation": "Insert", "lineNbr": { "value": 3 }, "location": { "value": "1" }, "lotSerialNumber": { "value": "SVE98776" }, "quantity": { "value": -1.0 } } ] } ], "date": { "value": "2022-05-20T10:07:16.563" }, "externalReference": { "value": "70" }, "description": { "value": "" } }  The response says that I did not provide either location and/or lot/serial number: { "message": "VismaId: 091b387b-aff6-49c5-b8bb-f756385ead1c. Error creating inventory issue. Error: Inserting 'Inventory transaction' record raised at least one error. Please review the errors.\r\nOne or more lines contain unassigned location and/or lot/serial number.\r\n" }  Though when I check the data that I send I think I provide both location and lot/serial nunber for every allocation line.   Can anyone see what I am doing wrong?   Best regards Ronny Videkull ... View more

Hi,   I have a problem now where we fail to perform the action /controller/api/v1/shipment/{shipmentNumber}/action/confirmShipment.   The response we get is { "message": "Error confirming shipment: Object reference not set to an instance of an object." }   It works for other customers except this one, but I cannot see what it different here.   The full call that we make is POST https://integration.visma.net/API/controller/api/v1/shipment/4709289/action/confirmShipment   Can you see if there is something wrong with that call?   Best regards, Ronny Videkull ... View more