Who is this article for?

Enterprise or Decani users and administrators who want to know about data table search and reporting

No special access or permissions are required.

Native table data reporting is now live in the current EHS+Q Enterprise and Decani UI. Tabular reports support child data in nested and flattened output modes, and child table data is supported in tabular report layouts. See below.

Filters applied to child data fields return only matching child rows. Combined header and table data export is available in Excel (flattened format).

This feature requires migration to the new platform search architecture. See Availability and migration below.

Overview

Availability

With release 2.64.4, child-level data reporting will be made available to new customers, as well as existing customers who have completed the infrastructure migration and are utilizing the redesigned user interface.

Please refer to article on exploring the Phase 1 UI redesign for a comprehensive overview of the UI changes.

Benefits

The platform search architecture upgrade restructures how data is collected, stored and queried, enabling a broader set of future search and reporting enhancements. Customers who migrate are investing in the platform's long-term capability roadmap.

The upgraded architecture is compatible with Ideagen Mazlan, Ideagen's AI-powered agent capability, which will enable users to build reports and dashboards by describing their desired data scope in natural language. Customers migrating now are positioned to take advantage of this when it becomes available.

True child data filtering

Previously, filters on child-level fields returned parent records that matched the filter condition but did not remove non-matching child rows from the output. The new platform search architecture corrects this - child field filters now return only the matching child rows, displayed correctly within the parent context. See Creating a data table report from a search

Note

Supported child relationships depend on your data configuration. Contact your Customer Success Manager or the Support team to confirm which relationships are available in your environment.

Tabular report layouts

Two tabular report layouts are available:

• Nested - Child records appear in sub-tables beneath each parent row, preserving the hierarchical relationship.
  This is best for reviewing parent-to-child relationships; formal reports and presentations.
• Flattened - Each child record appears as its own row in the report. Parent data is repeated on each child row.
  This is best for Excel exports; large-volume data review; analysis across all child records.
• Charts - All supported chart types - table, area, bar, column, or line charts, heatmap, pie, single metric, and treemap - display child data natively. When you add child data to a chart report, it renders automatically using the chart's native display. No additional layout selection is required.
  This is best for executive dashboards and live reporting; visual analysis of child data distributions and trends.

Any of these report types can be added to a dashboard as a live report.

Native reporting upgrades

Customers using Jaspersoft (DevonWay BI) for child data reporting now have access to a native replacement built directly into the reporting tools they already use, with no additional licensing required. Reports appear in the same interface, can be added to live dashboards, and carry the same responsiveness and UI consistency as all other native reports.

Availability and migration

To access this feature, your environment must be migrated to the new platform search architecture. Migration requires no system downtime and is included in your current license at no additional cost.

Search architecture changes

Customers on the current search infrastructure - including on-premise and GovCloud customers - will benefit from a platform search architecture upgrade to access native child data reporting.

Jaspersoft reports

Existing Jaspersoft reports will continue to work after migration. As native reporting is the platform's long-term direction, we will help you plan the transition at a pace that works for your team.

Upgrading to native reporting

Requirements

All new customers will be onboarded to the new upgraded platform search architecture from June 2026. See Exploring the Phase 1 UI redesign for more details.

Existing customers require at least one platform search architecture migration before accessing child data reporting:

• Miramar UI customers will move to a new search index with a new schema.
• Classic UI customers require two sequential migrations:
  • To the new search index with the new schema
  • Classic UI to the new updated platform UI (step 2)

Note

Migration projects from the Classic UI to the new upgraded platform UI are out of scope and managed on a separate track. Contact Product and Sales to initiate this migration.

Keyword search is more precise in the new platform search architecture, producing more accurate results. We recommend testing your key reports after migration.

Getting started

To get started with native child data reporting:

1. Contact your Customer Success Manager to confirm the schedule for your platform search architecture migration or open a service request.
2. Once migrated, start building your first child data report. See Creating a child level data table report from a search