About Florian Haase

Florian Haase · ‎09-09-2024

Hi Oskar, no, the problem was solved after we escalated it internally in Visma in the weekend. We could not wait until today since the whole integration platform stopped. I think somebody in the connect team knows exactly what happened, but I think it was due to a lot of token traffic from our side after the API got to live again. But we have to find out how we can quick enough answers when all is stopping due to such incidents also during a weekend. Florian

Florian Haase · ‎02-06-2023

Fantastic - you are right. Switching the App-Serviceplans fixed the problem. Thank you for helping!

Florian Haase · ‎02-06-2023

Hi, thanks for this fantastic description. I restarted the app-services first, but that did not help much. The error situation is a bit weird - now our UI is showing the right data but this curl failed: I will try to update the app-serviceplan. Florian

Florian Haase · ‎02-06-2023

We still have a lot of errors here. I tried to restart the app but that did not help much. Now I often get the error: Unable to connect to the remote server ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 91.123.56.208:443

Florian Haase · ‎02-06-2023

Is this related to Azure? I don't get these messages in debug and we have also other integrations which are running as services which don't seem to have the same problem....

Florian Haase · ‎02-06-2023

The same here, I have a lot of this SocketException errors here.

Florian Haase · ‎04-04-2023

Nothing is working here about the Swagger. What is the correct address just now?

Florian Haase · ‎17-03-2023

The same here, I get flooded by these error-messages in our alert-system! And the statuspage still shows operational?

Florian Haase · ‎02-02-2023

We are using ngrok a lot. This also has a web-interface and a great way to see if the webhook is triggered and also the payload of the webhook message. Florian

Florian Haase · ‎05-12-2022

Hi Magnus what is the status here? We have still the same issue... Florian

Florian Haase · ‎14-10-2022

Is there any progress here? We also do need that. Florian

Florian Haase · ‎14-09-2022

Hi Yildirim, sorry that this takes a bit of time. But now I have found out that the problem could be, that the user which is connected to the used token has been deleted. That was not us who generated the token and we are not using it either. Therefore it was difficult to understand what happened here. In addition I got feedback that only calls to to the print endpoint are not working - but now I guess that the whole integration stopped. We generate a new token on a new user and check if this solves the problem. Florian

Florian Haase · ‎08-09-2022

Hi Yildirim, in postman it looks this way: I wonder if there has changed something about the user-roles in admin - I will check this at the same time and we try to do the same operation in the UI

Florian Haase · ‎07-09-2022

- Do you have any exception? We only have this status code: 11:20:51.0 (39088503)|CALLOUT_REQUEST|[24]|System.HttpRequest[Endpoint=https://integration.visma.net/API/controller/api/v1/customerCreditNote/402831/print, Method=GET] 11:20:51.0 (356186286)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:512 11:20:51.0 (371086413)|CALLOUT_RESPONSE|[24]|System.HttpResponse[Status=Forbidden, StatusCode=403] - Is the error company specific ? (Please also try on another company and inform us) We don't have another company to check it out. - Have you checked the access roles of the user that the token generated with ? We haven't change anything with our roles or a token. We use the same token all the time and previously these endpoints worked fine with the current token.

Florian Haase · ‎07-09-2022

Hi there are still problems with this 403 error. This time regarding creating and printing Credit Notes: GET /controller/api/v1/customerCreditNote/{creditNoteNumber}/print POST /controller/api/v2/customerCreditNote When creating invoices or credit notes and opening them as pdf files we get error messages. The HTTP response for every callout returns: "status code 403". CompanyID: 747313 Florian

Florian Haase · ‎31-08-2022

Sorry that paste went wrong. Its 3116476

Florian Haase · ‎31-08-2022

080902

Florian Haase · ‎31-08-2022

Same problem here: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html> Faktura 203797 - <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html> We try to add attachment to incoming invoices. That critical for us because we use that for reverse invoicing.

Florian Haase · ‎01-06-2022

I tried also to send the http request without Escape characters - but it results in the same response. https://integration.visma.net/API/controller/api/v1/customer?PageNumber=1&PageSize=500&attributes={"GAKUNDNR":"41031"}

Florian Haase · ‎01-06-2022

Hi I don't know what happened here, but since yesterday the API-call: https://integration.visma.net/API/controller/api/v1/customer?PageNumber=1&PageSize=500&attributes=%7B%22GAKUNDNR%22:%2241031%22%7D results in: {"message":"An error has occurred.","exceptionMessage":"The 'CompressedContent' type failed to serialize the response body for content type 'application/json; charset=utf-8'.","exceptionType":"System.InvalidOperationException","stackTrace":null,"innerException":{"message":"An error has occurred.","exceptionMessage":"Incorrect syntax near ')'.\r\nInvalid usage of the option NEXT in the FETCH statement.","exceptionType":"System.Data.SqlClient.SqlException","stackTrace":" at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)\r\n at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)\r\n at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)\r\n at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()\r\n at System.Data.SqlClient.SqlDataReader.get_MetaData()\r\n at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)\r\n at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)\r\n at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)\r\n at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)\r\n at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)\r\n at System.Data.SqlClient.SqlCommand.ExecuteReader()\r\n at Visma.net.ERP.Api.AR.Repository.CustomerRepository.RunQueryUpfront(ICustomerQueryFilter customerQueryFilter, List`1 customerNotesIds) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\AR\\Repository\\CustomerRepository.cs:line 1034\r\n at Visma.net.ERP.Api.AR.Repository.CustomerRepository.<GetCustomersPaginantionUpfornt>d__13.MoveNext() in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\AR\\Repository\\CustomerRepository.cs:line 442\r\n at Visma.net.ERP.Web.Api.Repositories.CustomerWebRepository.<GetAllCustomers>d__15.MoveNext() in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Web.Api\\Repositories\\CustomerWebRepository.cs:line 161\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)\r\n at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)\r\n at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)\r\n at System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, Encoding effectiveEncoding)\r\n at System.Net.Http.Formatting.JsonMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, Encoding effectiveEncoding)\r\n at System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.WriteToStreamAsync(Type type, Object value, Stream writeStream, HttpContent content, TransportContext transportContext, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n at PX.Api.Compression.BaseCompressor.<Compress>d__4.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n at PX.Api.Compression.CompressedContent.<SerializeToStreamAsync>d__4.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n at System.Web.Http.WebHost.HttpControllerHandler.<WriteBufferedResponseContentAsync>d__22.MoveNext()"}} Our webshop integration is stopped therefore. What happened? Florian

Florian Haase · ‎01-06-2022

We are up and running again after generating new tokens. But this stopped our whole integration plattform. Hope that this was a single-time event.

Florian Haase · ‎25-04-2022

Hi, we do need the field PaymentReference in CustomerCreditNote endpoints (Post and Put) / object CustomerCreditNoteUpdateDto (ref Forumpost). The problem is that we have a customer which is importing thousands of invoices and creditNotes with CID-number from Svea/IScala. The customers are paying these by a structured payment which contains both the invoices-CID number- and creditNote-CID numberreferences in the payment. This is working quite badly when we only are able to import the invoice-CID numbers by the API. Until we get a solution here we have to import the creditnote-CID numbers by import-Scenario manually, therefore we hope that this could be solved. Florian

Florian Haase · ‎25-04-2022

ok, I do so.

Florian Haase · ‎22-04-2022

Hi, is the field paymentReference on CustomerCreditNoteUpdateDto missing? Florian

Florian Haase · ‎06-04-2022

Hi 1) The case is closed by deactivating the postcode validation. 2) Yes UI reports the correct errormessage, but the API reports Object reference not set to an instance of an object 3) No we did not, because its the integrated solution which is owner of the customerdata (and the postcodes). Its no point to correct the customerdata in VNet because it will be overwritten again by the pre-system. 4) The Post-Json does not contain anything other relevant than the customer-number on the order-header. (no point to send the details from the customer here to everybody) Florian

Florian Haase · ‎06-04-2022

Hi I had just a case in a Norwegian Visma.Net client. There was registered one customer with country "Netherland" and a wrong postcode. Our integration registered an order by API and got following reponse (here from swagger): {"message": "VismaId: 7f85e754-bfb8-4eff-a339-453c3f99984a. Object reference not set to an instance of an object."} in the userinterface: Det oppsto en feil under behandling av feltet Postnr. verdi 8861 Feil: Postnr. følger ikke reglene for valgte land. Could the error-handling in the API be improved here? Florian

Florian Haase · ‎24-02-2022

Hi the Location endpoint returns a bad request code when we run a put and the location was not found. Return-Message: "{\"message\":\"Location 7080000065264 of bAccount 80001 not found\"}" StatusCode = 400 All the other endpoints returns a Not Found Status code (404) Not sure whats actually correct since 404 actually means that the resource does not exist per definition of this code. But we use this statuscode to run a post after the put to create the record instead of update. This is implemented generic so it makes trouble if the statushandling is not the same for the endpoints. Florian

Florian Haase · ‎10-02-2022

Yes thats right. We would get a bit closer the solution if we could get the InventoryNumber in the discount Endpoint in addition of the ID. I'm not sure that storing a match table is a good design - than we have one more source for possible errors. But just to get rid of the problem I change it now to get the whole inventory-register with filter on integrated inventory Items. When I only expand the attributes and nothing else it takes about 3 minutes for about 3000 inventories. That was acceptable here and now. We also looked at the new SalesOrder API - Could this be a possible solution - is it much faster? Florian

Florian Haase · ‎10-02-2022

Hi, we have an integration here based on discount-agreements. The customer creates a lot of agreements with a connection between customergroup or customer to inventory items. In the integration to the 3. party system Visma.Net is declared as the mastersystem. We need to refresh the discount agreements completely in the 3. party system once a night, otherwise we run into problems with deleted agreements or deleted connections. (changes and new ones we can catch, but not deleted ones (thats actually the first problem)). First we thought that the minor part of agreements is based on item-connections (instead of item-group), but now I see thats actually the major part. That means nearly each inventory-item has any connection to one or more of the agreements. Since we need the External InventoryID (stored in the attributes on the inventory-Items) I run a get call now on each involved inventory-Item to get the external ID. (we get each inventory just once even it is used on several discount agreements since we store the result in the memory and reuse it). That causes in the end an overflow in max number of requests (at least in some situations). It seams to be better to get the whole inventory database from Visma.Net first with some fewer calls. We did not do this by design first, because the inventory endpoint is so extremly slow but that would of course reduce the number of calls. We will get some more inventories than needed but that's maybe the only way to get around the problem? I start to wonder a bit if it would be better to store the internal Visma-Inventory ID in the third-party system and get the whole inventory list from there instead. I guess that would be many times faster than asking the Visma.Net API or do you have any other suggestions? Florian

Florian Haase · ‎10-02-2022

Thank you, thats great.

Re: 403 Forbidden from /connect/token

Svar: System.Net.Sockets.SocketException

Svar: System.Net.Sockets.SocketException

Sv: System.Net.Sockets.SocketException

Sv: System.Net.Sockets.SocketException

Sv: System.Net.Sockets.SocketException

Sv: https://integration.visma.net/API-index/ is un...

Svar: Urgent - Connection to cache service failed

Sv: Is it possible to see the webhook response?

Re: Empty VATCode on CashtransactionLine

Sv: Inventory - POST/PUT recommended price

Re: Still some 403 errors

Re: Still some 403 errors

Re: Still some 403 errors

Still some 403 errors

Sv: "You don't have permission to access this reso...

Sv: "You don't have permission to access this reso...

Sv: "You don't have permission to access this reso...

Sv: Exception when filtering on customes with attr...

Exception when filtering on customes with attribut...

Sv: Processing Exception while reading ODP respons...

Field PaymentReference in CustomerCreditNote

Re: Field paymentReference on CustomerCreditNote

Field paymentReference on CustomerCreditNote

Re: PostCode validation and API Reponse

PostCode validation and API Reponse

Location Update does return bad request when locat...

Re: Hitting max number of requests

Hitting max number of requests

Re: Inventory Get SortOrder

Useful pages

About Visma

Contact us

Follow us