Rules Transport Tasks

Move Ascentix Rules Engine rules between Dataverse environments from Azure Pipelines.

• Rules Transport Export (RulesTransportExport@0) writes the published rules of one or more rule sets to a .asxrules.json package.
• Rules Transport Import (RulesTransportImport@0) imports each rule in a package into the target environment and publishes it there, one rule at a time.

Requirements

• The Ascentix Rules Engine solution in both environments. The target must run the same version as the source, or newer.
• Power Platform Build Tools in your organization, for the Power Platform service connection. Client secret and workload identity federation both work.
• The connection's application user holds the Rules Engine Author role in each environment.

Example

steps:
  - task: RulesTransportExport@0
    inputs:
      connection: Contoso-DEV
      ruleSets: Billing
      outputPath: $(Build.ArtifactStagingDirectory)/rules.asxrules.json

  - task: RulesTransportImport@0
    inputs:
      connection: Contoso-PROD
      packagePath: $(Build.ArtifactStagingDirectory)/rules.asxrules.json

Import inputs

Export takes published rules only. Draft and archived rules are skipped with a warning.

Each import attaches a summary to the pipeline run and writes rules-import-report.json and rules-import-report.md next to the package. A rule that fails fails the step. Conflicts and collisions mark it as succeeded with issues.

Documentation

Moving Rules Between Environments covers rule sets, the service connection and the import options in full.