FlowmageDocs

Browse

BetaReads data

Pulls Twinfield figures out as rows — a trial balance, open items or ledger detail.

Settings

SettingWhat it is
ConnectionRequiredThe Twinfield connection the step signs in with.
Company codeLeave empty to use the company code on the connection.
Report codeRequiredWhich Twinfield report to run. 040_1, 050_1 and 060 also need a regime column. Read browse definition lists them all.
ColumnsWhich fields to ask for, and how to narrow them. Twinfield's own advice: ask per period, and ask only for the columns you need — for example [{"field":"fin.trs.head.code"},{"field":"fin.trs.head.number"},{"field":"fin.trs.line.value"},{"field":"fin.trs.head.yearperiod","operator":"between","from":"2026/01","to":"2026/12"}]
Sort onOne of the field names above.
Direction"ascending" or "descending"
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `twinfield`)
officetext
browseCodetext
columnstext
sortFieldtext
sortOrder"ascending" or "descending", by default "ascending"

Output

FieldType
rowsarray
columnsColumn namesarray
rowCountRows in this answernumber
Sample output, and the expression for each field
  • columns
    • [0]"fin.trs.head.code"
    • [1]"fin.trs.line.value"
  • rowCount1
  • rows
    • [0]
      • fin.trs.head.code"VRK"
      • fin.trs.line.value"121.00"

Errors

When a step of this node stops a run, the run page shows a code. Look it up:

Example step

The step as a flow file holds it. Replace each value in <…>.

{
  "config": {
    "browseCode": "<report code>",
    "columns": "",
    "connection": "<connection id>",
    "office": "",
    "sortField": "",
    "sortOrder": "ascending"
  },
  "label": "Browse",
  "type": "twinfield.browse",
  "version": 1
}