Datamining Tiers - Blueprint Columns

TABLE OF CONTENTS

• Datamining Tiers – Blueprint Columns
• What Are Blueprints?
• How to Add Blueprint Columns
• Blueprint Column Configuration Options
  • Name
  • Module
  • All on One Line
  • Trim to Last X Folders and Blueprint
  • Extract Nth Folder from the Tree
  • Blueprint Selection
• Example Configuration
• Blueprint Columns – Canonical Rules
• Blueprint Columns – Frequently Asked Questions
  • Why do I see multiple rows for the same item?
  • Why are some Blueprint memberships missing?
  • Why is the Blueprint path very long?
  • Why does the column show a folder name instead of a Blueprint?
  • Can I show both User and Application Blueprints in the same report?
  • Do Blueprint Columns affect Readiness or calculations?
• Common Support Scenarios
  • Scenario: My report row count increased after adding a Blueprint Column
  • Scenario: I need a single geographic value per item
  • Scenario: I need multiple Blueprint perspectives in one report

Datamining Tiers – Blueprint Columns

The Blueprint Columns Tier allows Blueprint membership related to a module item to be added to a Datamining Report.

Blueprint Columns can be configured to include specific subsets of the Blueprint tree (for example, all Blueprints under a Location branch). Results can be displayed either as multiple Blueprint values in a single cell or expanded so that each Blueprint membership appears as a separate row. This supports advanced grouping, filtering, and pivoting scenarios.

What Are Blueprints?

Blueprints in ManagementStudio provide a structured way to organise related items within a project using a folder-style tree hierarchy.

Blueprints can contain items from multiple modules, including:

• Users
• Applications
• Devices
• Mailboxes
• Bespoke Items
• Deployment Units

Unlike traditional folder structures, a single module item can belong to multiple Blueprints at the same time.

For example, an Application might belong to multiple Blueprints such as Finance, Marketing, London, and Problem Apps.

How to Add Blueprint Columns

To add Blueprint Columns to a report:

1. Click Add Blueprint Columns in the ribbon menu.
2. In the Blueprint Columns panel, click Add Blueprint Column.
3. A Blueprint Column configuration panel is added to the report.

The Add Blueprint Column button can be clicked multiple times to add multiple Blueprint Columns to the same report.

Blueprint Column Configuration Options

Name

The display name of the column as shown in the report.

When adding multiple Blueprint Columns, each column name should be unique.

Module

Specifies which module’s Blueprint memberships are resolved for this column.

This is typically the top-level module of the report, but it does not have to be. For example, in a User-to-Application report, you can add:

• Blueprints the User belongs to
• Blueprints the Application belongs to

All on One Line

Controls how multiple Blueprint memberships are displayed.

• When enabled, all matching Blueprints are displayed as a list in a single cell.
• When disabled, the report expands to one row per Blueprint membership for each item.

Trim to Last X Folders and Blueprint

Blueprint paths can be deep, resulting in long folder paths.

This option trims the Blueprint path from the left and displays only the Blueprint name plus the specified number of parent folders.

For example, you can display only the Blueprint name and its immediate parent folder.

Extract Nth Folder from the Tree

In some cases, the folder structure is more important than the Blueprint itself.

This option extracts a specific parent folder from the Blueprint path based on its depth in the Blueprint tree.

A common use case is when folders represent geographic regions and Blueprints represent cities or sites. This option allows higher-level geographic data to be extracted as a single reportable value.

Blueprint Selection

Use the Add Blueprint dropdown to specify which branch of the Blueprint tree should be resolved for this column.

Because items may belong to many Blueprints for different purposes (for example, Department, Location, Deployment Ring, VIP, or Early Adopters), each Blueprint Column should be scoped to a specific branch.

Example Configuration

You might add two Blueprint Columns to the same report:

• One column scoped to the Department branch
• Another column scoped to the Location branch

This flattens a User’s hierarchical Blueprint memberships into two simple, reportable columns suitable for filtering, grouping, and export.

Blueprint Columns – Canonical Rules

• Blueprint Columns report Blueprint membership only; they do not modify Blueprint assignments.
• A single module item may belong to multiple Blueprints simultaneously.
• Blueprint Columns can be added multiple times to the same report.
• Each Blueprint Column resolves membership independently.
• Row expansion occurs only when All on One Line is disabled.
• Blueprint filtering is limited to the selected branch of the Blueprint tree.

Blueprint Columns – Frequently Asked Questions

Why do I see multiple rows for the same item?

If All on One Line is disabled and an item belongs to multiple Blueprints within the selected branch, the report expands to one row per Blueprint membership.

Why are some Blueprint memberships missing?

Only Blueprints within the selected branch are included. Memberships outside that branch are intentionally excluded.

Why is the Blueprint path very long?

Blueprint paths reflect the full folder hierarchy. Use Trim to Last X Folders to shorten the displayed path.

Why does the column show a folder name instead of a Blueprint?

If Extract Nth Folder is enabled, the column displays the selected parent folder from the Blueprint path rather than the Blueprint name.

Can I show both User and Application Blueprints in the same report?

Yes. Add multiple Blueprint Columns and configure each column to resolve Blueprints for a different module.

Do Blueprint Columns affect Readiness or calculations?

No. Blueprint Columns are purely informational and do not affect Readiness, filters, or calculations.

Common Support Scenarios

Scenario: My report row count increased after adding a Blueprint Column

Check whether All on One Line is disabled. Disabling this option causes row expansion for each Blueprint membership.

Scenario: I need a single geographic value per item

Use Extract Nth Folder to extract the appropriate level of the Blueprint folder hierarchy.

Scenario: I need multiple Blueprint perspectives in one report

Add multiple Blueprint Columns, each scoped to a different Blueprint branch (such as Department, Location, or Deployment Ring).