# Treat workbook multiselection exports as unique values, not selected-row counts

> Why can selecting several workbook rows produce fewer exported parameter values?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:28:26+00:00
- Modified: 2026-09-10T01:20:45+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Explainer
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

Why can selecting several workbook rows produce fewer exported parameter values?

## Potentially affected

Azure Monitor workbook query or metric components exporting parameters from multiselection.

## DSE recommendation

Define the downstream parameter as a set of selected field values and test repeated values explicitly.

## Article

## Source facts

Workbook query and metric components can export parameters from selected rows. With multiselection enabled, the exported values form an array containing only unique values; no selection defaults to an empty array. Without multiselection, the component exports only its last selected item. These rules distinguish exported values from the number of rows someone highlighted. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports).

## Applicability

Review the component’s selection mode, field to export, and downstream parameter use. Identify whether two displayed rows can share the same exported field value. Keep this behavior separate from dropdown default persistence: the question here is what row selection passes to another control.

## DSE recommendation

Define the downstream parameter as a set of selected field values and test repeated values explicitly. Have the report owner decide whether the chosen field identifies the intended target or collapses records that need to remain distinct. Make the no-selection experience deliberate rather than silently assuming it means all rows. Review quoting and delimiters when the exported array is inserted into a query.

## Verification

Use a test grid with repeated field values and select several rows spanning both repeated and distinct values. Inspect the exported parameter and resulting downstream scope. Clear the selection, then test the same component with single selection to verify the intended behavior. Preserve the test inputs and parameter output so reviewers can distinguish deduplication by design from missing query results or an unexpected target selection.

## Official references

[Microsoft Learn: Create interactive reports with Azure Monitor Workbooks](https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports). Source reviewed September 9, 2026.

## Primary reference

- Name: Create interactive reports with Azure Monitor Workbooks - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Treat workbook multiselection exports as unique values, not selected-row counts,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.