Skip to content

Commit 4c0c984

Browse files
authored
Merge branch 'main' into patch-2
2 parents 5826196 + ef9bdc9 commit 4c0c984

File tree

13 files changed

+209
-19
lines changed

13 files changed

+209
-19
lines changed

powerapps-docs/developer/component-framework/overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,10 @@ Developers can bundle all the HTML, CSS, and TypeScript files into a single [sol
4848
- Optimized for performance
4949
- Reusability
5050
- Ability to bundle all files into a single solution file.
51+
- Ability to handle being destroyed and reloaded for performance reasons while preserving state.
5152

5253
## Licensing
53-
<!--note from editor: I stopped here, in case this content is direct from CELA, except I turned "is" into "are" in the first sentence. Also made a couple of changes to the Note.-->
54+
5455
Power Apps component framework licensing requirements are inline with existing connectors and components and are based on the type of data and connections used in your app. More information: [Power Apps pricing](https://powerapps.microsoft.com/pricing/). To align with the licensing requirements, we will be classifying code components into two types:
5556

5657
- Code components that connect to external services or data directly via the user's browser client and not through connectors are considered as premium. When these components are used in an app, the app becomes premium, and end-users are required to have **Power Apps** licenses.

powerapps-docs/developer/data-platform/dataverse-sql-query.md

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,7 @@ You can use the **Analyze in Power BI** option (**Data** > **Tables** > **Analyz
7575

7676
Any operation that attempts to modify data (that is, INSERT, UPDATE) will not work with this read-only SQL data connection. For a detailed list of supported SQL operations on the Dataverse endpoint, see [How Dataverse SQL differs from Transact-SQL](how-dataverse-sql-differs-from-transact-sql.md).
7777

78-
The following Dataverse datatypes are not supported with the SQL connection: `binary`, `image`,
79-
`ntext`, `sql_variant`, `varbinary`, `virtual`, `HierarchyId`, `managedproperty`, `file`, `xml`, `partylist`, `timestamp`, `choices`.
78+
The following Dataverse datatypes are not supported with the SQL connection: `binary`, `image`, `sql_variant`, `varbinary`, `virtual`, `HierarchyId`, `managedproperty`, `file`, `xml`, `partylist`, `timestamp`, `choices`.
8079

8180
> [!TIP]
8281
> `partylist` attributes can instead be queried by joining to the `activityparty` table as shown below.
@@ -100,6 +99,9 @@ Dataverse choice columns are represented as \<choice\>Name and \<choice\>Label i
10099
101100
There is an 80-MB maximum size limit for query results returned from the Dataverse endpoint. Consider using data integration tools such as [Azure Synapse Link for Dataverse](../../maker/data-platform/export-to-data-lake.md) and [dataflows](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) for large data queries that return over 80 MB of data. More information: [Importing and exporting data](../../maker/data-platform/import-export-data.md)
102101
102+
> [!TIP]
103+
> To help keep the size of the returned data within acceptable limits, use as few multi-line text columns and choice columns as possible.
104+
103105
Dates returned in query results are formatted as Universal Time Coordinated (UTC). Previously, dates were returned in local time.
104106
105107
Querying data using SQL does not trigger any plug-ins registered on the <xref:Microsoft.Xrm.Sdk.Messages.RetrieveMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.RetrieveRequest> messages. Any rewriting of the query or results that would normally be performed by such a plug-in will therefore not take effect for a SQL query.
@@ -141,9 +143,16 @@ A blocked port error may look something like the following.
141143
142144
![Error message.](media/TDS-SQL-blocked-port-error.png)
143145
144-
The solution is to verify the TCP ports 1433 or 5558 from the client are unblocked. One possible method to do that is described below.
146+
The solution is to verify the TCP ports 1433 or 5558 from the client are unblocked. Use one of the following methods to do that is described below.
147+
148+
#### Use PowerShell to validate connection with TDS endpoint
149+
150+
1. Open a PowerShell command window.
151+
2. Run the Test-connection command. <br> `Test-NetConnection -ComputerName <environment>.crm.dynamics.com -port 1433`
152+
153+
If the connection is successful a line "TcpTestSucceeded : True" will be returned.
145154
146-
#### Establish a telnet session to the TDS service listener
155+
#### Establish a telnet session to the TDS endpoint
147156
148157
1. On a Microsoft Windows computer, install/enable telnet.
149158
1. Choose **Start**.
@@ -156,7 +165,7 @@ The solution is to verify the TCP ports 1433 or 5558 from the client are unblock
156165
157166
If the connection is successful, you will be in an active telnet session. If unsuccessful, you will receive the error:
158167
159-
“Connecting to <environmentname>.crm.dynamics.com… Could not open connection to the host, on port 1433: connect failed”.
168+
“Connecting to \<environmentname>.crm.dynamics.com… Could not open connection to the host, on port 1433: connect failed”.
160169
161170
This means the port has been blocked at the client.
162171

powerapps-docs/developer/data-platform/how-dataverse-sql-differs-from-transact-sql.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,7 @@ search.app:
1717
- D365CE
1818
---
1919

20-
# How Dataverse SQL differs from Transact-SQL (Preview)
21-
22-
[!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
20+
# How Dataverse SQL differs from Transact-SQL
2321

2422
This article describes the differences between Dataverse SQL and Transact-SQL. Dataverse SQL is a subset of Transact-SQL.
2523

@@ -42,6 +40,7 @@ More information: [Data types (Transact-SQL)](/sql/t-sql/data-types/data-types-t
4240
- nchar
4341
- numeric
4442
- nvarchar*
43+
- nvarchar(max) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# multi-line text
4544
- real
4645
- smalldatetime
4746
- smallint
@@ -62,13 +61,9 @@ More information: [Data types (Transact-SQL)](/sql/t-sql/data-types/data-types-t
6261

6362
- binary
6463
- image
65-
- ntext
66-
- nvarchar(max)
6764
- sql_variant
68-
- text
6965
- timestamp
7066
- varbinary
71-
- varchar(max)
7267
- virtual
7368
- partylist
7469
- HierarchyId
@@ -424,4 +419,4 @@ Hints are not supported.
424419

425420
[Use SQL to query data](dataverse-sql-query.md)
426421

427-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
422+
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/model-driven-apps/use-iframe-and-web-resource-controls-on-a-form.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,11 @@ IFRAME and web resource controls embed content from another ___location in pages by
2323
> [!NOTE]
2424
> The designs you choose for the form are also used for the Dynamics 365 for Outlook reading pane and forms used by Dynamics 365 tablets. Web resources and IFRAMEs aren’t displayed using the Dynamics 365 for Outlook reading pane, however, they are supported in Dynamics 365 for tablets. If your IFRAME depends on access to the `Xrm` object of the page or any form event handlers, you should configure the IFRAME so that it's not visible by default.
2525
26-
You can use an IFRAME to display the contents from another website in a form, for example, in an ASP.NET page. Displaying a form within an IFrame embedded in another form is not supported.
26+
You can use an IFRAME to display the contents from another website in a form, for example, in an ASP.NET page.
27+
28+
It is recommended to use [Power Apps component framework components](../component-framework/custom-controls-overview.md) if you're considering to use a web resource to show content that users will interact with.
29+
30+
Displaying a form within an IFrame embedded in another form is not supported.
2731

2832
You can use one of the following web resources to display the contents of web resources in a form:
2933

@@ -153,4 +157,4 @@ IFrame.setSrc(newTarget);
153157

154158

155159

156-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
160+
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/model-driven-apps/webpage-html-web-resources.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ Because an HTML web resource is just streamed to the user's browser, it can incl
3434

3535
- HTML web resources can only accept a limited number of query string parameters. [Pass parameters to HTML web resources](webpage-html-web-resources.md#BKMK_PassingParametersToWebResources)
3636

37+
- HTML web resources embedded as controls in a form can be reloaded by the form runtime for performance reasons. For example, the form runtime may destroy and re-initialize the control during tab navigations.
38+
3739
<a name="BKMK_UsingTextEditor"></a>
3840

3941
## Use the text editor for HTML web resources
@@ -150,4 +152,4 @@ Because of the capability for the HTML in web resources to be changed by using t
150152
[Using Stylesheet (XSL) web resources](stylesheet-xsl-web-resources.md)
151153

152154

153-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
155+
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2447,6 +2447,8 @@
24472447
href: ../teams/localizing-sample-apps.md
24482448
- name: Theming in sample apps
24492449
href: ../teams/sample-app-theming.md
2450+
- name: Working with table permission in sample apps
2451+
href: ../teams/dataverse-for-teams-table-permissions.md
24502452
- name: FAQs for sample apps
24512453
href: ../teams/sample-apps-faqs.md
24522454
- name: Known issues and limitations

powerapps-docs/maker/portals/configure/web-page.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sandhangitmsft
55
ms.service: powerapps
66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 04/21/2020
8+
ms.date: 08/19/2021
99
ms.subservice: portals
1010
ms.author: sandhan
1111
ms.reviewer: tapanm
@@ -65,6 +65,9 @@ The table below explains many of the standard web page attributes used by portal
6565

6666
Page comments provides users with the ability to view and post comments on a web page. By default this feature is disabled and can be enabled on a page by page basis.
6767

68+
> [!NOTE]
69+
> Comments are available when pages use **Full page** or **Page** page template.
70+
6871
1. Open the [Portal Management app](configure-portal.md).
6972

7073
2. Go to **Portals** > **Web Pages**.

0 commit comments

Comments
 (0)