Merge remote-tracking branch 'origin/main' into dsierman-patch-3

Author: Mattp123

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

@@ -1,7 +1,6 @@
 ---
 title: "Use SQL to query data (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to query Microsoft Dataverse table data using SQL." # 115-145 characters including spaces. This abstract displays in the search result.
-
 ms.date: 05/18/2023
 ms.reviewer: "pehecke"
 ms.topic: "article"
@@ -14,10 +13,13 @@ search.audienceType:
 
 # Use SQL to query data
 
-[This topic is pre-release documentation and is subject to change. Note that only the SQL data connection through SQL Server Management Studio and .NET libraries is in preview. Power BI is General Availability (GA)]
+[This topic is pre-release documentation and is subject to change.]
 
 The Microsoft Dataverse business layer provides a Tabular Data Stream (TDS) endpoint that emulates a SQL data connection. The SQL connection provides read-only access to the table data of the target Dataverse environment thereby allowing you to execute SQL queries against the Dataverse data tables. No custom views of the data have been provided. The Dataverse endpoint SQL connection uses the Dataverse security model for data access. Data can be obtained for all Dataverse tables to which a user has access.
 
+> [!NOTE]
+>  Only the SQL data connection through SQL Server Management Studio and .NET libraries is in preview. Power BI is generally available.
+
 ## Prerequisites
 
 The **Enable TDS endpoint** setting must be enabled in your environment. It is enabled by default. More information: [Manage feature settings](/power-platform/admin/settings-features)

powerapps-docs/maker/data-platform/low-code-plug-ins.md

@@ -164,6 +164,8 @@ Unique properties:
 
 ## Use Power Platform connectors in low-code plug-ins
 
+Power Platform connectors can be used in low-code plug-ins to easily integrate data and functionality from systems outside of Dataverse, such as SQL Server, Salesforce, and SharePoint, without the need for complex coding or custom development.
+
 ### Prerequisites for using connectors in low-code plug-ins
 
 > [!div class="checklist"]
@@ -172,10 +174,7 @@ Unique properties:
 
 ### Using connector actions in low-code plug-ins
 
-You can easily use [connectors]( /connectors/connector-reference/connector-reference-powerapps-connectors) and [custom connectors]( /connectors/custom-connectors/) from within a low-code plug-in Power Fx formula.
-
-> [!NOTE]
-> Not all connector actions are supported at this time.
+You can easily use [connectors]( /connectors/connector-reference/connector-reference-powerapps-connectors) and [custom connectors]( /connectors/custom-connectors/) from within a low-code plug-in a Power Fx formula.
 
 1. Create a connection to the connector you want to use.
 1. [Add a connection reference](/power-apps/maker/data-platform/create-connection-reference#manually-add-a-connection-reference-to-a-solution-using-solution-explorer) to the connection in the Dataverse environment.
@@ -186,13 +185,26 @@ Before using a connector in a low-code plug-in, review the connector's [document
 
 More information: [example](lowcode-plug-ins-examples.md#sample-instant-plug-in-with-msn-weather-connector)
 
-## Smart low-code plug-ins
+> [!NOTE]
+> * Not all connector actions are supported at this time.
+> * Do not use the Dataverse connector to connect to Dataverse tables from a plug-in expression. Instead, use the native Power Fx functions to interact with collections: [Filter, Search, LookUp](/power-platform/power-fx/reference/function-filter-lookup), [Patch](/power-platform/power-fx/reference/function-patch), [Collect](/power-platform/power-fx/reference/function-clear-collect-clearcollect#collect), and [Set](/power-platform/power-fx/reference/function-set), where columns are treated as global variables.
+
+## AI functions in low-code plug-ins
 
-### What are smart low-code plug-ins?
+### What are AI functions in low-code plug-ins?
 
 Dataverse includes AI-powered actions, which can be used to generate or extract data using Azure Open AI and the power of AI Builder. You can call these functions from both instant and automated low-code plug-ins.  
 
-**Functions supported for smart low-code plug-ins**
+### Prerequisites for using AI functions in low code plug-ins
+
+> [!div class="checklist"]
+> * [Prerequisites for creating a low-code plug-in](#prerequisites-for-creating-a-low-code-plug-in)
+> * AI Builder subscription
+
+> [!TIP]
+> If you don't have an AI Builder subscription, you can use an [AI Builder trial](/ai-builder/ai-builder-trials). View the AI models page in Power Apps (make.powerapps.com) to get AI Builder, which directs you to start a trial.
+
+### Supported functions
 
 | Function | Description |
 | - | - |
@@ -203,18 +215,13 @@ Dataverse includes AI-powered actions, which can be used to generate or extract
 | `AIClassify`| Classify text into one or more provided categories ([Example](lowcode-plug-ins-examples.md#sample-for-aiclassify)) | 
 | `AIExtract`| Extract specified entities such as registration numbers ([Example](lowcode-plug-ins-examples.md#sample-for-aiextract)) | 
 
-### Requirements
-
-> [!div class="checklist"]
-> * [Prerequisites for creating a low-code plug-in](#prerequisites-for-creating-a-low-code-plug-in)
-> * AI Builder subscription
+### Using AI functions in low-code plug-ins
 
-> [!TIP]
-> If you do not have an AI Builder subscription, you can use an [AI Builder trial](/ai-builder/ai-builder-trials). View the AI models page in Power Apps (make.powerapps.com) to get AI Builder, which directs you to start a trial.
+Type in the AI function and provide the correct input values. Use intellisense and the linked example documentation to understand how to provide correct values to each function.
 
 ## Test a low-code plug-in
 
-**Manually test instant plug-ins**
+## Test instant plug-ins
 
   1. From the **Home screen**, select an instant plug-in from the list, then select **Test** on the command bar. You can also get to this screen from the instant plug-in editor in the command bar after it's been saved.
   :::image type="content" source="media/low-code-plugin-test-home.png" alt-text="Select Test for the low-code plug-in":::
@@ -227,9 +234,14 @@ Dataverse includes AI-powered actions, which can be used to generate or extract
   > [!TIP]
   > Use output parameters to help validate expected behavior and results. Otherwise, you only see a success or failure when testing.
 
-**Test automated plug-ins**
+### Test automated plug-ins
 
 Test automated plug-ins by invoking the data event. Observe if the plug-in ran successfully by validating expected changes that were defined in the formula.
+> [!TIP]
+> During the preview, you can invoke the associated data event using the table editor in Power Apps:
+> 1. Sign into [Power Apps](https://make.powerapps.com), go to **Tables** > _Plug-in table_.
+> 1. On the command bar, select **Edit**.
+> 1. Create, update, or delete rows directly from this view. Alternatively, open a row in the default form by selecting a row, then select **Edit row using form** on the command bar.
 
 ### Integrate a low-code plug-in
 
@@ -268,12 +280,6 @@ Learn more about how you can [call Dataverse actions directly from Power Fx in c
 
 Follow the steps for **Unbound action** or **Function bound to table** sections in the [Invoking custom APIs from the Web API documentation](/power-apps/developer/data-platform/custom-api#invoking-custom-apis-from-the-web-api) (depending on the appropriate scope of the plug-in).
 
-## Trace logging
-
-Trace logging is a feature in Dataverse that allows you to capture detailed information about the execution of plug-ins. By enabling trace logging, you can get a more complete picture of what's happening during plug-in execution, which can be helpful for troubleshooting issues and identifying performance bottlenecks. When you enable trace logging for plug-ins, Dataverse generates log files that include information about the plug-in's input and output parameters, as well as any exceptions or errors that occur during execution.
-
-To enable trace logging for plug-ins, you need to [enable the trace logging feature for the environment](/power-apps/developer/data-platform/logging-tracing).
-
 ## Contacting Help + support
 
 For issues with the Dataverse Accelerator solution installation or low-code plug-ins, such as errors received, [use the Help + support experience](/power-platform/admin/get-help-support) and include the following information:
@@ -298,7 +304,7 @@ For a few examples of how to create a low-code plug-in, go to [Example Dataverse
         { Regarding : First(Accounts) }
     )
     ```
-- When low-code plug-ins interact with connectors and DLP is employed, the admin can block creation of connections using DLP. However, existing connection references in the Dataverse environment will continue to function. In case the admin needs to block all low-code plug-in interactions with any connectors, they can simply disable the organization setting `Allowconnectorsonpowerfxactions`. This setting is enabled by default and can be disabled by usual SDK methods (WebAPI, SDK, PowerShell, and so on). You can disable this using a low-code instant plug-in as follows:
+- When low-code plug-ins interact with connectors and DLP is employed, the admin can block creation of connections using DLP. However, existing connection references in the Dataverse environment continue to function. In case the admin needs to block all low-code plug-in interactions with any connectors, they can disable the organization setting `Allowconnectorsonpowerfxactions`. This setting is enabled by default and can be disabled by usual SDK methods (WebAPI, SDK, PowerShell, and so on). You can disable this using a low-code instant plug-in as follows:
    ```powerapps-dot
    Patch(Organizations, First(Organizations), { 'Enable connectors on power fx actions.': 'Enable connectors on power fx actions. (Organizations)'.No })
    ```

powerapps-docs/maker/model-driven-apps/media/timeline-what-you-missed-display-view.png

@@ -50,7 +50,6 @@ When you configure the Power Apps read-only grid control for a table, *all* view
    - **Navigation types allowed**: Determines which lookup controls in the grid render as hyperlinks. The default value is All.
      - **All**: All table lookup columns render in the grid as a hyperlink.
      - **Primary only**: Suppresses hyperlinks on all lookup fields except the primary column for the selected table.
-     - **None**: Doesn't display hyperlinks, which allow table record navigation.
 
    :::image type="content" source="media/configure-power-apps-grid-control.png" alt-text="Select the client types where you want to use the control" lightbox="media/configure-power-apps-grid-control.png":::
 1. To save your changes, select **Save** on the command bar. When you're ready to make the changes available to app users, select **Publish** on the command bar.

powerapps-docs/maker/model-driven-apps/power-apps-grid-control.md

@@ -2,7 +2,7 @@
 title: Add and configure the timeline control in Power Apps | MicrosoftDocs
 description: "Learn how to add and configure the timeline control to use in a model-driven app."
 ms.custom: ""
-ms.date: 09/11/2023
+ms.date: 10/05/2023
 ms.reviewer: "matp"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -232,7 +232,7 @@ You can send and receive records with images, but they don't display when the re
 
 |Form designer configure view | Form designer display view|
 |---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|
-|![Configure “What you’ve missed” summary](media\timeline-what-you-missed-display-options-advanced-11a.png "Configure “What you’ve missed” summary")| ![Disable “What you’ve missed” summary](media\timeline-what-you-missed-display-options-advanced-11b.png "Disable “What you’ve missed” summary") |
+|![Configure “What you’ve missed” summary](media\timeline-what-you-missed-display-options-advanced-11a.png "Configure “What you’ve missed” summary")| ![Display view for “What you’ve missed” summary](media\timeline-what-you-missed-display-view.png "Disable “What you’ve missed” summary") |
 |The **What you’ve missed** setting displays new records you haven't seen. It's enabled by default. To disable it, clear the box next to the setting. |When enabled, when you view an account record, the newest activities appear at the top of the list.|
 
 ### Record settings
@@ -615,17 +615,26 @@ Power platform administrators can restrict the file size of attachments users ca
 
 ## Known issues
 
-### When you create a note in a timeline, the character string "$&" is converted to "{3}amp;"
+### Duplicate posts are shown when sorting records by older to newer
+
+The API the timeline uses to fetch posts doesn't support sorting by older to newer posts. When you sort this way, the timeline receives the wrong posts to display. When sorting the timeline by older to newer, use notes instead.
+
+### Notes can only have one attachment added from the attachment button
 
-This is a configuration issue for the rich text editor control. To resolve this, add `"removePlugins": "stickystyles" ` to your RTE config file. More information: [Create and use advanced configuration for the rich text editor control](rich-text-editor-control.md#create-and-use-advanced-configuration-for-the-rich-text-editor-control)
+This is by design, with plans to allow more attachments in the near future. Multiple attachments can be added inline by dragging and dropping them into the note.
 
 ### Timeline fails to load with error `code:"0x8004430d","message":"Number of link entity: <number> exceed limit 15`
 
 There's a limit of 15 different tables that can be associated with a timeline. Either disable some of the activities associated with the timeline, or follow one of the workarounds described in this article: [Timeline doesn't render and shows "Records couldn't be loaded"](https://support.microsoft.com/topic/timeline-does-not-render-and-shows-records-could-not-be-loaded-4ce9200a-1afe-3ef4-ac11-a74b91f4f40c)
 
+### When you create a note in a timeline, the character string "$&" is converted to "{3}amp;"
+
+This is a configuration issue for the rich text editor control. To resolve this, add `"removePlugins": "stickystyles" ` to your RTE config file. More information:  [Rich text editor properties](rich-text-editor-control.md#rich-text-editor-properties)
+
 ### See also
 
 [FAQs for timeline control](faqs-timeline-control.md) 
 
+[Use the timeline control](../../user/add-activities.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/model-driven-apps/set-up-timeline-control.md

@@ -45,7 +45,7 @@ When you configure the Power Apps grid control for an entity, all views for that
        :::image type="content" source="media/jump-bar-in-view.png" alt-text="Jump bar enabled and displayed in the view for an app":::
     - The **Enable pagination** property can be used to decide between modern data browsing (infinite scroll) and paging buttons. The default value is **No**. Select **Yes** to disable infinite scrolling and surface paging buttons. Note that the **Select all** action isn't available currently when using infinite scroll, but users can still perform range selection
     - The **Enable OptionSet colors** property can be used to increase the visual appeal of choice columns by showing each value with its configured background color.  The default value is **No**. Be sure to verify the configured color for each choice column to ensure readability and accessibility before enabling this property for a table.  
-    - The **Navigation types allowed** property determines which lookup controls in the grid render as hyperlinks. The default value is **All**. Select **Primary only** to suppress hyperlinks on all lookup fields except the primary column for the selected entity.  
+    - The **Navigation types allowed** property determines which lookup controls in the grid render as hyperlinks. The default value is **All**. Select **Primary only** to suppress hyperlinks on all lookup fields except the primary column for the selected entity, or **None** to suppress all hyperlinks in the grid.  
     -  The **Customizer control** property allows the maker to link to a single customizer PCF control with definitions for changing the visuals or interactions for one or more columns in the grid. <!-- More information: [Customizing the Power Apps grid control](tbd) -->
 
 3. After configuring the Power Apps grid control to meet your needs, select **Save** on the command bar to save your changes. When you're ready to make the changes available to app users, select **Publish** on the command bar.