Deploy & ALM

Install the Logic Fabric CLI

Install the Logic Fabric CLI as a .NET tool, connect it to a Dataverse environment, and check that it works.

The Logic Fabric CLI is a command-line tool named flowon-dynamics. You install it once on your machine, or at the start of every pipeline run, and then call its commands with a connection string for the environment you want to work with.

Before you begin

.NET 10 SDK on the machine or build agent (the CLI is installed as a .NET tool).
Access to the environment: a Dataverse user or application user that can export and import solutions and read and write the Logic Fabric project, typically one with the System Customizer or System Administrator security role. For pipelines, use an application user (app registration with a client secret or certificate) rather than a person’s account.
Logic Fabric installed in each environment you export from or import to.

Install the tool:

dotnet tool install --global Flowon.Xrm.Tools.CommandLine

Check that it runs:

flowon-dynamics --help
flowon-dynamics --version

To update later:

dotnet tool update --global Flowon.Xrm.Tools.CommandLine

A local tool pins the CLI version in your repository, so every developer and pipeline uses the same one.

In the repository root, create a tool manifest once and add the tool:
Terminal window
```
dotnet new tool-manifest
dotnet tool install Flowon.Xrm.Tools.CommandLine
```
Commit the generated .config/dotnet-tools.json.
On any machine or build agent, restore and run it:
Terminal window
```
dotnet tool restore
dotnet tool run flowon-dynamics --help
```

Connect to an environment

Every command that works with an environment takes --connectionstring (-c): a standard Dataverse connection string. For pipelines, use an app registration:

AuthType=ClientSecret;Url=https://contoso.crm.dynamics.com;ClientId=<app id>;ClientSecret=<secret>

Dynamics 365 CE on-premisesConnecting to Dynamics 365 CE on-premisesApplies to the other edition

The CLI works the same way against an on-premises organization. Use the connection string type that matches how your deployment signs users in, for example Active Directory:

AuthType=AD;Url=https://crm.contoso.local/Contoso;Domain=CONTOSO;Username=svc-deploy;Password=<password>

For an internet-facing deployment, use AuthType=IFD with the organization’s external address. Use a dedicated service account that has the Logic Fabric security roles in the target organization.

Keep connection strings in your pipeline’s secret store or an environment variable, never in source control:

export DEV_CONNECTION="AuthType=ClientSecret;Url=https://contoso-dev.crm.dynamics.com;ClientId=...;ClientSecret=..."
flowon-dynamics projects -c "$DEV_CONNECTION"

projects lists the Logic Fabric projects in the environment with their solutions. It’s a quick way to check the connection and to find the exact project name the other commands need.

Output, logging and exit codes

Every command prints its outcome, for example Exported project 'Contoso Service' to './out/Contoso_Service.flop' in 42 seconds.
Problems the CLI can detect up front, such as an unreachable environment, a missing file or an unknown project, are reported before anything runs.
Failures show a short reason, not a stack trace. Run the command again with --log-level verbose for full details.
The exit code is 0 on success and 1 on failure.

`--log-level`	Output
`none` (default)	Errors only, plus the outcome line.
`info`	Progress messages.
`verbose`	Diagnostic details, including full error details.