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 ... View more

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 ... View more

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 ... View more

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   ... View more

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    ... View more