BladeFX Documentation

Reports → Open report → Report Code

The Report Code tab is used to define all data logic of the report.

Important design rule:

All grouping, sorting, filtering, limits, and calculations must be defined here.

The Report Designer does not change data logic – it only controls visual layout.

Visit section Tables to learn more about tables in report code.

The Report Code tab is used to define all data logic of the report.

Important design rule:

All grouping, sorting, filtering, limits, and calculations must be defined here.

The Report Designer does not change data logic – it only controls visual layou

Each report can consist of one or more tables.

To add a new table:

1. Open the Report Code tab.
2. Click the ➕ Add new table option.
3. A new table (e.g. New table 1) will be created.
4. The query editor will become active for this table.

Each table represents one result set rendered in the report.

Each table has its own configuration.

Available fields

• Name*
• Logical name of the table (shown in designer and internal references).
• Sort position*
• Defines the order in which tables are processed and displayed.
• Connection*
• Connection used to execute the query / API.
• Check column list
• Optional validation list to ensure expected columns exist in result set.

Table options

• ☑ Is active
• Enables or disables the table.
• ☑ Can be empty
• Allows the table to return zero rows without causing an error.
• ⛔ Connection locked
• Forces the table to always use the selected connection.
• ⚙️ SetRepParams
• Enables parameter binding between report parameters and query execution.

The Report Code editor is where all business logic and data retrieval logic is defined.

Depending on the selected table data source, the code can be:

• SQL (for relational databases)
• ODBC-based queries (for non-SQL or proprietary systems)
• API request definitions (for external services)

You can define:

• Data retrieval logic
• Query or request definition used to fetch data from the source
• Joins between data entities
• Using SQL joins, ODBC-supported joins, or structured API responses
• Aggregations
• Calculations such as totals, counts, averages, and derived metrics
• (e.g. , , , or source-specific equivalents)
• Grouping
• Logical grouping of data at source level
• (e.g. or API-side grouping mechanisms)
• Sorting
• Definition of result ordering
• (e.g. or source-specific sorting rules)
• Filtering
• Restricting datasets using conditions
• (e.g. , filters, or API parameters)
• Result size control
• Limiting returned data
• (e.g. , pagination, or API limits)
• Advanced logic
• Complex data shaping such as unions, subqueries, derived datasets, or multi-step API calls

Example use cases:

• Top N entities (products, customers, orders)
• Sales or performance summaries
• Aggregated KPIs and metrics
• Drilldown-compatible datasets
• Combined datasets from multiple systems

Important rule

All data logic belongs in Report Code, regardless of data source.

The Report Designer is pixel-perfect only and does not modify logic, grouping, or calculations.

A single report can contain multiple tables, for example:

• Main dataset
• Totals / summary row
• Auxiliary lookup table

Tables are:

• Executed independently
• Ordered by Sort position
• Available individually in the Report Designer

The Report Code editor provides several tools:

• 💾 Save – saves current report code
• ▶ Execute / Test – runs the SQL query
• 🔍 Search – find text in SQL editor
• ⛶ Fullscreen – expand editor to full screen
• ❗ Info – show available editor commands
• ✏ Edit / Parameters test – test parameter values

• Report Code = logic layer
• Report Designer = pixel-perfect layout
• SQL defines what data is returned
• Designer defines how data is shown