Dear @lubos,
In the past, we should use Custom Reports to query transaction-level data, effectively a full General Ledger Transactions table linked to all other entities (Customers, Suppliers, Payments, Invoices, etc.).
Now, with the shift to Advanced Queries, that functionality has been deprecated. The only comparable dataset seems to be the Transactions table under the Summary page, but this table currently appears isolated: it’s not linked to the rest of the system’s entities and therefore cannot be used for comprehensive analysis.
This creates a significant limitation for anyone trying to generate unified views across the system (for example, linking GL transactions to counterparties, invoice metadata, or any of the new Custom Fields).
In fact, the old Custom Report model is now obsolete and doesn’t even expose these new custom fields, so there’s currently no complete way to query or export transaction-level data with all contextual details.
I would strongly suggest that the “Transactions” source be implemented (or reconnected) as a fully relational structure within Advanced Queries, allowing joins with entities such as Contacts, Payments, Invoices, and Custom Fields.
This would restore the powerful analytical capability that many users previously relied on for reconciliations, auditing, and custom reporting, but using the new, modern Advanced Queries engine.
Thanks
D.