Deploy & ALM

Move Logic Fabric projects from development to test and production in a repeatable way with the Logic Fabric CLI.

Application lifecycle management (ALM) is how a change travels from the environment where you build it to the environments where people use it: reliably, every time, with a record of what went where. For Logic Fabric that means moving a project’s Dataverse solution, its logic, processes and APIs, the settings that differ per environment, and the reference data the logic depends on.

The Logic Fabric CLI automates these steps. It runs on a developer machine or in a build pipeline, so a deployment is a script you can review and repeat rather than a checklist of manual imports. A PowerShell module offers most of the same operations as cmdlets.

What moves between environments

Artifact	File	What it holds
Dataverse solution	`<solution>_managed.zip` / `<solution>_unmanaged.zip`	Tables, columns, forms, views and other Dataverse customizations of the project’s solution.
Logic Fabric package	`<project>.flop`	The project’s Logic Fabric artifacts: logic blocks, logic flows, recipes, events, schedules, business processes, APIs, configuration values, service connections and localized resources.
Data map files	`*.datamap.xml`	The values that differ per environment (configuration values, service connections, localized resources and references to records), with the value to use in the target environment.
Data file	`data.xml`	Reference data (records) the logic depends on, such as case types, document templates or approval levels.

A typical release

flowchart TD
  A[Development] -- export --> B[Source control<br/>solution, .flop,<br/>maps, data]
  B -- import with<br/>UAT maps --> C[Test / UAT]
  B -- import with<br/>production maps --> D[Production]

Export the project from development: the package, the solution and, if needed, reference data.
Commit the files to source control, together with one set of data map files per target environment.
Import into test, then production, each time with that environment’s data map files.

Each command prints what it did and ends with exit code 0 on success or 1 on failure, so pipelines stop at the first problem.

Explore

Install the CLIInstall the Logic Fabric CLI and connect it to an environment.ExportExport a project, its solution and reference data.ImportDeploy solutions, packages and data to a target environment.Data mappingSet environment-specific values during deployment.Business dataMove reference data with a data specification.PipelinesAzure DevOps and GitHub Actions examples.Command referenceEvery command and option.PowerShell moduleThe same operations as PowerShell cmdlets.Best practicesHabits that keep deployments boring.