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
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common-data-service/common-issues-resolutions-solution-checker.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,7 @@ If a web-avoid-eval error is reported for a Power Apps component framework code
254
254
255
255
## Web-unsupported-syntax issue for web resources
256
256
257
-
ECMAScript 6 (2015) or later versions are not currently supported for solution checker. When solution checker analyzes JavaScript using ECMAScript 6 or later, a web-supported-syntax issue for the web resource is reported.
257
+
Solution checker supports global variables for ECMAScript 2015 (ES6) and up to ECMAScript 2018 (ES9) syntax. When solution checker analyzes JavaScript using global variables later than ES6, or syntax later than ES9, a web-unsupported-syntax issue for the web resource is reported.
258
258
259
259
## Multiple violations reported for plug-ins and workflow activities based on call scope
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common-data-service/use-powerapps-checker.md
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Solution checker works with unmanaged solutions that can be exported from an env
29
29
30
30
> [!NOTE]
31
31
> - This topic explains how to run solution checker from the Power Apps maker portal. A PowerShell module is also available that you can use to interact directly with the service. The Microsoft.PowerApps.Checker.PowerShell module can be used for analysis of managed and unmanaged solutions for supported versions of on-premises and online environments, or to automate and integrate the service into your build and release pipelines. More information: [Microsoft.PowerApps.Checker.PowerShell Overview](/powershell/powerapps/overview?view=pa-ps-latest#get-started-using-the-microsoftpowerappscheckerpowershell-module)
32
-
> - Solution checker doesn't work with solutions that contain JavaScript using ECMAScript 6 (2015) or later versions. When JavaScript using one of these versions is detected, a JS001 syntax issue for the web resource is reported.
32
+
> - Solution checker supports global variables for ECMAScript 2015 (ES6) and up to ECMAScript 2018 (ES9) syntax. When JavaScript is detected using global variables later than ES6 or syntax later than ES9, a web-unsupported-syntax issue for the web resource is reported.
33
33
34
34
## Enable the solution checker
35
35
The Solution checker is enabled by default in every Common Data Service environment. A **Solution checker** menu item is available when you select an unmanaged solution in the **Solutions** area of Power Apps. If the **Run** option is not available in the **Solution checker** menu, you can enable it by installing the Power Apps checker solution. To install it, follow these steps:
@@ -156,7 +156,6 @@ Here's a summary of each column in the report.
156
156
| Plug-in or workflow activity |[il-avoid-lock-plugin](https://go.microsoft.com/fwlink/?LinkID=398563&error=il-avoid-lock-plugin&client=PAChecker)| Avoid lock of static members in plug-ins. |
157
157
| Plug-in or workflow activity |[meta-avoid-retrievemultiple-annotation](https://go.microsoft.com/fwlink/?LinkID=398563&error=meta-avoid-retrievemultiple-annotation&client=PAChecker)| Avoid registering a plugin on RetrieveMultiple of annotation. |
158
158
|Web Resources |[web-use-async](https://go.microsoft.com/fwlink/?LinkID=398563&error=web-use-async&client=PAChecker&source=featuredocs)| Interact with HTTP and HTTPS resources asynchronously. |
159
-
|Web Resources |[meta-remove-invalid-form-handler](https://go.microsoft.com/fwlink/?LinkID=398563&error=meta-remove-invalid-form-handler&client=PAChecker&source=featuredocs)| Correct or remove invalid Common Data Service form event registrations. |
160
159
|Web Resources |[meta-remove-orphaned-form-element](https://go.microsoft.com/fwlink/?LinkID=398563&error=meta-remove-orphaned-form-element&client=PAChecker&source=featuredocs)| Correct or remove orphaned Common Data Service form event registrations. |
161
160
|Web Resources |[web-avoid-modals](https://go.microsoft.com/fwlink/?LinkID=398563&error=web-avoid-modals&client=PAChecker&source=featuredocs)| Avoid using modal dialogs. |
162
161
|Web Resources |[web-avoid-crm2011-service-odata](https://go.microsoft.com/fwlink/?LinkID=398563&error=web-avoid-crm2011-service-odata&client=PAChecker&source=featuredocs)| Don't target the Microsoft Dynamics CRM 2011 OData 2.0 endpoint. |
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/create-dynamics-portal.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
5
5
ms.service: powerapps
6
6
ms.topic: conceptual
7
7
ms.custom:
8
-
ms.date: 10/07/2019
8
+
ms.date: 07/24/2020
9
9
ms.author: nenandw
10
10
ms.reviewer: tapanm
11
11
---
@@ -14,6 +14,9 @@ ms.reviewer: tapanm
14
14
15
15
If you select an environment that contains model-driven apps in Dynamics 365 (such as Dynamics 365 Sales and Dynamics 365 Customer Service), you can create the portals mentioned in [Portal templates](portal-templates.md).
16
16
17
+
> [!NOTE]
18
+
> - There can be only one portal of each type and for a language created in an environment. For more information, go to [creating additional portals](create-portal.md#create-additional-portals-in-an-environment).
19
+
17
20
1. Sign in to [Power Apps](https://make.powerapps.com).
18
21
19
22
2. Select **Create** on the left pane and enter **portal** in the **Search templates** field to display all Dynamics 365 portal templates.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/create-portal.md
+30-3Lines changed: 30 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
5
5
ms.service: powerapps
6
6
ms.topic: conceptual
7
7
ms.custom:
8
-
ms.date: 02/07/2020
8
+
ms.date: 07/27/2020
9
9
ms.author: nenandw
10
10
ms.reviewer: tapanm
11
11
---
@@ -29,7 +29,8 @@ If you choose to create your portal in an existing environment without portal pr
29
29
Based on the selected environment in Power Apps, you can create a Common Data Service starter portal or a portal in an environment containing model-driven apps in Dynamics 365.
30
30
31
31
> [!NOTE]
32
-
> When you create a portal, a few solutions are installed and sample data is imported.
32
+
> - There can be only one portal of each type and for a language created in an environment. For more information, go to [creating additional portals](#create-additional-portals-in-an-environment).
33
+
> - When you create a portal, a few solutions are installed and sample data is imported.
33
34
34
35
More information on working with environments: [Working with environments and Microsoft Power Apps](https://docs.microsoft.com/powerapps/maker/canvas-apps/working-with-environments)
35
36
@@ -71,14 +72,40 @@ After the portal is provisioned successfully, the status is updated and the port
71
72
To edit the portal in Power Apps portals Studio, see [Edit a portal](manage-existing-portals.md#edit).
72
73
73
74
> [!NOTE]
74
-
> - There can be only one portal of each type and for a language created in an environment.
75
75
> - If you don't have sufficient privileges to provision a portal, an error is displayed. You must have the System Administrator role in Common Data Service to create a portal. You must also have the **Access Mode** set to **Read-Write** under **Client Access License (CAL) Information** in the user record.
76
76
> - If you have purchased an older portal add-on, and want to provision a portal using the add-on, you must go to the **Dynamics 365 Administration Center** page. More information: [Provision a portal using the older portal add-on](provision-portal-add-on.md)
77
77
> - If you have provisioned a portal using the older portal add-on, you can still customize and manage it from [make.powerapps.com](https://make.powerapps.com).
78
78
> - Provisioning portals from [make.powerapps.com](https://make.powerapps.com) does not consume the older portal add-ons. Also, these portals are not listed under the **Applications** tab on the **Dynamics 365 Administration Center** page.
79
79
> - A Common Data Service starter portal cannot be created from the **Dynamics 365 Administration Center** page.
80
80
> - Power Apps portals is not available in the France region.
81
81
82
+
### Create additional portals in an environment
83
+
84
+
An environment can have one portal of each type and for each language. Environments with Common Data Service have [starter portal template](portal-templates.md#environment-with-common-data-service) available. If you already have a starter portal for such an environment, you can't create another starter portal for the same language. Similarly, environments with Dynamics 365 have several [portal templates](portal-templates.md#environment-with-model-driven-apps-in-dynamics-365) available. If you have a portal from one of the templates already created in a language, you can't create a new portal with the same template type and language. New portal must have either a different portal type, or a different language.
85
+
86
+
For example, consider a scenario where you have a Common Data Service environment without the Dynamics 365 Apps. In this environment, you have a portal with *English* language created with the template type of *Starter portal*. You want to create a new portal in this environment.
87
+
88
+
In this scenario, the following table explains which additional portal template and language combination is allowed when creating additional portals:
89
+
90
+
| Template type and language of existing portal | Template type and language of the new portal that you want to create | Allowed |
91
+
| - | - | - |
92
+
|*Starter portal* in English |*Starter portal* in English |✗|
93
+
|*Starter portal* in English |*Starter portal* in French |✓|
94
+
95
+
Similarly, the following table explains the allowed template type and language combination for a portal that can be created if you have a Common Data Service environment with Dynamics 365 Apps. In this example, you have a portal with the template *Portal from blank* created in *English* language. You want to create a new portal in this environment.
96
+
97
+
| Template type and language of existing portal | Template type and language of the new portal that you want to create | Allowed |
98
+
| - | - | - |
99
+
|*Portal from blank* in English |*Portal from blank* in English |✗|
100
+
|*Portal from blank* in English |*Community portal* in English |✓|
101
+
|*Portal from blank* in English |*Portal from blank* in French |✓|
102
+
103
+
When an environment already has a portal of the available template type created, and if the environment doesn't have any additional languages enabled, you'll see this error message: *You have reached the maximum limit of 1 portal(s) on this environment. Please choose another environment or create new environment.*
104
+
105
+

106
+
107
+
For more information about enabling languages in an environment, go to [Enable language for an environment](https://docs.microsoft.com/power-platform/admin/enable-languages#enable-the-language).
108
+
82
109
## Create new environment
83
110
84
111
Follow these steps when you create an environment using the option provided in the **Portal from blank** window.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/provision-portal-add-on.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
5
5
ms.service: powerapps
6
6
ms.topic: conceptual
7
7
ms.custom:
8
-
ms.date: 11/11/2019
8
+
ms.date: 07/24/2020
9
9
ms.author: nenandw
10
10
ms.reviewer: tapanm
11
11
---
@@ -15,7 +15,8 @@ ms.reviewer: tapanm
15
15
If you have purchased an older portal add-on, and want to provision a portal using the add-on, you must go to the **Dynamics 365 Administration Center** page and provision the portal.
16
16
17
17
> [!NOTE]
18
-
> To provision a portal, you must be assigned either System Administrator or System Customizer role of the Common Data Service environment selected for the portal. You must also have the [required permissions](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#required-permissions) to create and register an application in Azure AD. If you don't have the required permissions, contact the Global Administrator to update your permissions or ask the Global Administrator to provision the portal.
18
+
> - To provision a portal, you must be assigned either System Administrator or System Customizer role of the Common Data Service environment selected for the portal. You must also have the [required permissions](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#required-permissions) to create and register an application in Azure AD. If you don't have the required permissions, contact the Global Administrator to update your permissions or ask the Global Administrator to provision the portal.
19
+
> - There can be only one portal of each type and for a language created in an environment. For more information, go to [creating additional portals](create-portal.md#create-additional-portals-in-an-environment).
0 commit comments