Live publish for 28 February 2024.

bishalgoswami · web-flow · commit faccdd595160 · 2024-02-28T06:00:07.000+05:30
diff --git a/powerapps-docs/developer/data-platform/create-elastic-tables.md b/powerapps-docs/developer/data-platform/create-elastic-tables.md
@@ -2,7 +2,7 @@
 title: Create elastic tables using code
 description: Learn how to create Dataverse elastic tables with code.
 ms.topic: article
-ms.date: 07/18/2023
+ms.date: 02/22/2024
 author: pnghub
 ms.author: gned
 ms.reviewer: jdaly
@@ -11,6 +11,7 @@ search.audienceType:
 contributors:
  - sumantb-msft
  - JimDaly
+ - bhavana95
 ---
 
 # Create elastic tables using code
@@ -319,10 +320,22 @@ One-to-many relationships are supported for elastic tables with the following li
 - Formatted values for lookup columns aren't returned when the following conditions are true:
 
     - The table that is retrieved is a standard table, and the lookup refers to an elastic table.
-    - You're using a custom elastic table `partitionid` value. In other words, the `partitionid` value is set to something other than the default value (the primary key value of the elastic table row). [Learn how to choose a partitionid value](elastic-tables.md#choosing-a-partitionid-value).
+    - You're using a custom elastic table `partitionid` value. In other words, the `partitionid` value is set to something other than the default value (null). [Learn how to choose a partitionid value](elastic-tables.md#choosing-a-partitionid-value).
 
 Elastic tables support one-to-many relationships, and related rows can be retrieved when a record is retrieved. Related records can't be included in a query. [Learn how to return related rows in a query](use-elastic-tables.md#return-related-rows-in-a-query).
 
+### Partitionid value column on referencing table
+
+When you create a many-to-one relationship on a table that refers to an elastic table, a lookup column is created on the referencing table as you would expect.
+
+At the same time, a string column is created that follows this naming convention `<lookup name>pid`. This column stores the `partitionid` value for the related elastic table record.
+
+The `<lookup name>pid` column value is set automatically when you use the elastic table alternate key to set the lookup column. [Learn to associate elastic table records](use-elastic-tables.md#associate-elastic-table-records)
+
+If you are *not* using a partitioning strategy for your elastic table, the value for this `<lookup name>pid` column is null, and you shouldn't change it after the record is created.
+
+If you *are* using a partitioning strategy for your elastic table, and you want to retrieve the related elastic table record, you can't rely on the value of the lookup column alone. You must also include the `partitionid` value from the `<lookup name>pid` column to uniquely identify the related table. [Learn more about partitioning and horizontal scaling](elastic-tables.md#partitioning-and-horizontal-scaling)
+
 ## Next steps
 
 > [!div class="nextstepaction"]
diff --git a/powerapps-docs/developer/data-platform/use-elastic-tables.md b/powerapps-docs/developer/data-platform/use-elastic-tables.md
@@ -2,7 +2,7 @@
 title: Use elastic tables using code
 description: Learn how to perform data operations on Dataverse elastic tables using code.
 ms.topic: how-to
-ms.date: 01/18/2024
+ms.date: 02/22/2024
 author: pnghub
 ms.author: gned
 ms.reviewer: jdaly
@@ -11,6 +11,7 @@ search.audienceType:
 contributors:
  - sumantb-msft
  - JimDaly
+ - bhavana95
 ---
 
 # Use elastic tables using code
@@ -84,6 +85,9 @@ MSCRM.SessionToken: 240:8#144100870#7=-1
 
 As was mentioned in [Partitioning and horizontal scaling](elastic-tables.md#partitioning-and-horizontal-scaling), each elastic table has a `partitionid` column that you must use if you choose to apply a partitioning strategy for the table. Otherwise, don't set a value for the `partitionid` column.
 
+> [!IMPORTANT]
+> If you choose to use a partitioning strategy for your elastic table, all operations on that table or referring to records in that table **MUST** specify the `partitionid` column value to uniquely identify the record. There is no error thrown if `partitionid` is not specified in the lookup value of referencing table, but the lookup will fail to locate the record when you use it. You must document and enforce this requirement via code reviews to ensure that your data is consistent and `partitionid` is used appropriately for all the operations.
+
 After you specify a non-null value for the `partitionid` column when you create a row, you must specify it when you perform any other data operation on that row. You can't change the value later.
 
 If you don't set a `partitionid` value for a record when you create it, the `partitionid` column value remains null, and you can't change it later. In this case, you can identify records by using the primary key, just as you do with standard tables. Specifying a `partitionid` value isn't required.
@@ -97,7 +101,7 @@ You can set the `partitionid` value in following ways when you perform various d
 
 As was mentioned in [Alternate keys](create-elastic-tables.md#alternate-keys), every elastic table has an alternate key that is named `KeyForNoSqlEntityWithPKPartitionId`. This alternate key combines the primary key of the table with the `partitionid` column.
 
-You can use this alternate key to specify the `partitionid` value when you use `Retrieve`, `Update`, or `Delete` operations.
+If you are using a partitioning strategy, you must specify an alternate key to specify the `partitionid` value when you use `Retrieve`, `Update`, or `Delete` operations, or when you set a lookup column for another table that refers to an elastic table record.
 
 #### [SDK for .NET](#tab/sdk)
 
@@ -680,6 +684,173 @@ You can also use the `partitionId` parameter:
 
 ---
 
+## Associate elastic table records
+
+When a table record refers to an elastic table record where the `partitionid` column value is null, you can associate a record in that table to a elastic table record just like standard records. Refer [SDK for .NET](org-service/entity-operations-associate-disassociate.md), or [the Web API](webapi/associate-disassociate-entities-using-web-api.md).
+
+When a table record refers to an elastic table record which has `partitionid` column value set, you must include the `partitionid` column value of the elastic table record when you set the lookup column of the referencing table. You can do this by including the value as an alternate key. 
+
+As described in [Partitionid value column on referencing table](create-elastic-tables.md#partitionid-value-column-on-referencing-table), when a one-to-many relationship is created and the elastic table is the *referenced* table, a string column and a lookup column is created on the *referencing* table. The string column stores the `partitionid` value of the referenced elastic table record.
+
+You can set both the lookup and the string column values with their respective values by:
+
+- Using an alternate key reference to set only the lookup
+- Setting the two column values together in one update
+
+How you do this depends on whether you are using the SDK for .NET or Web API
+
+
+#### [SDK for .NET](#tab/sdk)
+
+This example associates an elastic `contoso_SensorData` table record with the specified ID and `partitionid` to an existing account record by setting the lookup column with an alternate key:
+
+```csharp
+/// <summary>
+/// Demonstrates associate to elastic table operation.
+/// </summary>
+/// <param name="service">Authenticated client implementing the IOrganizationService interface</param>
+/// <param name="sensordataId">The unique identifier of the contoso_sensordata table.</param>
+/// <param name="deviceId">The deviceId. PartitionId of sensor data record.</param>
+/// <param name="accountId">The unique identifier of the account record to update.</param>
+public static void AssociateAccountAlternateKeyExample(
+    IOrganizationService service,
+    Guid sensordataId,
+    string deviceId,
+    Guid accountId)
+{
+    var keys = new KeyAttributeCollection() {
+        { "contoso_sensordataid", sensordataId },
+        { "partitionid", deviceId }
+    };
+
+    var sensorDataReference = new EntityReference("contoso_sensordata", keys);
+
+    Entity account = new("account", accountId)
+    {
+        Attributes =
+            {
+                {"contoso_sensordata", sensorDataReference}
+            }
+    };
+
+    service.Update(account);
+}
+```
+
+This example does the same thing, but sets both of the columns together:
+
+```csharp
+/// <summary>
+/// Demonstrates associate to elastic table operation.
+/// </summary>
+/// <param name="service">Authenticated client implementing the IOrganizationService interface</param>
+/// <param name="sensordataId">The unique identifier of the contoso_sensordata table.</param>
+/// <param name="deviceId">The deviceId. PartitionId of sensor data record.</param>
+/// <param name="deviceId">The unique identifier of the account record to update.</param>
+public static void AssociateAccountBothColumnsExample(
+    IOrganizationService service,
+    Guid sensordataId,
+    string deviceId,
+    Guid accountId)
+{
+    Entity account = new("account", accountId) {
+        Attributes =
+            {
+                {"contoso_sensordata", new EntityReference("contoso_sensordata", sensordataId)},
+                {"contoso_sensordatapid", deviceId }
+            }
+    };
+
+    service.Update(account);
+}
+```
+
+Finally, this example shows using the [AssociateRequest](xref:Microsoft.Xrm.Sdk.Messages.AssociateRequest) to associate a collection of `account` records to the same `contoso_SensorData` table record in one operation.
+
+```csharp
+/// <summary>
+/// Demonstrates associating multiple accounts to a contoso_sensordata elastic table record
+/// </summary>
+/// <param name="service">Authenticated client implementing the IOrganizationService interface</param>
+/// <param name="sensordataId">The unique identifier of the contoso_sensordata table.</param>
+/// <param name="deviceId">The deviceId. PartitionId of sensor data record.</param>
+/// <param name="relatedEntities">A collection of references to account records to associate to the contoso_sensordata elastic table record</param>
+public static void AssociateMultipleElasticTableExample(
+   IOrganizationService service,
+   Guid sensordataId,
+   string deviceId,
+   EntityReferenceCollection relatedEntities)
+{
+
+   // The keys to the elastic table record including the partitionid
+   var keys = new KeyAttributeCollection() {
+         { "contoso_sensordataid", sensordataId },
+         { "partitionid", deviceId }
+   };
+
+   AssociateRequest request = new()
+   {
+         Target = new EntityReference("contoso_sensordata", keys),
+         Relationship = new Relationship("contoso_SensorData_contoso_SensorData_Acc"),
+         RelatedEntities = relatedEntities
+   };
+
+   service.Execute(request);
+}
+```
+
+
+#### [Web API](#tab/webapi)
+
+This example uses the alternate key style to associate a row of the `contoso_SensorData` table with `contoso_sensordataid` = `490c3c40-e8d1-ee11-9079-000d3a993550` and `partitionid` = `'DEVICE-123'` to account record with `accountid` value of `2ada33e7-ef8b-ee11-8179-000d3a9933c9`.
+
+**Request:**
+
+```http
+PATCH [Organization URI]/api/data/v9.2/accounts(2ada33e7-ef8b-ee11-8179-000d3a9933c9)
+Content-Type: application/json
+OData-MaxVersion: 4.0
+OData-Version: 4.0
+
+{
+  "contoso_SensorData@odata.bind": "contoso_sensordatas(contoso_sensordataid=490c3c40-e8d1-ee11-9079-000d3a993550,partitionid='DEVICE-123')"
+}
+```
+
+**Response:**
+
+```http
+HTTP/1.1 204 No Content
+OData-Version: 4.0
+```
+
+This example does the same thing, but sets both of the columns together:
+
+**Request:**
+
+```http
+PATCH [Organization URI]/api/data/v9.2/accounts(2ada33e7-ef8b-ee11-8179-000d3a9933c9)
+Content-Type: application/json
+OData-MaxVersion: 4.0
+OData-Version: 4.0
+
+
+{
+  "contoso_sensordatapid": "DEVICE-123",
+  "contoso_SensorData@odata.bind": "contoso_sensordatas(490c3c40-e8d1-ee11-9079-000d3a993550)"
+}
+
+```
+
+**Response:**
+
+```http
+HTTP/1.1 204 No Content
+OData-Version: 4.0
+```
+
+---
+
 ## Bulk operations with elastic tables
 
 Often, applications must ingest a large amount of data into Dataverse in a short time. Dataverse has a group of messages that are designed to achieve high throughput. With elastic tables, the throughput can be even higher.
diff --git a/powerapps-docs/maker/data-platform/azure-synapse-link-view-in-fabric.md b/powerapps-docs/maker/data-platform/azure-synapse-link-view-in-fabric.md
@@ -98,7 +98,7 @@ Link to Microsoft Fabric from the Power Apps **Tables** area: Select **Analyze**
 5. If needed, the wizard asks you to create a one time connection to Microsoft Fabric within the same step. This connection is needed to enable Fabric and Dataverse services to securely access data. You need to sign in and then save the connection to proceed.
 6. The wizard asks you to select an existing Fabric workspace or to create a new one. You can expect to see shortcuts to all your tables within this workspace.
 7. If you don't see workspaces, ask the system to create a workspace. Go to [Troubleshooting common issues](#troubleshooting-common-issues) if you don't see the desired workspace.  
-8. All Dataverse tables where "Change tracking" property is enabled are linked to Fabric. If this environment is linked to Finance Operations, you can add Finance and operations tables later. See [manage links section](## Manage link to Fabric).
+8. All Dataverse tables where "Change tracking" property is enabled are linked to Fabric. If this environment is linked to finance and operations apps, you can add finance and operations tables later. More information: [Manage link to Fabric](#manage-link-to-fabric).
 9. When done, select **Create** in the wizard to create the workspace, create shortcuts, and to perform the initialization for the first time.
 10. When complete, Fabric lakehouse opens in a separate browser tab. 
 
@@ -123,7 +123,7 @@ Admins can manage tables linked to OneLake from the **Azure Synapse Link for Dat
 5. When you add a table, the system performs an initial sync and indexes the data. When the initial sync is completed, a shortcut to OneLake is created. View the status of tables by selecting **Manage tables**.
 
    > [!NOTE]
-   > If your environment is linked to a Dynamics 365 finance and operations environment, the add tables option enables you to include tables from finance and operations apps. Learn more: (Choose finance and operations data in Azure Synapse Link for Dataverse)[azure-synapse-link-select-FnO-data.md]
+   > If your environment is linked to a Dynamics 365 finance and operations environment, the add tables option enables you to include tables from finance and operations apps. Learn more: [Choose finance and operations data in Azure Synapse Link for Dataverse](azure-synapse-link-select-FnO-data.md)
 
 6. When the sync status is **Active**, as data gets updated, your data changes are shown in reports created in Fabric.
 7. If a new column is added to a table that’s already added (also known as a metadata change), you can use the **Refresh Fabric tables** option to update the change in Fabric. You might need to review the report and downstream data flows to see that they aren't impacted by the change.
diff --git a/powerapps-docs/maker/data-platform/preferred-solution.md b/powerapps-docs/maker/data-platform/preferred-solution.md
@@ -59,7 +59,8 @@ You can delete your preferred solution or a preferred solution that other makers
 
 - You can't set or view the preferred solution in the classic solution explorer.
 - Components that are created in the classic solution explorer won't go into the preferred solution.
-- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, flows, connections, gateways, custom connectors, and canvas apps created from image or a figma design.
+- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, and canvas apps created from image or a figma design.
+- When a component is already part of an existing unmanaged solution, it will still be added to the preferred solution.
 
 ### See also
 
diff --git a/powerapps-docs/maker/model-driven-apps/set-properties-chart-list-included-dashboard.md b/powerapps-docs/maker/model-driven-apps/set-properties-chart-list-included-dashboard.md
@@ -2,9 +2,8 @@
 title: "Set properties for a model-driven app chart or list included in a dashboard in Power Apps | MicrosoftDocs"
 description: "Learn how to set properties for  chart or list included in a dashboard"
 ms.custom: ""
-ms.date: 06/06/2018
+ms.date: 02/27/2024
 ms.reviewer: ""
-
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "conceptual"
@@ -48,11 +47,11 @@ search.audienceType:
       
     - **Default View**. Select the view used to retrieve the data for the chart.  
       
-    - **Default Chart**. Select the default chart that you want to display when the dashboard is first opened. The available values are determined by the value set for the Table property. This property works together with the Display Chart Selection property. A user can change the type of chart if the **Display Chart Selection** option is turned on, but the chart will revert to Default Chart the next time the dashboard is opened.  
+    - **Default Chart**. Select the default chart that you want to display when the dashboard is first opened. The available values are determined by the value set for the Table property. This property works together with the Display Chart Selection property. A user can change the chart displayed in the component if the **Display Chart Selection** option is turned on, but the chart will revert to Default Chart the next time the dashboard is opened.  
       
     - **Show Chart Only**. Select this check box if you want to display just the chart. Clear this check box if you want to display the chart and its associated data.  
       
-    - **Display Chart Selection**. Select this check box to enable users to change the type of chart (column, bar, pie, etc.) when they use the dashboard. If the user changes the type of chart, the settings aren’t saved. The chart type reverts to the Default Chart setting when the dashboard is closed.  
+    - **Display Chart Selection**. Select this check box to enable users to change the chart displayed in the component at runtime. The component reverts to displaying the Default Chart next time the dashboard is opened.
   
 1. You can set the following **list** properties from the **Set Properties** dialog box:  
       
