PowerShellUniversal.Component.Pivot
0.5.0
Minimum PowerShell version
7.4
Installation Options
Owners
Copyright
(c) 2026 eizedev. MIT License.
Package Details
Author(s)
- eizedev
Tags
PowerShellUniversal UniversalDashboard PSU Pivot PivotTable Report Dashboard Excel Visualization
Functions
New-UDPivotReport New-UDPivotReportPlaceholder ConvertFrom-UDPivotView ConvertFrom-UDPivotViewFile ConvertTo-UDPivotViewFile New-UDPivotFileTemplateStore New-UDPivotTemplateStore Invoke-UDPivotTemplateRequest Get-UDPivotSqlColumnDescription
Dependencies
This module has no dependencies.
Release Notes
### Security
- pivotkit-xlsx 0.3.1: a crafted Excel workbook could pass the size checks before parsing and fill
the reader's browser memory (denial of service in the reader's own tab;
[GHSA-c6vh-q36c-92r3](https://github.com/eizedev/pivotkit/security/advisories/GHSA-c6vh-q36c-92r3),
pivotkit-xlsx 0.3.0 and earlier, so release 0.4.0 of this module with `-AllowImport`; update from
0.4.0). Workbooks with namespace-prefixed elements are checked like the others. Also, a workbook's
different texts and cell formats count against `importCells` while they are unpacked.
### Added
- `-ImportLimit`: pivotkit's limits for a file loaded with `-AllowImport` per report, e.g.
`@{ fileBytes = 250MB; rows = 2000000 }` (`fileBytes`, `rows`, `columns`, `importCells`,
`textLength`, `archiveEntries`, `unpackedBytes`; keys left out keep pivotkit's defaults). They go to
pivotkit-react's `importLimits`, so the app's `-Data` keeps pivotkit's own limits. An unknown key or
a value that is not a whole number of at least 1 is an error that names it
([#103](https://github.com/eizedev/powershell-universal-components/issues/103),
[#106](https://github.com/eizedev/powershell-universal-components/issues/106)).
### Changed
- pivotkit 0.6.1 ([pivotkit-react release](https://github.com/eizedev/pivotkit/releases/tag/pivotkit-react%400.6.1),
[upgrading from 0.4](https://pivotkit.eize.dev/getting-started/upgrading/)): pivotkit-core and
pivotkit-react 0.6.1, pivotkit-xlsx 0.3.1 and pivotkit-report 0.2.1, all pinned and in the one
bundle (1.58 MB, 494 KB gzip). Export's table as CSV is called **Table as CSV (.csv)**; pivotkit's
Source data export stays off (`-ExportData` follows,
[#113](https://github.com/eizedev/powershell-universal-components/issues/113)). A view saved in the
browser for a sheet of a loaded workbook opens on that sheet again. Dates before 1 AD carry their era
("Q1 2 BC"). Export has an HTML report, the chart as SVG and Print or save as PDF; Excel, the HTML
report and print are light also from a dark app. Column subtotals are off unless a view turns them on
(`totals = @{ colSubtotals = $true }`); views the report saves name all four totals. The chart's
text is 14 px, the font weights are four (`--psu-pivot-weight-*`). `-Tips` knows the tip
`colSubtotals`. The filter menus write view version 2 (below).
- A colour scale without colours of its own runs from light to strong blue, the heatmap's colours,
on screen and in the Excel export, not from red over yellow to green: it says "more", not "good" or
"bad". `--psu-pivot-scale-low` and `--psu-pivot-scale-high` fall back to `--psu-pivot-heat-low` and
`--psu-pivot-heat-high`; `--psu-pivot-scale-mid` adds a middle colour. The Themes page shows how to
get red, yellow and green back
([#107](https://github.com/eizedev/powershell-universal-components/issues/107)).
- Themes: the corporate stylesheet sets each mode for the page and for the theme the report shows
(`:root, .ud-pivot-report [data-pk-theme="light"]` and `:root[data-theme="dark"],
.ud-pivot-report [data-pk-theme="dark"]`), so the Excel export and the HTML report of a dark app take
the light values and a report pinned with `-Theme` takes those of its own theme. A stylesheet with
`:root[data-theme="dark"]` alone still themes the screen, but its dark values reach those files.
- New theme properties: `--psu-pivot-input-border` and `--psu-pivot-rule` (the edge of a text field and
the line between a menu's groups, PSU's neutral greys instead of pivotkit's blue-grey) and
`--psu-pivot-weight-normal`, `-medium`, `-strong` and `-bold`. The admin panel of `-AdminRole` takes
the report's corners, weights and text size (at least 14 px; its code was 13 px).
- pivotkit's view version 2 ([pivotkit#165](https://github.com/eizedev/pivotkit/issues/165)): every
filter is `{ field, type, ..., not, blanks }` with the types `in`, `blank`, `text`, `compare`,
`relative`, `top` and `value`. Views of version 1 (`include`, `exclude`, `label`, the operators
`!=`, `notBetween`, `notEquals`, `notContains`) in `-View`, `-SavedView`, `-Templates`, view files,
template stores and links still load with the same result: the report migrates them. The report
writes version 2, so `-OnViewChange`, `Get-UDElement` and saved views carry it.
- View files: `ConvertFrom-UDPivotViewFile`, `-TemplatePath` and the template stores read format
versions 1 and 2 and views of version 1 and 2; a newer one is still refused.
`ConvertTo-UDPivotViewFile` and the stores write format version 2 with
`https://pivotkit.eize.dev/schema/view-file-2.json` for a view of version 2, and format version 1
with `view-file-1.json` for a view of version 1 or without a version, so stored views of version 1
stay readable by older releases.
- The shipped view "Open work per team" and the showcase's "Lead time per customer" are views of
version 2. Docs: the Views page has a section on filters (types, `not`, `blanks`, version 1).
FileList
- PowerShellUniversal.Component.Pivot.nuspec
- index.2316bc902259368d1ef2.bundle.js
- PowerShellUniversal.Component.Pivot.psd1
- index.2316bc902259368d1ef2.bundle.js.LICENSE.txt
- Private\Register-PSUComponentAsset.ps1
- CHANGELOG.md
- README.md
- THIRD-PARTY-NOTICES.txt
- Private\SHARED.txt
- import-worker.d63a2a5bc5bba3ac2e2d.js
- LICENSE
- Private\ConvertTo-PSUComponentData.ps1
- PowerShellUniversal.Component.Pivot.psm1