Datex Studio CLI · Release notes

dxs 0.5.6

See which columns are indexed before you filter on them, and keep your report-canvas preferences across reloads.

Released Sep 8, 2026 Previous 0.5.5 Merged PRs 5
Schema

Inspect database indexes

New commands show key-column order and included columns for every physical index.

Reports

Canvas preferences that stick

Sample Data panel, preview mode and margins survive a reload.

Schema discovery

  • Database-index inspectionNew#228

    New dxs schema indexes and dxs schema describe-index commands expose physical index metadata, including key-column order and included columns. Listings filter by entity set and column. Entity descriptions, schema batches and the Studio explorer also surface index information.

    This needs a Footprint server that exposes index metadata. Other servers keep normal schema discovery and return a clear diagnostic for index-only commands. Missing metadata is reported separately from evidence that a column is unindexed.

Reports

  • Persistent report-canvas preferencesFix#253

    The Sample Data panel state, Preview/Expressions mode and margin visibility survive reloads. Sample-data changes respect an explicit mode choice. Zoom still fits the page automatically.

Sign-in and onboarding

  • Initialization keeps Footprint client credentialsFix#252

    Interactive dxs init --client-id … --client-secret … signs in before saving credentials to the identity. When credentials cannot be persisted, initialization returns an actionable error instead of reporting success while discarding them.

Datex staff tooling

Datex

Needs a Datex staff identity. Nothing here changes anything for customers.
  • Branch work-item managementNew#247

    dxs source branch workitem assign, list, update and unassign manage links to Azure DevOps work items, Dynamics support cases and Dynamics Requirements. branch create accepts --workitem. Readers recognize all three sources, and release-note enrichment handles the platform's renamed organization field and mixed-source links.

Behind the scenes

  • More reliable release publishingTooling#249

    The release workflow pushes the version commit and tag atomically, retries competing updates to main, and checks version reuse and agreement before tagging. Production promotion's rebase recovery was also corrected.

Before you upgrade

What might need a change on your side

  • Headless initialization scripts. Establish a cached identity before attaching Footprint client credentials. A standalone DXS_ACCESS_TOKEN does not provide the persistent identity they are saved to.

Source record

Compiled from the 5 pull requests merged to main between v0.5.5 and v0.5.6, assigned by tag ancestry. Deploy-pin and version-bump commits are omitted. Dates use America/New_York. The 0.5.6 release workflow, wheel and source distribution were verified on PyPI at publication.

PyPI package