TALXIS.CLI 1.7.0

TALXIS CLI (txc)

TALXIS CLI (txc) is a modular, extensible .NET global tool for Power Platform and Dataverse development. It's built around a code-first philosophy: scaffold and manage components locally in your repo — fast, offline and coding agent-friendly — then synchronize to a live environment.

This makes txc ideal for coding agents and CI/CD pipelines where hitting a live environment on every operation is too slow and too fragile. Work locally, build, sync.

Table of Contents

• Installation
• Identity, Connections & Profiles
• Example Usage
• Local Development & Debugging
• Versioning & Release
• Collaboration

Detailed guides: Schema Management · Changeset Staging · Architecture · Profiles & Auth · Output Contract

Installation

Install the CLI as a .NET global tool:

dotnet tool install --global TALXIS.CLI

Update to the latest version:

dotnet tool update --global TALXIS.CLI

dotnet new update

After installation, use the CLI via the txc command in any terminal.

Identity, Connections & Profiles

txc decouples who you are (credentials) from where you target (connections) and exposes the combination as a named profile. Every command that touches a live environment takes exactly one context flag — --profile <name>.

Quickstart for most developers:

txc config profile create --url https://contoso.crm4.dynamics.com/

Drop in the Dataverse environment URL, sign in in the browser, and txc creates and selects the profile for you.

For explicit credential / connection / profile steps, repository pinning, or headless / CI setup, see docs/profiles-and-authentication.md.

Example Usage

txc commands fall into two layers:

The recommended workflow: Use txc workspace to create and modify components locally (entities, attributes, solution structures), then deploy to the environment with txc env. This is dramatically faster than round-tripping every change through a live org — especially for coding agents that make dozens of changes per session.

The environment layer is organised into three planes:

Workspace — Local-First Development

The fastest way to build Dataverse components. Everything happens locally in your repo — no environment round-trips, no publish waits. Ideal for coding agents that need to scaffold dozens of components in a session.

# Explore available component types and their parameters
txc workspace component type list
txc workspace component explain pp-entity

# Scaffold a Dataverse entity — instant, local, no environment needed
txc workspace component create pp-entity \
  --param Behavior=New \
  --param PublisherPrefix=tom \
  --param LogicalName=location \
  --param DisplayName=Location \
  --param DisplayNamePlural=Locations

# When ready, deploy the solution to a live environment
txc env sln import ./out/MySolution_managed.zip

The environment commands below assume you have an active profile (see above). Pass --profile <name> to override for a single call.

Control Plane

Manage environment-level settings exposed by the Power Platform admin API — feature toggles, Copilot flags, IP restrictions, and more.

List environment management settings:

txc env setting list --filter powerApps

Enable Power Apps Code Apps:

txc env setting update --name powerApps_AllowCodeApps --value true

Application Plane

Deploy, inspect, and manage solutions and packages in the target environment.

# Deploy a package straight from NuGet, inspect the result
txc env pkg import TALXIS.Controls.FileExplorer.Package
txc env deploy show --package-name TALXIS.Controls.FileExplorer.Package

# Import a solution, target a different environment for one call
txc env sln import ./Solutions/MySolution_managed.zip --profile customer-b-prod

# Uninstall a package cleanly
txc env pkg uninstall TALXIS.Controls.FileExplorer.Package --yes

Data Plane

Query, create, update, and bulk-operate on Dataverse records — all cross-platform on modern .NET.

Three query languages — pick the one you think in:

# OData — familiar, filterable, composable
txc env data query odata accounts --select "name,revenue" --filter "revenue gt 1000000" --top 10

# FetchXML — full aggregation, linked entities, fiscal date filters
txc env data query fetchxml '<fetch top="5"><entity name="contact"><attribute name="fullname"/></entity></fetch>'

# T-SQL — because sometimes you just want SELECT ... WHERE
txc env data query sql "SELECT fullname, emailaddress1 FROM contact WHERE statecode = 0" --top 20

Record CRUD, file columns, relationships, bulk:

txc env data record create --entity account --data '{"name":"Contoso Ltd","revenue":5000000}' --apply
txc env data record upload-file --entity account $ID --column logo --file ./logo.png --apply
txc env data record associate $ID --entity account \
  --target $TARGET_ID --target-entity contact --relationship accountleads_association --apply
txc env data bulk upsert --entity contact --file ./contacts.json   # CreateMultiple/UpsertMultiple under the hood

Configuration Migration Tool (CMT) — import, export, convert. Runs natively on macOS/Linux (no Windows VM needed). Exports to a folder by default so you can commit data directly to your repo:

# Export → folder → edit → import round-trip
txc data pkg export --schema ./data_schema.xml --output ./data-package --export-files
txc data pkg import ./data-package

# Advanced tuning options not exposed by PAC CLI or CMT GUI:
txc data pkg import ./data-package \
  --batch-mode                  # ExecuteMultiple batching (vs one-by-one) \
  --batch-size 500              # records per batch (default: 200) \
  --connection-count 4          # parallel service channels \
  --override-safety-checks      # skip duplicate detection \
  --prefetch-limit 100          # pre-cache record lookups

txc data pkg convert --input export.xlsx --output data.xml

See docs/configuration-migration.md for the full deep-dive into CMT internals, deduplication logic, and tuning strategies.

Application Plane — Schema Management

Define your Dataverse schema from the terminal — entities, columns, relationships, option sets. Every mutating command supports --apply (execute now) or --stage (queue for batch). See docs/schema-management.md.

# Spin up a new entity with a money column in seconds
txc env entity create --name tom_project \
  --display-name "Project" --plural-name "Projects" \
  --ownership user --apply

txc env entity attribute create --entity tom_project \
  --name tom_budget --type money --display-name "Budget" --apply

# Or stage everything and apply in one optimised batch
txc env entity create --name tom_invoice \
  --display-name "Invoice" --plural-name "Invoices" --stage
txc env entity attribute create --entity tom_invoice \
  --name tom_amount --type money --display-name "Amount" --stage
txc env entity attribute create --entity tom_invoice \
  --name tom_duedate --type datetime --display-name "Due Date" --stage

txc env changeset status          # review what's queued
txc env changeset apply --strategy batch   # one batch, one publish

Changeset staging batches entity creation via the CreateEntities SDK action and consolidates all publishes into a single PublishXml call — dramatically faster than sequential operations. See docs/changeset-staging.md.

Local Development & Debugging

Clone the repository and restore dependencies:

git clone <repo-url>
cd tools-cli
dotnet restore

Build the solution:

dotnet build

Run the CLI directly:

dotnet run --project src/TALXIS.CLI -- workspace explain

Versioning & Release

• Versioning is managed in Directory.Build.props (Microsoft-style versioning).
• Releases are published to NuGet.org via GitHub Actions.

Collaboration

We welcome collaboration! For feedback, suggestions, or contributions, please submit issues or pull requests.

For onboarding or customization, contact us at hello@networg.com.