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
1. Numeric with arithmetic expressions (for example, `Filter(table, field + 10 > 100)` ) aren't delegable. Language and TimeZone aren't delegable.
77
80
@@ -81,20 +84,14 @@ Dataverse for processing (rather than processing locally within Power Apps).
81
84
3. DateTime is delegable except for DateTime functions Now() and
82
85
Today().
83
86
84
-
4. Supports comparisons. For example, Filter(TableName, MyCol = Blank()).
87
+
4. Supports comparisons. For example, `Filter(TableName, MyCol = Blank())`.
85
88
86
89
5. The aggregate functions are limited to a collection of 50,000 rows. If
87
-
needed, use the Filter function to select 50,000 rows from a larger set
88
-
before using the aggregate function.
90
+
needed, use the Filter function to select 50,000
89
91
90
-
> [!NOTE]
91
-
> Choices, Guids, and Aggregate functions for Dataverse are supported only with
92
-
the new version of the connector. Depending on the version of Power Apps that
93
-
you're using, enable this connector with either the **Preview** switch titled **Relational data, choices, and other new features for Dataverse** or **Experimental** switch **Use the Dataverse connector**. To find these switches, select **Settings** > **Upcoming features** > **Preview** or **Experimental**.
92
+
6. CountRows on Dataverse uses a cached value. For non-cached values where the record count is expected to be under 50,000 records, use `CountIf(table, True)`.
94
93
95
-
## Dataverse and the improved data source experience
96
-
97
-
If you created a canvas app with a Microsoft Dataverse connector prior to November 2019, then you might not have the benefit of the most current version of the Dataverse. Read [Dataverse connection improvements](../use-native-cds-connector.md) for more details and to upgrade your connection.
94
+
7. For CountRows, ensure that users have appropriate permissions to get totals for the table.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/create-edit-powerbi-report-dataset-components.md
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: paulinbar
5
5
manager: kfollis
6
6
ms.component: cds
7
7
ms.topic: how-to
8
-
ms.date: 09/16/2022
8
+
ms.date: 09/21/2022
9
9
ms.subservice: dataverse-maker
10
10
ms.author: painbar
11
11
search.audienceType:
@@ -38,15 +38,17 @@ In this article, you'll learn how to do the following tasks:
38
38
39
39
## General limitations and restrictions
40
40
41
-
* The **Power BI Extensions (Preview)** system solution must be installed. It is installed in new environments by default. Existing environments must install it manually from PPAC before importing solutions and creating Power BI components. To install the extension, go to the [Power Platform admin center](https://aka.ms/powerbi_extension).
42
-
*Connection references to Power BI data sources aren't supported.
43
-
*Only datasets created with the enhanced dataset model are supported. Paginated reports aren't supported.
41
+
* The **Power BI Extensions (Preview)** system solution must be installed. In new environments it's installed by default. Existing environments must install it manually from PPAC before importing solutions and creating Power BI components. To install the extension, go to the [Power Platform admin center](https://aka.ms/powerbi_extension).
42
+
*Only Power BI reports and datasets can be added to a solution. Only datasets created with the enhanced dataset model are supported. Any other artifact type is not supported (such as dashboard, dataflow, and paginated report).
43
+
*Connection references to Power BI data sources aren't supported (for example, in composite models).
44
44
* The Power BI dataset parameter types "Any" and "Binary" aren't supported in the Power BI integration with Power Apps solutions.
45
45
* Sharing Power BI reports and datasets can only be done from Power BI (sharing the model driven app doesn't share the embedded report).
46
46
* Recovery from workspace deletion isn't supported. Once the dedicated environment workspace has been deleted, you won't be able to add/import any Power BI component to the Power Apps environment.
47
47
* Power Apps Application IDs aren't supported during public preview.
48
48
* The Power Apps environment and the Power BI workspaces all need to be in the same geography. For more information, see [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#cross-geo-operations).
49
-
* Environment life cycle operations aren't supported during public preview. More information: [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#environment-life-cycle-operations).
49
+
* Environment life cycle operations aren't supported during preview. More information: [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#environment-life-cycle-operations).
50
+
* Dataverse for Teams environments are not supported.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/important-changes-deprecations.md
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
title: Important upcoming changes and deprecations in Power Apps portals
3
3
description: Learn about the important changes, including deprecations, coming soon to Power Apps portals.
4
4
author: sandhangitmsft
5
-
6
5
ms.topic: conceptual
7
6
ms.custom:
8
-
ms.date: 09/09/2022
7
+
ms.date: 09/21/2022
9
8
ms.subservice: portals
10
9
ms.author: sandhan
11
10
ms.reviewer: ndoelman
@@ -37,10 +36,12 @@ At launch, users with the system administrator role along with [service admins](
37
36
38
37
## OAuth 2.0 implicit grant flow within your portal
39
38
40
-
Starting June 2022, [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow will be deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs.
39
+
The [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow is deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs.
41
40
42
41
> [!NOTE]
43
-
> All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
42
+
> - All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
43
+
> - For more information on using a custom certificate, go to [Using a custom certificate](oauth-implicit-grant-flow.md#custom-certificates).
44
+
> - For sample code on using POST calls on the Token endpoint, go to [Token endpoint sample](oauth-implicit-grant-flow.md#token-endpoint-sample).
44
45
45
46
## List OData feed
46
47
@@ -111,4 +112,4 @@ Starting with portals version [9.3.4.x](versions/version-9.3.4.x.md), the follow
111
112
112
113
[Important changes (deprecations) coming in Power Apps, Power Automate, and customer engagement apps](/power-platform/important-changes-coming)
Custom certificates provide another layer of security while using the OAuth 2.0 end point. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below
27
+
Using the default certificate for OAuth 2.0 implicit grant flow is [deprecated](important-changes-deprecations.md#oauth-20-implicit-grant-flow-within-your-portal). You will need to use a custom certificate while using the OAuth 2.0 endpoint. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below:
29
28
30
29
1. Go to [portal settings](manage-existing-portals.md#settings) and select **Site Settings**.
31
30
@@ -161,4 +160,4 @@ This sample is an ASP.NET based project and is used to validate the ID token iss
161
160
This sample shows how you can use the getAuthenticationToken function to fetch an ID token using the Token endpoint in Power Apps portals. The sample can be found here: [Token Endpoint sample](https://github.com/microsoft/PowerApps-Samples/blob/master/portals/TokenEndpoint.js).
0 commit comments