Merge branch 'main' into patch-6

Author: JimDaly

powerapps-docs/developer/data-platform/use-upsert-insert-update-record.md

@@ -1,7 +1,7 @@
 ---
 title: "Use Upsert to insert or update a record (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "UpsertRequest(Update or Insert) message helps you simplify various data integration scenarios where you do not know if a record already exists in Microsoft Dataverse. In such cases you won’t know if you should call an UpdateRequest or a CreateRequest operation. This results in your querying for the record first to determine if it exists before performing the appropriate operation. UpsertRequest message helps you solve that issue" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 03/22/2022
+ms.date: 04/08/2022
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "divka78" # GitHub ID
@@ -25,44 +25,47 @@ You can reduce the complexity involved with data integration scenarios by using
 
 <a name="BKMK_UsingUpsert"></a>   
 
-## Using Upsert  
+## Using Upsert
+
  It is best to use <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> only when you aren’t sure if the record exists. That is, when you aren’t sure if you should call a <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> or an <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest> operation. There is a performance decrease in using <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> versus using <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest>. If you are sure the record doesn’t exist, use <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest>.  
 
- The <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> includes a property named <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest.Target>. This property contains the table definition that will be used in an <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest> or a <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> operation. It also includes all the columns required by the <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> for the target table type so that the record can be created if it doesn’t exist.  
+ The <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> includes a property named <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest.Target>. This property contains the entity instance that will be used in an <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest> or a <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> operation. It also includes all the columns required by the <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> for the target entity so that the record can be created if it doesn’t exist.  
 
  You can inspect <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.RecordCreated> to determine if the record was created. <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.RecordCreated> will be true if the record didn’t exist and was created. It will be false if the record already existed and was updated. <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.Target> will be an `EntityReference` to the record that was found to exist or to the record that was created.  
 
  To understand how <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> works, see the following section.  
 
-<a name="BKMK_upsert"></a>   
+<a name="BKMK_upsert"></a>
+
 ## Understanding the Upsert process  
+
  The following steps describe the processing logic when an <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> is received:  
 
 1. Send <xref:Microsoft.Xrm.Sdk.Messages.UpsertRequest> with enough data for a create or insert operation.  
 
-2. Dataverse will look up the record targeted by the target table.  
+2. Dataverse will look up the record targeted by the target entity.  
 
 3. If the record exists:  
 
-   1.  Set the ID property of the target table with the ID of the found record.  
+   1.  Set the ID property of the target entity with the ID of the found record.  
 
    2.  Call Update.  
 
    3.  Set the <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.RecordCreated> to `false`.  
 
-   4.  Create an <xref:Microsoft.Xrm.Sdk.EntityReference> from the target table of the update as the value for <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.Target>.  
+   4.  Create an <xref:Microsoft.Xrm.Sdk.EntityReference> from the target entity of the update as the value for <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.Target>.  
 
    5.  Return the <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse>.  
 
 4. If the record doesn’t exist:  
 
-   1.  Copy any alternate key values that the target does not already have in its attributes collection, into the target table columns.  
+   1.  Copy any alternate key values that the target does not already have in its attributes collection, into the target entity attributes.  
 
    2.  Call `Create`.  
 
    3.  Set the <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.RecordCreated> to `true`.  
 
-   4.  Create an <xref:Microsoft.Xrm.Sdk.EntityReference> from the target table type and the ID result of the `Create` request as the value for <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.Target>.  
+   4.  Create an <xref:Microsoft.Xrm.Sdk.EntityReference> from the target entity and the ID result of the `Create` request as the value for <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse.Target>.  
 
    5.  Return the <xref:Microsoft.Xrm.Sdk.Messages.UpsertResponse>.  
 
@@ -72,11 +75,12 @@ You can reduce the complexity involved with data integration scenarios by using
 
 <a name="BKMK_SampleCode"></a>   
 
-## Sample code  
- The [Insert or update a record using Upsert](/samples/browse/) sample [ProductUpsertSample.cs](https://code.msdn.microsoft.com/Insert-or-update-a-record-aa160870/sourcecode?fileId=136218&pathId=1243320355) file contains the following `ProcessUpsert` method to apply the `UpsertRequest` message on the contents of an XML file to create new records or update existing ones.  
+## Sample code
+
+The [SampleMethod.cs](https://github.com/microsoft/PowerApps-Samples/blob/master/cds/orgsvc/C%23/InsertRecordUsingUpsert/InsertRecordUsingUpsert/SampleMethod.cs) file in the [Insert record using Upsert](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/InsertRecordUsingUpsert/InsertRecordUsingUpsert) sample contains the following `ProcessUpsert` method to apply the `UpsertRequest` message on the contents of an XML file to create new records or update existing ones.  
 
 ```csharp
-public void ProcessUpsert(String Filename)
+public static void ProcessUpsert(CrmServiceClient service, String Filename)
 {
     Console.WriteLine("Executing upsert operation.....");
     XmlTextReader tr = new XmlTextReader(Filename);
@@ -97,15 +101,15 @@ public void ProcessUpsert(String Filename)
         productToCreate["sample_name"] = productName;
         productToCreate["sample_category"] = productCategory;
         productToCreate["sample_make"] = productMake;
-        UpsertRequest request = new UpsertRequest()
+        var request = new UpsertRequest()
         {
             Target = productToCreate
         };
 
         try
         {
             // Execute UpsertRequest and obtain UpsertResponse. 
-            UpsertResponse response = (UpsertResponse)_serviceProxy.Execute(request);
+            var response = (UpsertResponse)service.Execute(request);
             if (response.RecordCreated)
                 Console.WriteLine("New record {0} is created!", productName);
             else
@@ -117,22 +121,15 @@ public void ProcessUpsert(String Filename)
         {
             throw;
         }
-
     }
-    // Prompts to view the sample_product entity records.
-    // If you choose "y", IE will be launched to display the new or updated records.
-    if (PromptForView())
-    {
-        ViewEntityListInBrowser();
-    }
-
 }
 ```
 
-### See also  
- [Use change tracking to synchronize data with external systems](use-change-tracking-synchronize-data-external-systems.md)   
- [Define alternate keys for a table](define-alternate-keys-entity.md)   
- [Using alternate keys](use-alternate-key-create-record.md)
+### See also
+
+[Use change tracking to synchronize data with external systems](use-change-tracking-synchronize-data-external-systems.md)   
+[Define alternate keys for a table](define-alternate-keys-entity.md)   
+[Using alternate keys](use-alternate-key-create-record.md)
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/mobile/powerapps-mobile-troubleshoot.md

@@ -126,6 +126,22 @@ To resolve connection related issues, ensure you remain connected to the interne
 
 The Flow action menu in Power Apps mobile doesn't support flows created in a solution.
 
+## App resets when running it on Power Apps mobile
+
+When you run a canvas or model-driven app on Power Apps mobile it can reset if the app is using too many resources. If the app uses more resources than are available on your device, the app will reset. This is similar to when you visit a large complex webpage, and the web browser suspends the page because it is consuming too much power.
+
+Power Apps mobile is designed to run on a wide range of devices, including low-end devices with limited resources. When you create a canvas or model-driven app, remember to optimize the app to run on the lowest specificized device that your end-users will use.
+
+If you experience a reset, contact your app developer, and point them to this topic. 
+
+For more information for developers, see:
+
+- Blog post: [PowerApps coding standards and guidelines](https://powerapps.microsoft.com/blog/powerapps-canvas-app-coding-standards-and-guidelines/)
+- Whitepaper: [PowerApps canvas app coding
+standards and guidelines](https://pahandsonlab.blob.core.windows.net/documents/PowerApps%20canvas%20app%20coding%20standards%20and%20guidelines.pdf) (Note, review the section titled, **Optimizing for performance**).
+
+
+
 ### See also  
 
 [Power Apps portals known issues](../maker/portals/known-issues.md) <br/>