About Florian Haase

Florian Haase · ‎17-12-2024

And even more interesting that the same happens when I go from Associate and run a joindown to the balance. Same error on this tenant, works fine on another.

Florian Haase · ‎17-12-2024

I think you are right Ole, that works fine with another company. Very interesting...

Florian Haase · ‎17-12-2024

Hi, both the query: query { useCompany(no:XXXXXXX) { customerCurrentBalance {items { joinup_Associate_via_Customer { customerNo } customerNo } } } } or query { useCompany(no:XXXXXXX) { customerCurrentBalance {items { joindown_Associate_via_CustomerCurrentBalance { items { name } } customerNo } } } } are failing with en sql error: { "message": "Error: SQL command no. 3014 failed.", "path": [ "useCompany", "customerCurrentBalance", "items", 0, "joindown_Associate_via_CustomerCurrentBalance", "items" ], "extensions": { "data": { "status": 2, "status_name": "databaseError" } } } even both queries are "valid" due to the GraphiQL Interface. I can't get both the customerbalance and customerdata in the same query... Florian

Florian Haase · ‎10-12-2024

Thank you, now it works 🙂

Florian Haase · ‎10-12-2024

We did find the processing but it does return a guid in filepath (i think that proofs that the document is saved on blob). But filebytes is empty.

Florian Haase · ‎10-12-2024

Is it not possible to download the documents again?

Florian Haase · ‎09-12-2024

We have implemented this now and are checking the statuscode instead.

Florian Haase · ‎09-12-2024

Great improvment, but could you please be a bit more careful with such breaking changes? We have a retry strategy in our code exactly due to this problem: (result.StatusCode == HttpStatusCode.OK && (content?.Contains("The request could not be executed: unable to parse response data") ?? false) && attempts < 4) This change breaks absolutely all integrations for all customers here where the row is locked! Florian

Florian Haase · ‎05-12-2024

Er det noe fremdrift her? Her står fortsatt alt.

Florian Haase · ‎05-12-2024

The API seems to be partially down. We have thousands of messages of problems with Error trying to resolve field 'items'.

Florian Haase · ‎22-11-2024

Hi the last night between 4 o'clock until about 7 o'clock we had a mass of Response status code does not indicate success: 503 (Service Temporarily Unavailable) errors. Now its up and running again, but I just wonder if this was a serverside problem or something which went wrong on our side? Florian

Florian Haase · ‎28-10-2024

Hi, interesting problem here: In the exchange Table the fromDate column is a part of the primary key. Due to paging issues when not sort-ordering by primary key columns we have implemented a generic way to sort always by PK (something Visma should have implemented in the API-Layer, but that's another thread). In the Exchange-Table scheme the fromDateAsDate column is also marked as primaryKey even this is a generated column by the API-engine. OrderBy on that column will not work. The PK marking of that column should be removed on all tables where fromDate is a part of the PK. We have not checked if there are any time-columns with the same problem... Florian

Florian Haase · ‎16-10-2024

What is the status here? We also need the suspension date info and still can't get this information from the API. We wonder how to do it?

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 · ‎27-08-2024

Hi Looks like that we have found an issue regarding the handling of memo content in combination with the API: When you load a page (or call it a window, screen or setup) which contains memos and we update the content of these memos in the background by the API the UI will not show the updated version. Even not if you change the page and even not if you refresh the data. The only way to get the updated data is to close the window-setup and reopen it again. Both the return value from the API-show the right value and the Graphi-QL too Florian

Florian Haase · ‎14-12-2023

Yes there is: We currently offer a solution tailored for accounting offices. In this context, it is essential for us to identify any open customer transactions and perform specific processes on them. Presently, our approach involves executing a SQL query to determine the existence of open transactions, and subsequently, we record this information in either a master client or the vbsys. This allows us to selectively carry out the necessary processes only for those clients with active open transactions. However, this method may pose challenges in Bnxt due to the need to iterate through over 1000 companies to identify where open transactions exist. To streamline this process, we initially considered leveraging the TaskOverview. While an alternative solution involving webhooks might be viable, it could introduce technical complexities and potentially be less stable compared to the simplicity of retrieving information directly from a table. Florian

Florian Haase · ‎14-12-2023

Sorry - that is not solved. As I wrote we did connect the taskOverview in BNxt to the Isv - user but the API request with that isv-user still results in an empty response

Florian Haase · ‎13-12-2023

One thing we wonder about: These taskOverviews are defined per user. When we sent in the first request (above) the taskOverview was not connected to the isv -- user. That we have fixed now but it still results in a null - response.

Florian Haase · ‎12-12-2023

Hmm, UI shows: API request: query { useCustomer(no:4613192 ) { taskOverview { items { companyName count description } } } } shows: { "data": { "useCustomer": { "taskOverview": { "items": null } } }, "extensions": { "vbnxt-trace-id": "00000000000000005d0630672b22937c" } }

Florian Haase · ‎11-12-2023

Hi we try to find the correct API-table for UI Overvåkningspunkt or probably TaskOverview in the datamodel. But we can't find the data which are shown in the UserInterface. Could you help us to find the right GraphQL table? Florian

Florian Haase · ‎30-11-2023

Yes, also we have reported this before.

Florian Haase · ‎30-11-2023

Did you set this adding / removing of bit-values on a feature-list for future versions? We also see that this is needed.

Florian Haase · ‎26-09-2023

I guess this is the same problem as in my thread Filters on CompanyChangeLog Thats really critical. It seems like if the changedDateTime filter does not hit any row together with the other filters the other filter are being overridden in any way and you get a wrong result. We just recognized the same problem on GeneralLedgerAccounts with filter on accountNo

Florian Haase · ‎18-09-2023

Sorry, I did see this first now that we have some " in the text. The question is more how to escape these " in correct way...

Florian Haase · ‎18-09-2023

Followin mutation: {mutation { useCompany(no: 4655191) { orderLine_create(values: [{ orderNo: 1736 lineNo: 1 productNo: "TEQ1001" processingMethod2: 81920 processingMethod1: 0 processingMethod4: 262144 quantity: 1 priceInCurrency: 9999 }, { orderNo: 1736 lineNo: 2 productNo: "TEQ1" structureLevel: 1 processingMethod2: 16385 description: "Eldøyane Camp Aker, Eldøyane, Stord, Norge-"Busshålo", Stord, Norge" processingMethod1: 4096 quantity: 1 orgUnit1: 3131 transactionInformation1: "TB-032193-S01-N002" transactionInformation2: "STD" structureHeadLineNo: 1 priceInCurrency: 9999 }, { orderNo: 1736 lineNo: 3 productNo: "TEQTurInf" processingMethod2: 422330368 memoNo: 1538 }]) { affectedRows, items { orderNo lineNo description changedByUser changedDateTime } } } }} Results in: {"Error parsing query: Unexpected character \"å\""} What is the right way to send "å"?

Florian Haase · ‎12-09-2023

Ok, That would also be a very rare scenario. But good to know. Thank you

Florian Haase · ‎11-09-2023

Hi, Is it possible in the _like queries to escape the % - character for differencing between text or search-character? When I for example have a text: _eq: "My text contains a % character" and if I now want to find all rows which contains exact this text, I have an issue: _like: "%My text contains a % character%" would also hit a row with the content: "My text contains a # character" the first and the last character are meant as wildcard search characters but the one in the middle as a text. Its only a question and so far only a theoretical issue, but if there is a possibility to escape the character in the middle it would be great to know... Florian

Florian Haase · ‎11-09-2023

The problem is that the reference to the client_id is lost when an user updates the batch. The updating user gets the owner of the batchcopy and it is not possible any more to filter out what is imported by the API. But due to revision we have to have the possibility to filter on API-Imports to be able to make check-reports. In the first version I think it would be enough for us, to have an own origin on API-Imports.

Florian Haase · ‎08-09-2023

I guess that the limitation already hits on a layer above the API, for example on the webserver? - it does not look like a client limitation since we get a HTTP-Responsecode...

Florian Haase · ‎08-09-2023

The companyNo should be a 7 digit number which relates to the companyID from the Visma Connect plattform and not the internal Visma Business CompanyNumber. The advantage is that you can write API-integrations across different customers by using the Visma-unique companyNumbers.

Sv: Joinup / joindown from customerCurrentBalance

Sv: Joinup / joindown from customerCurrentBalance

Joinup / joindown from customerCurrentBalance

Re: Download document

Re: Download document

Sv: Download document

Re: Error: The request could not be executed: unab...

Re: Error: The request could not be executed: unab...

Sv: API Down

API Down

API down?

FromDateAsDate column is marked as primary Key

Sv: Suspension date

Re: 403 Forbidden from /connect/token

Memo-Content caching in UI

Sv: Overvåkningspunkt / Taskoverview in API?

Sv: Overvåkningspunkt / Taskoverview in API?

Sv: Overvåkningspunkt / Taskoverview in API?

Sv: Overvåkningspunkt / Taskoverview in API?

Overvåkningspunkt / Taskoverview in API?

Sv: Field origin ids not defined …

Sv: Bitflag columns

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

Sv: Orderline - description "å"

Orderline - description "å"

Re: Escape wildcard %

Escape wildcard %

Re: Origin of Batch

Sv: Upload document to voucher (again)

Sv: Getting error : Unknown company.

Useful pages

About Visma

Contact us

Follow us