Data Source

A Data Source (DS) in ManagementStudio is a core component used to define complex filters for scoping data.

Data Sources are evaluated at runtime each time they are used and always resolve identically, regardless of whether they are used in Datamining Reports, ESM Plans, Dashboard Widgets, Personas, or via the API.

A Data Source is always tied to a single primary module. This primary module determines the available Processes, Blueprints, and Deployment Units that can be used for filtering.

Data Source Components

Each Data Source is composed of one or more filtering components. By default, filters are combined using OR logic unless explicitly excluded.

All Module Items

Returns the IDs of all items within the selected module (for example, all Applications, Users, or Devices).

This is the most commonly used Data Source option.

By default, archived and deleted items are excluded.

Explicit Module Items

Scopes results to only those items explicitly selected in the grid at the time the Data Source is created.

Example:

If 20 applications are selected in the Applications grid and a Datamining Report is run, the Data Source defaults to Explicit Module Items and includes only those 20 applications.

Explicit Module Items can also be supplied programmatically via the PowerShell API by providing an explicit list of IDs. This behaves the same as items selected in the UI.

When running saved reports or automations:

• Saved reports compare the stored Data Source with the current grid selection. If they differ, the user is prompted to continue with the saved Data Source or generate a new one.
• ESM Plans store their Data Source as part of the plan definition.
• API executions reuse the stored Data Source unless a new one is supplied.

Using Explicit Module Items outside the UI is supported but uncommon and not recommended for most scenarios.

Rationalisation Status (Applications Only)

The Applications module includes a Rationalisation Status filter that is not available in other modules.

By default, only applications with a status of Accepted are in scope, even if this filter is not explicitly configured.

The following statuses can be included:

• Accepted
• Pending
• Rationalised
• Rejected

When multiple Rationalisation Statuses are selected, they are combined using OR logic.

Rationalisation Status can be combined with Process filters. By default, this combination uses OR logic.

A setting unique to Rationalisation Status called Cross Apply forces AND logic.

Example:

An application must be Pending AND in the 2. Discovery Process.

Processes

Allows scoping based on the current Process or Sub Process of an item.

Multiple Processes and Sub Processes can be selected and are combined using OR logic.

Example:

Scope the Data Source to applications that have completed a specific process, or users that are currently migrating.

Process Status

Processes and Sub Processes are associated with a common set of statuses.

Available statuses:

• Inactive
• In Progress
• On Hold
• Ready
• Out of Scope

Process Status applies to the current process only.

When combined with Process filters, Process Status uses OR logic.

Blueprints

Scopes items based on their membership in Blueprints or Blueprint folders.

Selecting a Blueprint folder includes all child Blueprints recursively.

Multiple Blueprints can be selected and are combined using OR logic.

Blueprint filters can be inverted using Exclude Items, allowing subtractive logic.

Example:

All Applications minus those in the London Blueprint.

Deployment Units

Scopes items to specific Deployment Units associated with the primary module.

Deployment Unit associations are direct only. Items can belong to one and only one Deployment Unit.

History Filter

Allows scoping based on historical state over a specified time range.

History filters evaluate both historical and current state if they overlap the selected date range.

Date and time boundaries are inclusive, and time-of-day is respected.

History tracking is always enabled and cannot be disabled.

Example:

Applications that were in UAT last week, or users who completed a survey in the last four weeks.

Datamining Source

Uses the output of another Datamining Report as the basis for the Data Source.

The referenced report is re-run each time the Data Source is evaluated and respects its own Data Source, filters, and tiers.

Duplicate IDs returned by the report are automatically de-duplicated.

The referenced report must output a column containing IDs using the appropriate internal column name (for example, Applications_AppId or Devices_DeviceId).

If the referenced report is modified or deleted, the Data Source may fail and return an error.

Include Archived

Includes archived items in the Data Source.

By default, archived items are excluded.

Include Deleted

Includes items currently in the delete queue.

Deleted items are not physically removed immediately. Once removed, they cannot be recovered or included.

Archived and Deleted states are independent and may coexist.

Exclude Items

Exclude Items removes a set of items from the Data Source after inclusion filters are applied.

Exclude logic converts OR-based inclusion into an effective AND NOT operation.

Example:

Applications in UAT minus those in the VIP Blueprint.

Usage Considerations

Data Sources provide powerful and flexible scoping for analysis, automation, and integration.

For advanced scenarios, combining Process, History, Blueprint, and Datamining Source filters enables highly precise targeting.

Data Source – Canonical Rules

• Data Sources are evaluated at runtime.
• Data Sources always resolve identically across all usage contexts.
• A Data Source is tied to exactly one primary module.
• Filter components are combined using OR logic by default.
• Exclude Items are applied last as a subtractive operation.
• Returned IDs are unique and module-specific.
• Deleted items cannot be recovered once physically removed.

Data Source – Frequently Asked Questions

Why did my Data Source return more items than expected?

By default, Data Source filters are combined using OR logic. Use Exclude Items or Cross Apply (where available) to enforce AND logic.

Why did my Data Source change after reopening a report?

ManagementStudio detects differences between saved Data Sources and current grid selections and prompts the user to confirm which Data Source to use.

Why didn’t my Data Source include archived or deleted items?

Archived and deleted items are excluded by default. Use Include Archived or Include Deleted to include them.

Why did my Datamining Source fail?

Datamining Sources depend on the referenced report. If that report is changed or deleted, the Data Source may fail.

Can a Data Source return items from multiple modules?

No. Each Data Source is scoped to a single primary module.