HI  Is there changes in the CustomerInvoice Endpoint?    As of yesterday morning we have one integration which suddenly stopped working and we can not create customerinvoices anymore. All the invoices get the same error, and I have also tried with old invoices which have been created without problem earlier.   error:  { "message": "VismaId: 33469094-37dc-4603-bac7-fb73b728a50e. Value cannot be null.\r\nParameter name: source" }  first error occured approx 8 am yesterday   ... View more

Hi  We are having trouble with the Severa/PM API, some of our calls are getting blocked by Severa firewall.  And in the documentation it says to contact API Support, but as far as I know there is no dedicated API support, so I am trying to post here, and maybe someone can forward it to the right contact person?     ... View more

Jag har problem med att vissa anrop i våra integrationer blir blockerade av någon brandvägg i PM.  Kollar man i dokumentationen står det att man skall kontakta API support men så vitt jag vet finns det inget speciell API support/utvecklar forum för PM, så jag testar här.   detta är akut, då det sker i integrationer som ligger skarpt och anropen går igenom ibland och ibland inte.      ... View more

and we are getting Bad Gateway in all API calls in almost all our integrations, AGAIN.    this is not okay!   ... View more

HI    I get SQL error when when we tries to create journal transactions fpr one customer. It indicates that Ledger is null, but it's "1" in the request, and it also exists in the customer setup.   VismaId: ca46eb5d-d476-446f-b93e-ada343ef5f62. Error creating journal transaction. Cannot insert the value NULL into column 'LedgerID', table 'ERP_SE_DEMO_0020.dbo.GLTran'; column does not allow nulls. INSERT fails. The statement has been terminated.   example json in the request:  { "hold": { "value": true }, "transactionDate": { "value": "2023-11-27 11:12:38" }, "ledger": { "value": "1" }, "description": { "value": "Bambora" }, "journalTransactionLines": [ { "operation": "insert", "accountNumber": { "value": "1931" }, "debitAmountInCurrency": { "value": 137969.25 } }, { "operation": "insert", "accountNumber": { "value": "1580" }, "creditAmountInCurrency": { "value": -137969.25 } } ] } ... View more

HI    since yesterday we are getting error when creating a salesorder in the salesorder api,  this is critical.  it's black friday/black week and one of our customers can not create any orders from the webshop.   the integrations has been running without problem for several months and the error started yesterday morning. --- System.Exception: Error retrieving response. Check inner details for more info. ---> System.Net.Http.HttpRequestException: No such host is known. (salesorder.visma.net:443) ---> System.Net.Sockets.SocketException (11001): No such host is known. ... View more

Hi    after approx. 01 today we only get internal server error from salesorder api, in the GET request.  we get the errors when adding the modifiedSince parameter? it has been working fine until tonight.  I have also tried to run the request in swagger, same there, 500 error. and no message. (I have also tried 2 different customers, same error)   have you made any updates??   This is really urgent since we don't receive any orders back.      I see that the naming of the lastchanged parameter seems to be different in different requests, but I don't know if it has always been like that or if that has something to do with it.       ... View more

When adding a shipment to a salesorder via the API, the shipment allocations are already set with what seemes to be a suggestions by the system. Is it possible to turn this off?   How do you add new allocation lines of components? I just can't get it to work. Could you provide a example of how the json object should look?   When I'm trying to update a shipment with data below, i get the following error: "message=VismaId: d469ffd1-6e70-483f-ab72-c426ecb31b64. Object reference not set to an instance of an object."   { "shipmentType":{ "value":"Issue" }, "shipmentDetailLines":[ { "operation":"Update", "lineNumber":{ "value":1 }, "allocations":[ { "operation":"Delete", "lineNbr":{ "value":2 }, "lotSerialNumber":{ "value":"2014.31" }, "quantity":{ "value":2.000000 } }, { "operation":"Delete", "lineNbr":{ "value":3 }, "lotSerialNumber":{ "value":"2014.32" }, "quantity":{ "value":2.000000 } }, { "operation":"Delete", "lineNbr":{ "value":4 }, "lotSerialNumber":{ "value":"2014.33" }, "quantity":{ "value":2.000000 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.31" }, "quantity":{ "value":1.0 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.93" }, "quantity":{ "value":1.0 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.32" }, "quantity":{ "value":1.0 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.94" }, "quantity":{ "value":1.0 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.98" }, "quantity":{ "value":1.0 } }, { "operation":"Insert", "lotSerialNumber":{ "value":"2014.97" }, "quantity":{ "value":1.0 } } ] } ] }     ... View more

Hej  vi har problem med att "projekt uppdaterat"-datum (Senast ändrat datum) inte alltid ändras/uppdateras när man ändrar någon information på projekten. det gör det väldigt svårt och omständligt att fånga upp ändringar i projekt ur ett utvecklarperspektiv (genom API:et)  när man endast vill hämta förändrade projekt. (ohållbart att hämta alla projekt varje gång när det rör sig om väldigt mycket projekt i installationerna)   Datumet ändras exempelvis inte när man uppdaterat projektet med nyckelord eller när man ändrar något i faserna. (det går visserligen att får ut ändrade faser separat genom API:et men då får man hämta alla ändrade faser och sen till vilket projekt det hör, vilket också känns ganska omständligt.) Båda dessa värden hör ju ihop med projektet och bör rimligtvis trigga att projektet har förändrats.    projekt utan nyckelord   projekt där jag precis lagt till nyckelord, datumet är det samma och det går inte fånga upp att projektet har förändrats.         ... View more