PowerShellUniversal.Component.Pivot

0.6.0

Pivot report builder for PowerShell Universal apps: readers drag fields into rows, columns, values and filters and get a table or a chart, with date grouping, drill-down to the source rows, templates, undo, Excel, CSV, PNG, SVG and HTML export and the reader's own CSV, JSON and Excel files read in the browser; light and dark theme, English and German, fed straight fro
Pivot report builder for PowerShell Universal apps: readers drag fields into rows, columns, values and filters and get a table or a chart, with date grouping, drill-down to the source rows, templates, undo, Excel, CSV, PNG, SVG and HTML export and the reader's own CSV, JSON and Excel files read in the browser; light and dark theme, English and German, fed straight from SQL DataTables, REST results and PowerShell objects.
Show more

Minimum PowerShell version

7.4

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name PowerShellUniversal.Component.Pivot

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name PowerShellUniversal.Component.Pivot

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

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 Invoke-UDPivotReport

Dependencies

This module has no dependencies.

Release Notes

### Added

- `Invoke-UDPivotReport`: renders a view over rows into an Excel workbook, an HTML report, CSV, JSON
 or SVG without a browser, for endpoints, schedules and jobs. `-Engine Node` runs pivotkit's command
 line on the PSU server (pivotkit-cli 0.2.1 or later; the rows in a temporary folder only this user can
 read, removed afterwards); `-Engine Rest` calls a pivotkit-server's file route with the rows in the
 request (pivotkit's data in the request, source `inline:`), or with `-Source` over a source the
 operator configured. `-Data`, `-Parameter` and `-DataAsOf` need pivotkit-server 0.2.0 or later
 (pivotkit-server 0.1.1 answers `-Data` with `INVALID_INPUT (400)`, and the error then says which
 version `-Data` needs); `-Source` works with pivotkit-server 0.1.1. Input is a view, a view file
 or a layout (`-Layout @{ rows = 'Team'; values = @{ field = 'Hours'; agg = 'sum' } }`); output is a
 file (`-OutFile`) or its bytes. A view with errors throws with pivotkit's findings. Every failure
 has a fixed error id (`PivotServerUnreachable`, `PivotRedirectRefused`, `PivotTokenRefused`,
 `PivotDataTooLarge`, `PivotViewHasErrors`, `PivotServerError`, `PivotCliNotFound`,
 `PivotCliFailed`) with `Status`, `Code`, `RetryAfter`, `Retryable`, `RequestId` and `MaxBytes` in
 the exception's `Data`; a 403 `INSUFFICIENT_SCOPE` is `PivotTokenRefused` and says to ask for the
 REST scope with `-Scope`. An error from the server names its code, detail, findings and request id
 (from the problem document, else the `X-Request-Id` header; a crashed handler's 500 shows its
 `error` text), says when to try again (`Retry-After` in seconds or as a time) or that trying again
 may work (`retryable`), and for a 413 what to do by its code (`BODY_TOO_LARGE`: send less or use
 `-Source`; `LIMIT_EXCEEDED`: make the view smaller or filter). A body over the server's cap ends in
 its 413, also when the server answers while the body is still being sent. A header value outside
 printable ASCII (a token with an umlaut) is refused before anything is sent, naming the header,
 not its value. `-TimeoutSec` limits each REST call as a whole, including sending the body and
 reading the report in full. The rows are written into the request or the data file one by one, a
 DataTable straight from its rows, by a class compiled once per process (100,000 rows x 3 columns:
 0.1 s and about 30 MB instead of seconds and hundreds of MB); `-MaxBytes` (default 10 MiB, the
 server's default cap) stops oversized data before the rest is converted and before anything is
 sent. The Reports page has a section on size and memory. Rows are read by column name (the first
 row's columns), so another property order keeps its columns
 ([#114](https://github.com/eizedev/powershell-universal-components/issues/114),
 [#112](https://github.com/eizedev/powershell-universal-components/issues/112),
 [#129](https://github.com/eizedev/powershell-universal-components/issues/129)).
- Sign-in for `-Engine Rest`: a static token (`-Token`, a PSU secret) or OAuth client credentials
 (`-Credential` with `-TokenUri`, `-Scope`, `-Audience`, `-Resource`), the access token kept per
 runspace (per client, secret hash, scopes and server) until a minute before it expires and fetched
 again once after a 401. https only (http to this machine), no user info in an address, and a
 `-Uri` with a query string or fragment is refused (the routes are appended to its path, so the
 query would be dropped from the request); no redirects followed; the token and the secret appear in no message, `$Error`, verbose or debug output. The new page "Reports
 without a browser" has an Authentik example
 ([#115](https://github.com/eizedev/powershell-universal-components/issues/115)).
- Links from pivotkit: the report opens a view from pivotkit's share format in the address
 (`#pivot-<-Id>=1.<view>`, and `#pivot=1.<view>` without a key), which pivotkit's MCP tool
 `create_link` and REST route `/views/link` make for a source whose `link` is the PSU page and whose
 `linkKey` is the report's `-Id`. A link made for other data (its source id is not the report's
 `-SourceId`) is not loaded; the console says why. The report then writes its own entry in place of
 pivotkit's, so a reload keeps the view. The Views page has the configuration
 ([#116](https://github.com/eizedev/powershell-universal-components/issues/116)).
- `-ExportData`: Export, Source data downloads every row of `-Data` as a CSV or JSON file (pivotkit's
 `exportData`, off by default). `-ExportDataColumn` keeps it, and the drill-down's copies and files,
 to the columns it names; a name that is no column of `-Data` is an error, so a typo never widens the
 export, and the explanation next to Source data names those columns. It is no access control: the
 field list, the drill-down panel and `$EventData.rows` still carry every column, so a column readers
 must not have is removed before `-Data`. The Pivot page has a table of what the exports, the drill-down and Source data hand out
 ([#111](https://github.com/eizedev/powershell-universal-components/issues/111),
 [#113](https://github.com/eizedev/powershell-universal-components/issues/113)).

### Changed

- pivotkit 0.7.0 ([pivotkit-react release](https://github.com/eizedev/pivotkit/releases/tag/pivotkit-react%400.7.0),
 [upgrading from 0.6](https://pivotkit.eize.dev/getting-started/upgrading/#from-0-6-1)):
 pivotkit-core and pivotkit-react 0.7.0, pivotkit-report 0.3.0 and pivotkit-xlsx 0.4.0, all pinned.
- Export, HTML report carries the dark colours of the report's theme too. A reader on a dark screen
 sees the app's dark values (the `--psu-pivot-*` of `.ud-pivot-report [data-pk-theme="dark"]`), or
 PSU's dark greys without them. Paper stays light.
- A colour scale's middle colour on a dark screen is the dark theme's `--psu-pivot-scale-mid`.
 Without one, the cells run between the dark low and high colours.
- Print or save as PDF opens the print dialog in the click itself.
- A second click on a menu's button closes the menu in Safari.
- A field's filter rules show in one column as wide as the menu.

### Fixed

- `-TemplatePath` lists only the view files made for the report's data (`-SourceId`, else `-Id`) and
 those that name no data, as the template stores do; it listed every file for every report. A
 folder that held the views of one report under another id shows them only in that report now
 ([#90](https://github.com/eizedev/powershell-universal-components/issues/90)).
- A shared `-Templates` entry with the name of a store's shared view showed twice in the Views menu;
 the store's view now takes its place, as for `-TemplatePath` files
 ([#91](https://github.com/eizedev/powershell-universal-components/issues/91)).
- A view from a link in the address bar is held to pivotkit's limits for views from outside (at most
 50 filters, 1,000,000 characters) instead of the app's own (128 filters); the tab's own view, kept
 in its sessionStorage, keeps the app's limits after a reload or the light/dark switch
 ([#105](https://github.com/eizedev/powershell-universal-components/issues/105)).

FileList

Version History

Version Downloads Last updated
0.6.0 (current version) 9 11/16/2026
0.5.0 16 11/14/2026
0.4.0 280 11/11/2026
0.3.0 54 11/9/2026
0.2.0 8 11/8/2026
0.1.0 9 11/8/2026
Show more