About Florian Haase

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.

Florian Haase · ‎08-09-2023

Interesting, same problem... query { useCompany(no: 4655191) { companyChangeLog(filter: { _and :[ {logType :{_eq : 1}}, {tableNo :{_eq : 152}}, {columnNo :{_eq : 4084}}, {_or :[ {changedDate : {_gte : 20230905}}, {_and : [ {changedDate : {_eq : 20230905}}, {changedTime : {_gte : 110}} ]} ]} ] }, sortOrder: {createdDate: DESC _thenBy: {createdTime: DESC}}) { items { logType tableNo columnNo newValue previousValue changedDateTime primaryKey } } } } { "logType": 2, "tableNo": 170, "columnNo": 9575, "newValue": "21", "previousValue": "", "changedDateTime": "2023-09-05T12:08:00", "primaryKey": "(Cap. asset no.) 12950" } But filter on createdDateTime seems to work at least.

Florian Haase · ‎08-09-2023

Can we set this on our christmas-wishes list?

Florian Haase · ‎06-09-2023

Just one idea about that here: The changelog would actually never be changed - is this maybe the root for the problem? I can test to get around this by filtering on createDateTime instead.

Florian Haase · ‎05-09-2023

It seems like that only occurs when the filter does not hit any rows. When both tableno columno logtype and lastchangeddatime filter hit any rows I get the rows with right filtering

Florian Haase · ‎05-09-2023

Hi query { useCompany(no: 4655191) { companyChangeLog(filter: {_and :[ {logType :{_eq : 1}}, {tableNo :{_eq : 152}}, {columnNo :{_eq : 4084}}, { changedDateTime : {_gte: "2023-09-05T01:10:07"}} ]}, sortOrder: {createdDate: DESC _thenBy: {createdTime: DESC}}) { items { logType tableNo columnNo newValue previousValue changedDateTime primaryKey } } } } results in: { "data": { "useCompany": { "companyChangeLog": { "items": [ { "logType": 2, "tableNo": 170, "columnNo": 5703, "newValue": "2031", "previousValue": "0", "changedDateTime": "2023-09-05T12:08:00", "primaryKey": "(Cap. asset no.) 12950" }, { "logType": 2, "tableNo": 170, "columnNo": 9575, "newValue": "21", "previousValue": "", "changedDateTime": "2023-09-05T12:08:00", "primaryKey": "(Cap. asset no.) 12950" } ] } } }, "extensions": { "vbnxt-trace-id": "0000000000000000e4efa4f3e7a6f641" } } It seems like the changeddatetime-filter overrides the other filters. Is there something wrong with my query? When I remove the datetimefilter I get the right tableid and column but I also need the filtering on lastchanged... Florian

Florian Haase · ‎22-08-2023

Hi, I can't get the joinup from orgUnit8 working on the associate by official: query { useCompany(no: 4655191) { orgUnit8(sortOrder: {createdDate: ASC _thenBy: {createdTime: ASC}}) { items { orgUnit8No orgUnit1 name official joinup_Associate_via_Official { employeeNo associateNo name shortName } } } } } Result: "data": { "useCompany": { "orgUnit8": { "items": [ { "orgUnit8No": "A1000", "orgUnit1": 1000, "name": "Avdeling 2", "official": 14179, "joinup_Associate_via_Official": null }, ..... Why is the official on OrgUnit8 14179 but the result of the joinup is null - we have checked the data consistency and all seems okay. Also the UI is working on that. Florian

Florian Haase · ‎09-08-2023

If you try to achive a WHERE EXISTS () clause in GraphQL, I think it is not a part of a standard GraphQL Server implementation, but there are several different solutions on the web how to do this. I wondered about the same thing before... But maybe Marius has some more comments...

Florian Haase · ‎09-08-2023

Yes, its already implemented and working 😀 But still (maybe a silly question due to bad vb knowledge) - what are these notes for?

Florian Haase · ‎09-08-2023

I think I figured that out: The notehandling is a bit confusing. There is a table "memo" which just contains the notes without reference. But on the orderline there is at least a graphql-column with the name MemoNo which references to the memo-table. There is no joindown/joinup-link between these tables but that's the table the UI is using. In the UI these table and the field is not visible, therefore I had a bit problems to find it. In the end this means (not tested yet) that we first have to insert into the note-table, get the running note-number and than update the orderline-table with the MemoNo. I have no idea what this orderline-note table is used for. Florian

Florian Haase · ‎08-08-2023

Hi there, we don't get the notes work. We are testing on orderline notes and the mutation is: mutation { useCompany(no: XXXXXXXX) { orderLineNote_create(values: [{ orderNo: 666 orderLineNo: 4 note: "TB-030298-S01-N002\t01.01.0001\t\t1 stk \t2000 kr\r\nTB-030298-S01-N001\t01.01.0001\t\t1 stk \t2000 kr\r\n" }]) { affectedRows items { orderNo orderLineNo note changedByUser changedDateTime } } } } The API answers perfectly: {"data":{"useCompany":{"orderLineNote_create":{"affectedRows":1,"items":[{"orderNo":666,"orderLineNo":4,"note":"TB-030298-S01-N002\t01.01.0001\t\t1 stk \t2000 kr\r\nTB-030298-S01-N001\t01.01.0001\t\t1 stk \t2000 kr\r\n","changedByUser":"","changedDateTime":"0001-01-01T00:00:00"}]}}},"extensions":{"vbnxt-trace-id":"0000000000000000e1586c71c1d153dd"}} No error so far and all perfect. But the UI does not show that there is a note and we don't know how to get access to this note again:

Florian Haase · ‎03-08-2023

Hi we used to copy some of our predefined UI-windows between or to different customers in Business OnPrem. Doing this by GraphQL would give us some excellent possibilities to do that more efficient and get our standard-windows updated all the time across the customers. But I can't find the right tables in the sys-database for that - it seems like Windows-elements, filters, connections and so on is not used in that way any more, but I don't find the correct tables in GraphQL either. Do you have any tips? Florian

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.

Re: Filters on CompanyChangeLog

Sv: Origin of Batch

Sv: Filters on CompanyChangeLog

Sv: Filters on CompanyChangeLog

Filters on CompanyChangeLog

Joinup on official on OrgUnit / Official

Svar: Filter on _joindown

Sv: Handling of notes

Sv: Handling of notes

Handling of notes

copy windows between customers

Useful pages

About Visma

Contact us

Follow us