You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Add canvas apps and cloud flows to a solution by default (preview)
3
-
description: Learn how to configure an environment to add new canvas apps and cloud flows to a default solution through various methods.
3
+
description: Learn how to configure an environment to add new canvas apps and cloud flows to a solution by default.
4
4
author: ChrisGarty
5
-
ms.topic: conceptual
6
-
ms.custom: canvas
5
+
ms.author: cgarty
7
6
ms.reviewer: angieandrews
8
-
ms.date: 02/27/2023
7
+
ms.topic: conceptual
8
+
ms.custom: canvas, bap-template
9
+
ms.date: 04/04/2023
9
10
ms.subservice: canvas-maker
10
-
ms.author: cgarty
11
11
search.audienceType:
12
12
- maker
13
13
contributors:
@@ -16,99 +16,104 @@ contributors:
16
16
17
17
# Add canvas apps and cloud flows to a solution by default (preview)
18
18
19
-
[This article is pre-release documentation and is subject to change.]
20
-
21
-
You can [create canvas apps from within a solution](add-app-solution.md) or [create a cloud flow in a solution](/power-automate/create-flow-solution) in the solutions section in Power Apps or Power Automate. However, creating canvas apps and cloud flows inside solutions is optional, and requires manual steps.
19
+
[This article is prerelease documentation and is subject to change.]
22
20
23
-
Canvas apps and cloud flows can now be created in a solution by default. For more information about solutions, see [Solutions overview](../data-platform/solutions-overview.md), and [application lifecycle management (ALM) guide](/power-platform/alm/overview-alm).
21
+
You can [create a canvas app in a solution](add-app-solution.md) in Power Apps or [create a cloud flow in a solution](/power-automate/create-flow-solution) in Power Automate. Creating a canvas app or a cloud flow in a solution previously required manual steps. Now you can create them in a solution by default.
24
22
25
-
Canvas apps and cloud flows in a solution are defined in Microsoft Dataverse and are more manageable because of Dataverse capabilities including [connection references](/power-apps/maker/data-platform/create-connection-reference), [environment variables](/power-apps/maker/data-platform/environmentvariables), the [Dataverse API](/power-apps/developer/data-platform/webapi/overview), [role-based security](/power-platform/admin/database-security#environments-with-a-dataverse-database), and solution-based [application lifecycle management (ALM)](/power-platform/alm).
23
+
Because canvas apps and cloud flows in a solution are defined in Microsoft Dataverse, you can use Dataverse capabilities to manage them, including [connection references](/power-apps/maker/data-platform/create-connection-reference), [environment variables](/power-apps/maker/data-platform/environmentvariables), the [Dataverse API](/power-apps/developer/data-platform/webapi/overview), [role-based security](/power-platform/admin/database-security#environments-with-a-dataverse-database), and solution-based [application lifecycle management (ALM)](/power-platform/alm).
> This is a preview feature. [!INCLUDE [cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
30
27
31
28
## Prerequisites
32
29
33
-
- Solutions are stored in Dataverse, so the environment must have a Dataverse database to use this feature. If needed, [add a Dataverse database](/power-platform/admin/create-database).
34
-
-You must have **Write**privilege to [CanvasApp table](../../developer/data-platform/reference/entities/canvasapp.md) to create canvas apps in solutions. To create cloud flows in solutions, the [Environment Maker role](/power-platform/admin/database-security#predefined-security-roles) is recommended because there is a set of table permissions needed. For more information, see [security roles and privileges](/power-platform/admin/security-roles-privileges).
35
-
- A canvas app or cloud flow within a solution must be shared with you before you can view or edit.
30
+
- Solutions are stored in Dataverse, so the environment must have a Dataverse database to use this feature. If yours doesn't, [add a Dataverse database](/power-platform/admin/create-database).
31
+
-To create canvas apps in solutions, you must have **Write**privileges to the [CanvasApp table](../../developer/data-platform/reference/entities/canvasapp.md). To create cloud flows in solutions, you should have the [Environment Maker role](/power-platform/admin/database-security#predefined-security-roles). For more information, see [security roles and privileges](/power-platform/admin/security-roles-privileges).
32
+
- A canvas app or cloud flow in a solution must be shared with you before you can view or edit it.
36
33
37
34
> [!IMPORTANT]
38
-
> Ensure you review the [considerations](#considerations) before enabling canvas apps in solutions by default.
35
+
> Before you enable the creation of canvas apps and cloud flows in solutions by default, review the [considerations](#considerations).
39
36
40
37
## Supported methods
41
38
42
-
There are different methods available to get started while creating canvas app. Canvas apps that are created within solution by default using this feature require the use of some of these entry points. Hence, it becomes important to understand how this feature can be utilized.
43
-
44
-
The following table summarizes which entry points benefit from canvas apps within solution by default.
39
+
Several methods, or entry points, are available for creating canvas apps and cloud flows. The following table summarizes the methods that allow you to create canvas apps in a solution by default.
45
40
46
-
| Method | Available for canvas apps within a solution by default?|
47
-
| - | - |
48
-
|[Canvas apps from Dataverse](data-platform-create-app.md)| Yes |
49
-
|Canvas apps from other data sources, such as [SharePoint](app-from-sharepoint.md), [Excel](get-started-create-from-data.md), [Azure Blob Storage](connections/connection-azure-blob-storage.md), and [others](connections-list.md#popular-connectors)| Yes |
|[Canvas apps from template](get-started-test-drive.md)| No |
52
-
|Canvas apps created by [customizing SharePoint forms](customize-list-form.md)| No |
53
-
|Canvas apps created directly from [Azure portal](https://portal.azure.com) using [Azure SQL Database](app-from-azure-sql-database.md)| No |
41
+
| Method | Available for canvas apps in a solution by default? |
42
+
| ---|--- |
43
+
|[Create a canvas app from Dataverse](data-platform-create-app.md)| Yes |
44
+
|Create a canvas app from other data sources, such as [SharePoint](app-from-sharepoint.md), [Excel](get-started-create-from-data.md), [Azure Blob Storage](connections/connection-azure-blob-storage.md), and [others](connections-list.md#popular-connectors)| Yes |
45
+
|[Create a blank canvas app](create-blank-app.md)</br> **NOTE**: [Power Apps](https://make.powerapps.com) > **Apps** > **New app** > **Canvas** also creates a blank canvas app. | Yes |
46
+
|[Create a canvas app from a template](get-started-test-drive.md)| No |
47
+
|Create a canvas app by [customizing SharePoint forms](customize-list-form.md)| No |
48
+
|Create a canvas app directly from [Azure portal](https://portal.azure.com) using [Azure SQL Database](app-from-azure-sql-database.md)| No |
54
49
55
-
## Supported entry points for cloud flows
50
+
The following table summarizes the methods that allow you to create cloud flows in a solution by default.
56
51
57
-
There are different entry points for creating cloud flows. The following table summarizes which entry points are supported by the switch for create in Dataverse solutions by default.
58
-
59
-
| Entry point | Available for cloud flows within a solution by default? |
60
-
| - | - |
61
-
|[Create a cloud flow from blank in portal](/power-automate/get-started-logic-flow)| Yes |
62
-
|[Create a cloud flow from template in portal](/power-automate/get-started-logic-template)| Yes |
52
+
| Method | Available for cloud flows in a solution by default? |
53
+
| --- | --- |
54
+
|[Create a cloud flow from blank in a portal](/power-automate/get-started-logic-flow)| Yes |
55
+
|[Create a cloud flow from a template in a portal](/power-automate/get-started-logic-template)| Yes |
63
56
| Create a cloud flow from Power Automate Management connector | Yes |
64
57
| Create a cloud flow from PowerShell | Yes |
65
-
| Create a cloud flow from Mobile App| No |
58
+
| Create a cloud flow from the mobile app| No |
66
59
|[Create a cloud flow from OneDrive](/power-automate/onedrive-business-launch-panel)| No |
67
-
|[Create a cloud flow from SharePoint](https://support.microsoft.com/en-us/office/create-a-flow-for-a-list-or-library-a9c3e03b-0654-46af-a254-20252e580d01)| No |
60
+
|[Create a cloud flow from SharePoint](https://support.microsoft.com/office/create-a-flow-for-a-list-or-library-a9c3e03b-0654-46af-a254-20252e580d01)| No |
68
61
| Create a cloud flow from other integration points, such as [the Excel add-in](/business-applications-release-notes/april18/microsoft-flow/build-run-flows-excel)| No |
69
-
| Create a cloud flow from legacy package import | No |
62
+
| Create a cloud flow from a legacy package import | No |
70
63
71
64
> [!IMPORTANT]
72
-
> Unsupported entry points will fail to create any cloud flow until that support is added to create a solution cloud flow with that entry point. Workaround: create using a supported entry point, such as creating directly in the Power Automate portal.
65
+
> Unsupported entry points will fail to create any cloud flow until that support is added to create a solution cloud flow with that entry point. You must first create a cloud flow in a solution using a supported method.
66
+
73
67
74
68
## Enable the feature
75
69
76
-
This feature is disabled by default and must be enabled manually. To enable this feature, go to Power Platform admin center by going to **Environments** > select an environment > **Settings** > **Product** > **Features**, and view the **Create in Dataverse solutions** switches. Toggle on the desired switch: Canvas apps and/or Cloud flows. More information: [Manage feature settings](/power-platform/admin/settings-features)
70
+
This feature is disabled by default. You must enable it before you can use it.
71
+
72
+
1. Sign in to the Power Platform admin center and select an environment.
73
+
1. Go to **Settings** > **Product** > **Features**.
74
+
1. Under **Create new canvas apps and cloud flows in Dataverse solutions (Preview`)**, turn on **Canvas apps** and **Cloud flows** as desired.
[Learn more about managing feature settings](/power-platform/admin/settings-features).
79
77
80
-
## Check canvas apps and cloud flows in solutions
78
+
## View canvas apps and cloud flows in solutions
81
79
82
-
To view canvas app and cloud flow objects inside a solution, use the [solution view](../data-platform/solutions-area.md). Only users that have access to the object added inside a solution can view it in a solution view.
80
+
To view canvas app and cloud flow objects in a solution, use the [solution view](../data-platform/solutions-area.md). You must have access to the object added inside a solution to view it in a solution view.
83
81
84
-
## Export and import via solutions
82
+
## Export and import using solutions
85
83
86
-
Once this feature is enabled, consider using solutions [export](../data-platform/export-solutions.md) and [import](../data-platform/import-update-export-solutions.md) instead of [export and import of canvas app packages](export-import-app.md).
84
+
Once the feature is enabled, consider using solutions [export](../data-platform/export-solutions.md) and [import](../data-platform/import-update-export-solutions.md) instead of [exporting and importing canvas app packages](export-import-app.md).
87
85
88
86
## Considerations
89
87
90
-
- Increase in capacity consumption of Dataverse environment and cost implications due to that increased capacity consumption.
88
+
Take the following considerations into account before you decide to create canvas apps and cloud flows in a solution by default.
91
89
92
-
-Known solution limitations related to canvas apps still apply to canvas apps created within solutions by default.
90
+
-Your Dataverse environment capacity consumption and related cost may increase.
93
91
94
-
-This feature also enables the automatic creation of environment variables when adding data sources for your apps.
92
+
-Known solution limitations related to canvas apps still apply to canvas apps created in solutions by default.
95
93
96
-
-By default, this feature saves all canvas apps to the default solution named **Common Data Services Default Solution** published by **Microsoft Dataverse Default Publisher**. However, we recommend that you use a non-default solution for canvas apps. To learn about adding existing canvas apps to solutions, see [Add an existing canvas app to a solution](add-app-solution.md#add-an-existing-canvas-app-to-a-solution).
94
+
-This feature automatically creates environment variables when you add data sources for your apps.
97
95
98
-
-When you toggle one of the feature switches in the Power Platform admin center, the Dataverse properties `enablecanvasappsinsolutionsbydefault` or `enableFlowsInSolutionByDefault` in the organization table are updated. The values can be reviewed using the following sample ODATA snippet: `[org URI]/api/data/v9.0/organizations`. More information: [Organization table reference](/power-apps/developer/data-platform/reference/entities/organization)
96
+
-By default, this feature saves all canvas apps to the default solution, **Common Data Services Default Solution**, published by **Microsoft Dataverse Default Publisher**. However, we recommend that you save your canvas apps to a different solution. [Learn more about adding existing canvas apps to solutions](add-app-solution.md#add-an-existing-canvas-app-to-a-solution).
99
97
100
-
-If you're planning to change the prefix for the default publisher, or solution for your environment, see [Solution publisher prefix](/power-platform/alm/solution-concepts-alm#solution-publisher-prefix), [Create solution publisher prefix](../data-platform/create-solution.md#create-a-solution-publisher) and [Change solution publisher prefix](../data-platform/create-solution.md#change-a-solution-publisher).
98
+
-When you turn the feature on or off for canvas apps and cloud flows in the Power Platform admin center, the Dataverse properties `enablecanvasappsinsolutionsbydefault` and `enableFlowsInSolutionByDefault` in the organization table are updated. You can view the value of these properties using the following sample ODATA snippet: `[org URI]/api/data/v9.0/organizations`. For more information, see [Organization table reference](/power-apps/developer/data-platform/reference/entities/organization).
101
99
102
-
- Non-solution canvas apps and non-solution cloud flows can be added into a solution to add them into Dataverse, but there is no way to revert back.
100
+
- If you're planning to change the prefix for the default publisher or solution for your environment, see [Solution publisher prefix](/power-platform/alm/solution-concepts-alm#solution-publisher-prefix), [Create solution publisher prefix](../data-platform/create-solution.md#create-a-solution-publisher) and [Change solution publisher prefix](../data-platform/create-solution.md#change-a-solution-publisher).
101
+
102
+
- Non-solution canvas apps and non-solution cloud flows can be added into a solution to add them into Dataverse, but there's no way to revert back.
103
103
104
104
## Known issues
105
105
106
-
- The **Monitor** > **Cloud flow activity** page doesn't currently support solution cloud flows.
106
+
- The **Monitor** > **Cloud flow activity** page doesn't support solution cloud flows.
107
107
108
108
-[Audit log events for cloud flow permissions](/power-platform/admin/logging-power-automate#see-audited-events) that provide visibility into sharing aren't updated for solution cloud flows.
109
109
110
-
- The [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) doesn't return solution cloud flows that haven't previously been turned on (published) since the identifier returned is the Logic Apps ID and unpublished flows don't yet have a Logic Apps ID. This API will be updated later to return all solution cloud flows.
110
+
- The [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) doesn't return solution cloud flows that haven't previously been turned on (published). The identifier returned is the Logic Apps ID, and unpublished flows don't have one. This API will be updated later to return all solution cloud flows.
111
111
112
112
- The [List Flows API](/connectors/flowmanagement/#list-my-flows) doesn't return any solution cloud flows. This will be updated later to return solution cloud flows when the [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) is updated.
0 commit comments