Export Operations

The export command extracts artifacts from a Dataverse environment for version control and deployment.

Export Command Syntax

flowon-dynamics export [options]

Options:
  -c,  --connectionstring <string>   Connection string for Dynamics 365 (required)
  -p,  --project-name <name>         Logic Fabric project to export (required)
  -o,  --output-directory <path>     Output directory (required, created if missing)
  -sm, --solution-managed            Also export the managed Dynamics 365 solution (default: false)
  -su, --solution-unmanaged          Also export the unmanaged Dynamics 365 solution (default: false)
  -ds, --data-spec-file-path <path>  Path to a data specification file (optional)
  -l,  --log-level <level>           None | Info | Verbose (default: None)

Package is always exported

Running export always produces the Flowon package (<ProjectName>.flop). The -sm/-su switches additionally export the associated Dynamics 365 solution in managed and/or unmanaged form. Business data is exported only when --data-spec-file-path is supplied.

Export Outputs

Solution Files

artifacts/
├── solutions/
│   ├── CustomerPortal_1.0.0.0_managed.zip
│   └── CustomerPortal_1.0.0.0_unmanaged.zip

Flowon Package (.flop)

The .flop file is a comprehensive package containing all Logic Fabric artifacts:

artifacts/
├── flowon/
│   └── CustomerPortal.flop

Contents of .flop file:

Component	Description
Logic Blocks	Reusable logic components
Flows	Flow definitions and configurations
Processes	Process definitions
APIs	Logic API configurations
Events	Event subscriptions and handlers
Service Connections	External service configurations
Recipes	Logic Recipe definitions

Configuration and Data

artifacts/
├── data/
│   ├── moj_documenttype.xml
│   ├── moj_statusreason.xml
│   └── moj_notificationtemplate.xml
├── mappings/
│   ├── configuration.datamap.xml
│   ├── entity.datamap.xml
│   ├── localizedresources.datamap.xml
│   └── serviceconnection.datamap.xml

Export Examples

Export the Flowon package with the managed and unmanaged solution:

flowon-dynamics export \
  --connectionstring "$CONNECTION_STRING" \
  --project-name "CustomerPortal" \
  --output-directory "./artifacts" \
  --solution-managed \
  --solution-unmanaged

Export with business data:

flowon-dynamics export \
  --connectionstring "$CONNECTION_STRING" \
  --project-name "CustomerPortal" \
  --output-directory "./artifacts" \
  --data-spec-file-path "./specs/data-spec.xml"

.flop Package Contents

The Flowon Package (.flop) is an extracted archive containing all Logic Fabric artifacts organized by category:

CustomerPortal.flop/
│
├── Api/                                    # API Configurations
│   ├── flwn_api/                          # API definitions
│   │   └── [api-guid]/
│   │       └── data.xml
│   └── flwn_apiversion/                   # API versions
│       └── [version-guid]/
│           └── data.xml
│
├── Logic/                                  # Logic Components
│   ├── flwn_configuration/                # Configuration settings
│   ├── flwn_eventdefinition/              # Event definitions
│   ├── flwn_eventhandler/                 # Event handlers
│   ├── flwn_localizedresource/            # Localized strings
│   ├── flwn_logicblock/                   # Logic Block definitions
│   ├── flwn_logicflow/                    # Logic Flow definitions
│   ├── flwn_logicrecipe/                  # Logic Recipe definitions
│   ├── flwn_schedule/                     # Scheduled jobs
│   └── flwn_serviceconnection/            # External service connections
│
├── Mappings/                               # Data Mapping Files
│   ├── configuration.datamap.xml
│   ├── entity.datamap.xml
│   ├── localizedresources.datamap.xml
│   └── serviceconnection.datamap.xml
│
├── Process/                                # Logic Process Orchestrator Components
│   ├── flwn_businessprocess/              # Business process definitions
│   └── flwn_businessprocessversion/       # Process versions
│
└── manifest.xml                            # Package manifest

Package Categories

Category	Folder	Contents
Api	`/Api`	Logic API definitions and versions
Logic	`/Logic`	Logic Blocks, Flows, Recipes, Events, Schedules, Service Connections
Mappings	`/Mappings`	Environment-specific data mapping files
Process	`/Process`	Logic Process Orchestrator Business Processes and versions

Entity Types in .flop

Entity	Description
`flwn_api`	API definition records
`flwn_apiversion`	API version records
`flwn_configuration`	Configuration key-value pairs
`flwn_eventdefinition`	Custom event definitions
`flwn_eventhandler`	Event handler subscriptions
`flwn_localizedresource`	Multi-language text resources
`flwn_logicblock`	Logic Block definitions
`flwn_logicflow`	Logic Flow definitions
`flwn_logicrecipe`	Logic Recipe definitions
`flwn_schedule`	Scheduled job definitions
`flwn_serviceconnection`	External service connection configs
`flwn_businessprocess`	Logic Process Orchestrator process definitions
`flwn_businessprocessversion`	Logic Process Orchestrator process versions

manifest.xml

The manifest file contains package metadata:

<?xml version="1.0" encoding="utf-8"?>
<Manifest>
  <ProjectName>CustomerPortal</ProjectName>
  <SolutionName>Customer Portal</SolutionName>
  <SolutionUniqueName>customerportal</SolutionUniqueName>
  <SolutionPrefix>crm</SolutionPrefix>
  <Title>Customer Portal</Title>
  <Description>Customer self-service portal project.</Description>
</Manifest>

The manifest records the project's identity and its associated Dynamics 365 solution. ProjectName, SolutionName, SolutionUniqueName, and SolutionPrefix are always written; Title and Description are optional and come from the project's metadata.

Export Command Syntax​

Export Outputs​

Solution Files​

Flowon Package (.flop)​

Configuration and Data​

Export Examples​

.flop Package Contents​

Package Categories​

Entity Types in .flop​

manifest.xml​