fontName and fontStyle have been made available for formElement and all the other tables (systeminformation, window, workspace, etc.) where a font size column was already available. query read_forms($cid: Int!) { useCustomer(no :$cid) { formElement { items { fontSize fontName fontStyle fontStyleFlags } } } } mutation write_forms($cid: Int!) { useCustomer(no: $cid) { formElement_create(values:[{ fontStyleFlags:[Bold,Italic,Underline,StrikeThrough] fontSize : 14, fontName : "Consolas" }]) { affectedRows } } } This will become available in the next release (tomorrow). ... View more

Working on a fix. For a query like: query read_orders($cid : Int!) { useCompany(no : $cid) { order(first: 10) { items { orderNo orderDate customerNo supplierNo employeeNo joinup_Associate_via_Customer { customerNo supplierNo employeeNo name } joinup_Associate_via_Supplier { customerNo supplierNo employeeNo name } joinup_Associate_via_Employee { customerNo supplierNo employeeNo name } } } } } The results will be as follows:   { "data": { "useCompany": { "order": { "items": [ { "orderNo": 1, "orderDate": 20210212, "customerNo": 10002, "supplierNo": 51004, "employeeNo": 0, "joinup_Associate_via_Customer": { "customerNo": 10002, "supplierNo": 0, "employeeNo": 0, "name": "Me AS" }, "joinup_Associate_via_Supplier": { "customerNo": 0, "supplierNo": 51004, "employeeNo": 0, "name": "Abc AS" }, "joinup_Associate_via_Employee": null }, { "orderNo": 2, "orderDate": 20130203, "customerNo": 0, "supplierNo": 0, "employeeNo": 0, "joinup_Associate_via_Customer": null, "joinup_Associate_via_Supplier": null, "joinup_Associate_via_Employee": null }, { "orderNo": 3, "orderDate": 20130401, "customerNo": 10004, "supplierNo": 0, "employeeNo": 0, "joinup_Associate_via_Customer": { "customerNo": 10004, "supplierNo": 0, "employeeNo": 0, "name": "You AS" }, "joinup_Associate_via_Supplier": null, "joinup_Associate_via_Employee": null },   ... View more

This is now available. See https://docs.business.visma.net/docs/schema/queries/modelinfo#language-selection   ... View more

We released a fix for this problem today (https://docs.business.visma.net/docs/releasenotes). We will be correcting the data that was stored base64 encoded instead of binary. ... View more