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
Building from scratch every time by recreating branding, layouts, links, complex connectors and flows, and more is painful and error-prone. Organizations where developers and makers build and share customized and reusable components and templates get more value from Power Platform. Successful organizations adopt a *fusion teams* model where pro-developers, makers, and admins all work together to deliver the best solutions for their users, and derive the highest value possible from Power Platform.
> - The catalog needs to be set up by an admin before you can use it, including permissions. More information [Administer the catalog](/power-platform/admin/administer-catalog#set-up-the-catalog).
25
21
> - The catalog only works with Microsoft Dataverse environments. Environments without Dataverse aren't supported at this time.
26
-
> -While not required for preview, when this feature is generally available, it'll require the use of Managed Environment capabilities. More information: [Managed Environments overview](/power-platform/admin/managed-environment-overview)
22
+
> -You need a Managed Environment in order to submit solutions to the catalog. However, you can install catalog items from any environment. More information: [Managed Environments overview](/power-platform/admin/managed-environment-overview)
27
23
28
24
In any organization, there might be many components and templates distributed among many environments. The catalog in Power Platform enables developers and makers to:
29
25
@@ -69,7 +65,15 @@ You can submit unmanaged solutions to the catalog for other makers to install an
69
65
- A **template**: A copy of your unmanaged solution that other makers can edit however they choose. Updates to the original unmanaged solution won't update templates, as templates are no longer "connected" to the solution it came from. If you want other makers to have the ability to change the catalog components as they see fit, use a template.
70
66
71
67
> [!NOTE]
72
-
> Currently, certain components aren't supported for use as templates.
68
+
> Currently, certain components aren't supported for use as templates. The supported components for templates are:
69
+
> - Table and its sub components like forms, saved queries, relationships, table maps.
70
+
> - Environment variables.
71
+
> - Canvas apps.
72
+
> - Modern workflows.
73
+
> - Security roles.
74
+
> -`AiModel` and its subcomponents like `AiConfig`.
75
+
> - Web resources.
76
+
> - Power Apps component framework components. This includes modern solution aware components created using the Power Apps component framework. For example custom API, `AiPlugin`, and `AIPlugin` operation.
73
77
74
78
- A **managed item**: Managed items can be updated with more versions as the original solution is updated, but are generally restricted from editing. If you want makers to use your solution *as is* and you also want to keep copies updated with your changes in the future, use a managed item. Managed items are useful for a variety of scenarios for makers:
In any organization, there might be many components and templates distributed among many environments. The catalog in Power Platform enables developers and makers to:
18
16
@@ -21,9 +19,7 @@ In any organization, there might be many components and templates distributed am
21
19
- Get started with templates and components that provide immediate value
> - While not required for preview, when this feature is generally available, it requires the use of Managed Environment capabilities. More information: [Managed Environments overview](/power-platform/admin/managed-environment-overview)
22
+
> You need a Managed Environment in order to submit items to the catalog. You can however install catalog items from any environment. More information: [Managed Environments overview](/power-platform/admin/managed-environment-overview)
27
23
28
24
Before reading this article, you should:
29
25
@@ -168,6 +164,6 @@ As previously mentioned, templates can be acquired as many times as you like, ea
168
164
169
165
### See also
170
166
171
-
[Catalog in Power Platform (Preview)](catalog-overview.md)
172
-
[Administer the catalog (Preview)](/power-platform/admin/administer-catalog)
173
-
[Use the catalog with Power Platform CLI (preview)](/power-platform/developer/submit-catalog-items)
167
+
[Catalog in Power Platform)](catalog-overview.md)
168
+
[Administer the catalog](/power-platform/admin/administer-catalog)
169
+
[Use the catalog with Power Platform CLI](/power-platform/developer/submit-catalog-items)
0 commit comments