Extract transactions of specific Fortnox general ledger account

Questions
,
1

I am trying to list all available tables in my Invantive Cloud database and create a view to extract transactions for a specific Fortnox-account (2422) for use in Excel.

I now know the correct query is:

select * from DataDictionaryTables@DataDictionary

(with a space between select, *, and from).

Creating a view for general ledger account 2422:

  • I want to create a view that shows all transactions for account 2422, but I am unsure which table to use since TransactionLines does not seem to be available in my database.
  • I have not been able to find a suitable table for transactions in the list of available tables.

Questions:

  1. Is the correct syntax for listing tables in Invantive Cloud always:
select * from DataDictionaryTables@DataDictionary

(with spaces as shown)?

  1. Which table should I use to create a view for all transactions for a specific account (e.g., 2422)?
  • The table TransactionLines is not available in my database.
  • I need guidance on the correct table name and how to write the view.
  1. Are there any permissions or settings I need to adjust to access transaction data or create views?

I have attached screenshots of the error messages and the list of available tables for reference. My goal is to export transaction data for account 2422 to Excel using a view created in Invantive Cloud.

Please provide guidance on the correct SQL syntax for listing tables and creating views, and advise which table to use for transaction data in my Invantive Cloud database.

2

The query to retrieve the available tables seems correct. As an alternative, visit:

To retrieve ledger information, Fortnox uses a different naming structure. They are all named starting with Voucher like VoucherLines.

Please consult for sample:

Please note that Fortnox probably will not perform well when querying these tables and views for a specific general ledger account given Fortnox’s API design.

Invantive intends to add SIE parse support for significantly faster access for such queries. See for more information the parsing of the output SieTransactionFiles described in:

This functionality has no expected delivery date.