Projects

A project is the container for your logic. Every logic block, logic flow, recipe, event definition, event handler, schedule, service connection, configuration and localized resource belongs to exactly one project, and so do business processes and Logic APIs. Each project is linked to a Dataverse solution, and you move a project between environments as one unit.

Organize projects around a business capability, such as “Sales Pricing” or “Case Management”, rather than around artifact types. Logic in one project can still use blocks and flows from another.

Create a project

1. In the Logic Fabric Logic Composer app, go to SettingsProjectsNew.
2. Enter a Project Name, for example Sales Pricing.
3. Choose the Solution the project belongs to. A new project offers only unmanaged solutions.
4. Optionally, on the Docs tab, add a Title and Description that explain what the project is for.
5. Save.

Settings

Setting	What it does	Notes
Project Name	Identifies the project.	Required. Letters, numbers, spaces, hyphens and underscores only.
Solution	The Dataverse solution the project belongs to.	Required. A new project lists only visible, unmanaged top-level solutions.
Title, Description (Docs tab)	Documentation for the project.	Optional.

How it behaves

• Artifacts stay in their project. You choose the Project when you create an artifact. After the first save the field is fixed, so moving an artifact to another project means recreating it.
• Managed means read-only. When the project’s solution is managed, which is typical in test and production after a managed import, the editors and fields of its artifacts open read-only. Change the logic in development and deploy it again.
• Recipes need an unmanaged solution. You cannot create a recipe in a project whose solution is managed.
• Projects with content cannot be deleted. While any artifact still belongs to a project (a block, flow, recipe, configuration, localized resource, service connection, schedule, event definition, event handler, business process or Logic API), Dataverse refuses to delete the project. Delete its content first. See Dependencies.

Move a project between environments

You export and import projects with the Logic Fabric CLI or its PowerShell commands, not from a button in the app. The project is exported as a package that you can keep in source control and import into another environment. See Export and Import.

Example

Your sales team needs discount and approval logic for quotes.

1. Create an unmanaged solution ContosoSales in development.
2. Create the project Sales Pricing and choose ContosoSales as its Solution.
3. Build the Quote Discount decision table, the Quote Ready For Approval validation set and the Submit Quote flow in that project, with a recipe on the Quote table that runs them.
4. Export the project with the CLI and import it into test as managed. There the logic is read-only, so it cannot drift from what you built in development.

Related

• Working in Composer
• Dependencies
• Deploy & ALM