TABLE OF CONTENTS
- Datamining Tiers – Reporting Tiers
- Top-Level Reporting Tier
- Standard Module Reporting Tiers
- Field Visibility & Discovery
- Reporting Tier Options (Primary vs Sub-Tier)
- Application-Specific Options
- History Fields
- Additional (Joined) Reporting Tiers
- Reporting Tiers – Canonical Rules
- Reporting Tiers – Frequently Asked Questions
- Common Support Scenarios
Datamining Tiers – Reporting Tiers
Reporting Tiers add direct, reportable information about module items. This includes standard detail fields, custom form fields, defects, tasks, surveys, attachments, emails, and other related data.
Reporting Tiers also define how module items are linked together in a report. They enable views such as User-to-Application or User-to-Device-to-Application reports.
Top-Level Reporting Tier
Every Datamining Report (DMR) starts with exactly one top-level Reporting Tier.
The top-level tier always corresponds to the module from which the report is launched.
For example, launching a Datamining Report from the Applications grid automatically adds the Applications Reporting Tier as the top-level tier.
Standard Module Reporting Tiers
The top-level Reporting Tier provides access to:
- Standard Detail Fields
- Custom Form Fields
Some default fields are selected automatically.
Standard Reporting Tiers are available for the following modules:
- Applications
- Users
- Devices
- Mailboxes
- Bespoke
- Deployment Units
- Tasks
- Defects
Field Visibility & Discovery
Enable Show Hidden Fields in the Build Report tab to display all available Detail and Custom Form fields.
Two “filter as you type” search boxes allow rapid discovery of fields by name.
Reporting Tier Options (Primary vs Sub-Tier)
Each Reporting Tier includes an options panel, collapsed by default and expandable using the eye icon.
Reporting Tiers are stacked vertically. The first tier is the Primary Tier; all subsequent tiers are Sub-Tiers. Some options are shared, while others are specific to tier type.
Primary Tier Options
- Include Counts of Linked Items
Adds counts of linked module items (for example, linked Users or Devices on an Application report). - Include All Visible Detail Fields
Dynamically includes all visible Detail Fields on each report run. - Include All Visible Custom Form Fields
Dynamically includes all visible Custom Form fields on each report run. Useful for Power BI endpoints and future-proofing saved reports. - Include Last Note / Include Last 5 Notes
Adds a single column containing concatenated note text. The Last 5 Notes are ordered most recent first.
Sub-Tier Options
- Include Dependencies
Adds dependency items even if no direct link exists between the Primary Tier and the Sub-Tier items. - Limit to First-Level Dependencies
Stops dependency expansion after one level. Deeper dependency chains are not traversed. - Resolve via Module
Includes Sub-Tier items via shared links through one or more intermediate modules not present in the report. These items appear as if directly linked. - Include All Visible Detail Fields
Dynamically includes all visible Detail Fields on each report run. - Include All Visible Custom Form Fields
Dynamically includes all visible Custom Form Fields on each report run. - Include Last Note / Include Last 5 Notes
Adds a single column with concatenated note text.
Application-Specific Options
The Applications Reporting Tier includes additional options to:
- Display the original application name (if renamed)
- Display rationalisation information, including source application
History Fields
Enabling Show History Fields in the Build Report tab allows history tracking to be enabled per field and per tier.
Each selected history field adds three columns:
- Previous Value
- Date Changed
- Modified By
Only the most recent historical change is shown. For multi-change history analysis, use a dedicated History Report.
Additional (Joined) Reporting Tiers
Additional Reporting Tiers extend the top-level tier by joining related data. They cannot exist independently.
Each additional tier may introduce one-to-many relationships, resulting in multiple rows per top-level item.
Where possible, ManagementStudio attempts to collapse duplicate link-based rows unless a tier or option explicitly expands them.
Dependencies Reporting Tier
Lists dependencies for each top-level module item. Each dependency is displayed on a separate row.
Common dependency fields can be enabled via checkboxes (such as dependency name, Process, and dependency depth).
To include additional fields (for example, a Device serial number), enter the field’s internal name (such as Devices_SerialNumber) in the Expand Dependency Fields textbox.
Available Fields
True Parent Id, Parent Project Id, Parent Module Id, Parent Instance Id, Project, Module, Item Name, Title, Instance Id, Module Id, Project Id, Process, Sub Process, Process Status, Process Id, Sub Process Id, Process Status Id, Is Locked, Is Archived, Is Deleted, Is Depend Of, Depth, Is Top Level
Contacts Reporting Tier
Lists Contacts linked to the module item. Multiple Contacts appear as separate rows.
Includes standard contact details and an option to include Contact Type (for example, “UAT” or “Application Owner”).
Available Fields
Title, First Name, Last Name, Sam Account, Domain, Organisation, Job Title, Phone Work, Phone Mobile, Email Work, Email Home, Contact Id, Website, Office Site, Address, City, Country, Post Code, Note
Surveys Reporting Tier
Adds Portal Forms (formerly Surveys) to the report, including user responses, completion dates, pass/fail results, and comments.
Survey results can be displayed for all surveys (one row per response), or a specific survey can be selected. Multiple Survey Reporting Tiers may be added to the same report.
Available Fields
Survey Id, Is Enabled, Title, Survey Name, Internal Name, Survey Url, Comments, Fail Reason, Is Locked, Is Locked Date, Is Archived, Test Sign Off Url, Page Visit Count, Page Last Visit Date, Email Statistics
Testing Reporting Tier
Adds test results (such as Application UATs) to the report.
Multiple test results for the same item (for example, repeated UATs) appear as separate rows. Filtering by test type is not currently supported.
Available Fields
Test Result Id, Survey Id, Contact Id, First Name, Last Name, Email, Test Type, Title, Is Global Sign Off, Notes to Tester, Test Window Start, Test Window End, Device Name, Completed By, Complete Results, Complete Date, Comments, Fail Reason, Is Locked, Is Locked Date, Is Archived, Test Sign Off Url, Page Visit Count, Page Last Visit Date, Email Statistics
Attachments Reporting Tier
Displays information about files attached to the module item.
An optional Download Url column can be included to allow direct file downloads, which is useful for portal-exposed reports.
Attachment type filtering is not available in this panel, but can be applied using the Advanced Filter and Sort tab.
Available Fields
Attachment Id, Attachment Type, File Name, Comment, Content Type, File Extension, File Size KB, Download Url, Internal Name, Last Modified Date, Last Modified By
Email Reporting Tier
Displays email activity related to the primary module item.
Email templates must be registered to the module and explicitly selected in the Reporting Tier.
Available Fields
Email Name, Email Category, To Address, CC Address, BCC Address, Template Subject, Email Subject, Last Sent Date, Last Opened Date, Open Count, Send Success
Self Schedule Reporting Tier
Reports on Deployment Unit self-scheduling activity and completion status.
Available Fields
Instance Id, Self Schedule Is Locked, Allow Expired Self Schedule, Is Scheduling Exception, Link Expiry Date, Schedule Url, Page Visit Count, Page Last Visit Date, Request Email Sent, Reminder Email Sent, Complete Email Sent, Update Email Sent, Cancel Email Sent
Reporting Tiers – Canonical Rules
- Every Datamining Report has exactly one top-level Reporting Tier.
- The top-level tier is determined by the module used to launch the report.
- Additional Reporting Tiers must join to a top-level tier.
- Reporting Tiers control data visibility only.
- Reporting Tiers do not affect Readiness calculations.
- Primary and Sub-Tiers have different option sets.
- Include via Module resolves indirect links as direct for reporting.
- Dependencies are additive, not replacing direct links.
- History Fields show only the most recent change.
Reporting Tiers – Frequently Asked Questions
Why do I see multiple rows for the same item?
Additional Reporting Tiers (such as Dependencies, Surveys, or Tests) create one row per linked record. Multiple linked records result in multiple rows.
Why can’t I add a Reporting Tier by itself?
Reporting Tiers must be joined to a top-level module. They cannot exist without a primary module context.
Why don’t I see a field I expect?
The field may be hidden by default. Enable Show Hidden Fields in the Build Report tab to display all available fields.
Why did new Custom Form fields not appear in my saved report?
Unless the option to include all Custom Form Fields is enabled, newly added fields must be manually selected in existing reports.
How do I download attachments from a report?
Enable the Download Url field in the Attachments Reporting Tier to allow direct downloads.
Can I filter attachments by type?
Attachment type filtering is not available in the Reporting Tier panel. Use the Advanced Filter and Sort tab instead.
Do Reporting Tiers affect Readiness?
No. Reporting Tiers only control data visibility. Readiness is calculated exclusively by Readiness Tiers.
Common Support Scenarios
Scenario: My report suddenly has more rows than expected
Check for additional Reporting Tiers that introduce one-to-many relationships, such as Dependencies, Surveys, or Testing tiers.
Scenario: Power BI reports break when new Custom Form fields are added
Enable the option to include all Custom Form Fields so new fields are automatically added to future report outputs.
Scenario: Email data is missing
Confirm that the correct Email Templates are registered to the module and selected in the Email Reporting Tier.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article