What is the challenge? |
Views allow users to pull related data into tables that can be customised, analysed, and exported, making them a key tool for operational analysis and in‑app reporting. Users often invest significant time designing views that reflect agreed business logic by combining filters, relationships, and object data.
However, once a view is created, its logic cannot be reused directly as a query.
This creates a gap because queries serve a different but closely related purpose:
Queries are designed to retrieve specific datasets in a machine‑readable format
They are intended for BI tools, analytics platforms, and external reporting
Query outputs are structured to support many‑to‑many relationships between objects (e.g. audits ↔ risks ↔ issues ↔ controls)
Today, users must manually recreate view logic when building a query, translating visual, user‑friendly configurations into technical query definitions. This is particularly challenging where views include multiple related objects and complex relationships.
|
What is the impact? |
Inefficient transition from analysis to BI reporting Users analyse data in Views, then may have to rebuild the same logic again to extract data for BI tools (e.g. Power BI), slowing delivery of insights.
-
High risk of inconsistency Manually recreating logic can lead to differences between:
What is shown and exported from a View
What is returned by a Query and consumed in BI reports This is especially problematic with many‑to‑many relationships, where small differences in logic can significantly change results.
Reduced confidence in data integrity When views and queries do not align, users lose confidence that external reporting accurately reflects in‑system analysis.
Limited reuse of agreed business logic Views that have been reviewed, validated, and relied upon by the business cannot easily become a reusable, governed data source for downstream reporting and integrations.
This has a material impact on Internal Audit, Risk, and Compliance teams who depend on consistent, defensible datasets for executive, board, and regulatory reporting.
|
Describe your idea |
Introduce the ability to create a query directly from an existing view, automatically translating the view’s logic into a structured, machine‑readable query suitable for BI and analytics use cases.
Proposed capability:
From a saved view, users can select “Create query from view”
The system converts the view’s filters, logic, and object relationships into a query definition
-
The generated query:
Preserves how data is structured to support many‑to‑many relationships
Produces outputs suitable for BI tools and external analytics
Can be edited, saved, and reused independently of the view
-
The query can then be used for:
BI integrations (e.g. Power BI)
Structured reporting and analytics
Data exports and automation scenarios
Optionally, the query indicates it was generated from a specific view to support traceability and governance
This enables customers to:
Analyse data visually in Views
Seamlessly progress from analysis to BI‑ready datasets
Reuse trusted business logic without rework
Maintain consistency across in‑app reporting, exports, and external analytics
|
Extend functionality to Custom Reports - e.g. Introduce the ability to create a custom report module directly from an existing view