{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
        "slug": "dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/"
        },
        "title": "Treat workbook multiselection exports as unique values, not selected-row counts",
        "summary": "Why can selecting several workbook rows produce fewer exported parameter values?",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:28:26+00:00",
        "modified_at": "2026-09-10T01:20:45+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 246,
        "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.",
        "primary_source": {
            "name": "Create interactive reports with Azure Monitor Workbooks - Azure Monitor | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Review the component&#8217;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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Create interactive reports with Azure Monitor Workbooks</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nWorkbook 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.\nApplicability\nReview 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.\nDSE recommendation\nDefine 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.\nVerification\nUse 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.\nOfficial references\nMicrosoft Learn: Create interactive reports with Azure Monitor Workbooks. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nWorkbook 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).\n\n## Applicability\n\nReview 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.\n\n## DSE recommendation\n\nDefine 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.\n\n## Verification\n\nUse 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.\n\n## Official references\n\n[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."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Treat workbook multiselection exports as unique values, not selected-row counts",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/",
                "headline": "Treat workbook multiselection exports as unique values, not selected-row counts",
                "description": "Why can selecting several workbook rows produce fewer exported parameter values?",
                "abstract": "Why can selecting several workbook rows produce fewer exported parameter values?",
                "articleBody": "Source facts\nWorkbook 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.\nApplicability\nReview 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.\nDSE recommendation\nDefine 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.\nVerification\nUse 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.\nOfficial references\nMicrosoft Learn: Create interactive reports with Azure Monitor Workbooks. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:28:26+00:00",
                "dateModified": "2026-09-10T01:20:45+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-210-treat-workbook-multiselection-exports-as-unique-values-not-selected-row-counts/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Treat workbook multiselection exports as unique values, not selected-row counts"
                },
                "articleSection": [
                    "IT"
                ],
                "keywords": [
                    "IT",
                    "Explainer",
                    "Information priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 246,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Create interactive reports with Azure Monitor Workbooks - Azure Monitor | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/workbooks-interactive-reports"
                }
            }
        ]
    }
}