Flowline 0.21.0
dotnet tool install --global Flowline --version 0.21.0
dotnet new tool-manifest
dotnet tool install --local Flowline --version 0.21.0
#tool dotnet:?package=Flowline&version=0.21.0
nuke :add-package Flowline --version 0.21.0
Flowline
![]()
Flowline is a Dataverse ALM CLI for Dynamics 365 and Power Apps. PAC CLI gives you the primitives, Flowline gives you the workflow.
About ยท ๐ Documentation ยท Changelog
About
A professional Git-based workflow for plugin developers and solution architects, without the overhead of Power Platform Pipelines or managed solutions. clone โ push โ pull โ deploy, from the inner dev loop to production, in one tool.
Where PAC CLI already handles it, Flowline wraps โ it doesn't re-implement. Where PAC has no answer, Flowline fills the gap.
Pipelines are buried steel โ permits, compressors, years to commission. A flowline goes where the pipeline can't.
Familiar with spkl? Flowline is an actively maintained successor inspired by spkl, whose last meaningful updates date back to 2021.
What sets Flowline apart:
- Attribute-driven plugin registration โ decorate your
IPluginclasses with[Step],[Filter],[PreImage],[PostImage], and[CustomApi]; Flowline reads the assembly and handles every Dataverse registration. No Plugin Registration Tool needed. Works with a classic.dllor a NuGet.nupkgpackage (Dependent Assemblies). - Form events and web resource dependencies auto-wired from source โ
// flowline:onload,// flowline:onsave, or// flowline:onchangebinds a function straight to a form's event, closing the last manual step in the JS dev loop;// flowline:dependslinks JS-to-JS and RESX dependencies the same way. Both are registered and kept in sync on everypush. No Maker Portal visits, no manual Configure Event dialogs, or dependency trees. - Orphan cleanup built in โ steps, step images, and web resources missing from source are deleted from Dataverse on every
push.deploycleans up removed code components in unmanaged solutions too, the cleanup you'd otherwise only get from managed (details). No stale registrations, no ghost records. Use--no-deleteto opt out. - Dry-run before you touch anything โ
--dry-runshows exactly what would change before a single Dataverse record is touched. Run it as a CI safety gate or any time you want confidence. No other Dataverse ALM tool offers this. - AI-native by design โ
pullwritesDATAVERSE_CONTEXT.mdwith your full schema (entities, attributes, option sets, forms, views, plugin steps); Copilot and Codex load it automatically via the also scaffoldedAGENTS.md/CLAUDE.mdfile by Flowline. Install Flowline as a Claude Code / Codex plugin (/plugin marketplace add RemyDuijkeren/Flowline) and an agent knows the fullclone โ push โ pull โ deployloop โ and how to migrate off other tools, like spkl โ before you've even cloned a project.
Install
dotnet tool install --global Flowline
Update later with dotnet tool update --global Flowline.
Prerequisites: .NET SDK 10 or later, Git, and PAC CLI.
Authenticate using PAC CLI before using Flowline:
pac auth create --environment https://your-org.crm4.dynamics.com
Quick start (project mode)
# One-time: bootstrap an existing solution into the Git repo
flowline clone ContosoSales --env https://contoso.crm4.dynamics.com
# Daily dev loop
flowline push # push code assets to DEV
flowline pull # pull Dataverse changes back to source
git commit -m "feat: add validation"
# Promote
flowline diff v1.2.0 # what changed since the last release
flowline deploy test
flowline deploy prod
Starting from scratch instead? flowline init <solution-name> creates the publisher and solution in Dataverse, then scaffolds the repo the same way โ see Command Reference.
For full setup, auth, and project workflow: Getting Started
Plugin registration
flowline push inspects your compiled plugin assembly and registers every step, image, and Custom API in Dataverse โ no Plugin Registration Tool, no Maker Portal.
Decorate your IPlugin classes with [Step], [Filter], [PreImage], [PostImage], or [CustomApi] from the source-only Flowline.Attributes package:
<PackageReference Include="Flowline.Attributes" Version="1.0.0" PrivateAssets="all" />
Then you can do:
[Step("account")]
[Filter("creditlimit")]
public class CreditLimitValidationUpdatePlugin : IPlugin
{
public void Execute(IServiceProvider sp)
{
var ctx = (IPluginExecutionContext)sp.GetService(typeof(IPluginExecutionContext));
var target = (Entity)ctx.InputParameters["Target"];
if (target.GetAttributeValue<Money>("creditlimit")?.Value > 100_000)
throw new InvalidPluginExecutionException("Credit limit cannot exceed 100,000.");
}
}
Already have a built assembly? Push it standalone, no cloned project needed:
flowline push plugins --path ./bin/Release/Plugins.dll --solution-name ContosoSales --env https://contoso-dev.crm4.dynamics.com
Flowline.Attributes reference ยท Push Plugins and Custom APIs wiki
Web resources
flowline push syncs your local web resource files straight to Dataverse โ no Maker Portal upload, no manually created web resource records.
Point it at a build output folder, and it creates, updates, and removes web resources to match, standalone, no cloned project needed:
flowline push webresources --path ./dist --solution-name ContosoSales --env https://contoso-dev.crm4.dynamics.com
Beyond the sync itself, Flowline reads // flowline:... comment annotations straight out of your built files and uses them to auto-wire Dataverse metadata that would otherwise mean a Maker Portal visit:
// flowline:onload,// flowline:onsave, or// flowline:onchangebinds a function to a form's event โ Flowline registers (and keeps in sync) the Form Event Handler and its Form Library entry, closing the last manual step in the JS dev loop.// flowline:dependslinks JS-to-JS and RESX dependencies, registered automatically on everypush.
// flowline:onload account "Account Main"
export function onLoad(executionContext) { ... }
// flowline:onchange account "Account Main" creditlimit
export function onChangeCreditlimit(executionContext) { ... }
Commands
| Command | What it does |
|---|---|
clone [solution-name] |
Bootstrap an existing solution from Dataverse into the repo; run with no solution to pick one interactively |
init [solution-name] |
Create a new publisher + empty solution in Dataverse (greenfield), then scaffold the repo; run with no name to be prompted |
push |
Build and sync code assets to DEV; push plugins or push webresources for one target, or standalone with --path |
pull |
Pull the current solution state from DEV into source control |
deploy <target> |
Pack from the repo and import into test, uat, prod, or a URL; or deploy a pre-built zip standalone with --path |
provision [dev\|test\|uat] |
Provision a DEV, TEST or UAT environment by copying from production |
generate |
Generate early-bound C# types into Plugins/Models/ (configurable with --output) |
drift <target> |
Compare committed source, or a pre-built zip with --path, against a live environment; read-only. Exits 0 unless --exit-code is passed. Use diff for the git-history axis |
diff [from] [to] |
Report which solution components changed between two git refs (positional, or a range like A..B); no Dataverse connection, no auth, no network. The git-axis counterpart to drift |
settings <operation> |
Read or change one environment's configuration. apply sets the environment from a settings file and capture writes one from it; toggle switches one component on or off and set sets one value or binding, without touching the file |
scaffold <webresources\|plugins> |
Write a project template into this folder and add it to the nearest solution file. No Dataverse, no auth, no network. Alias: new |
status |
Show environment info, Flowline version, and PAC CLI status |
sln add <path> |
Add a .cdsproj to the solution file โ dotnet sln add refuses those. Runs standalone |
Documentation
Full docs live on the Wiki. Using an AI agent? See AI Agents for the exit-code contract and how to install Flowline as a Claude Code / Codex plugin.
Coming from another tool? Migration from spkl ยท Migration from Daxif ยท Migration from ALM Accelerator ยท Migration from PACX
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.21.0 | 103 | 11/9/2026 |
| 0.20.0 | 151 | 9/19/2026 |
| 0.19.0 | 131 | 9/13/2026 |
| 0.18.0 | 150 | 8/26/2026 |
| 0.17.0 | 235 | 8/16/2026 |
| 0.16.0 | 137 | 8/7/2026 |
| 0.15.0 | 149 | 8/3/2026 |
| 0.14.0 | 145 | 7/31/2026 |
| 0.13.0 | 132 | 7/24/2026 |
| 0.12.0 | 146 | 7/17/2026 |
| 0.11.0 | 156 | 7/15/2026 |
| 0.10.0 | 159 | 7/12/2026 |
| 0.9.0 | 158 | 7/5/2026 |
| 0.8.0 | 159 | 6/29/2026 |
| 0.7.0 | 157 | 6/21/2026 |
| 0.6.0 | 167 | 6/5/2026 |
| 0.5.0 | 163 | 5/29/2026 |
| 0.4.0 | 169 | 5/7/2026 |
| 0.3.0 | 144 | 5/5/2026 |
| 0.2.0 | 170 | 4/19/2026 |