Merge branch 'main' into ado-13880

Author: ProfessorKendrick

.openpublishing.redirection.json

@@ -7,12 +7,12 @@
     },
     {
       "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/removeOnPostSave.md",
-      "redirect_url": "../../formContext-data-entity/removeOnPostSave",
+      "redirect_url": "../formContext-data-entity/removeonpostave",
       "redirect_document_id": false
     },
     {
       "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/addOnPostSave.md",
-      "redirect_url": "../../formContext-data-entity/addOnPostSave",
+      "redirect_url": "../formcontext-data-entity/addonpostsave",
       "redirect_document_id": false
     },
     {

powerapps-docs/cards/card-requirements.md

@@ -16,11 +16,11 @@ ms.collection:
 
 [!INCLUDE[cards_preview_notice](includes/preview-include.md)]
 
-This article contains information on requirements for cards to show up and work as expected.
+This article contains information about requirements for cards to show up and work as expected.
 
 ## Environment requirements
 
-Cards are available in environments with Dataverse.
+Cards are available in environments with Microsoft Dataverse.
 
 The table below shows the environment regions cards are supported in.
 

powerapps-docs/cards/make-a-card/designer-overview.md

@@ -42,7 +42,7 @@ Legend:
 
 ### Main menu
 
-Use the main menu to switch between the tools available in the card designer:
+Use the main menu to switch between the tools available in the card designer.
 
 - **Tree View**: View card elements as a hierarchy and view the relationships between elements
 - **Insert**: Add controls
@@ -75,16 +75,16 @@ Each element also has advanced properties, such as:
 
 - **Repeat for every**: Trigger whether or when an element should be repeated
 - **Show when**: Trigger when to show the element
-- **Requires**: Make the element dependent on certain features, with a corresponding minimum version
+- **Requires**: Make the element dependent on certain features with a corresponding minimum version
 
 You can also enter Power Fx expressions in some properties, creating low-code solutions that make your card more powerful.
 
 ### Formula bar and Power Fx editor
 
-Use the formula bar to enter a Power Fx expression as a property of the selected control; for example, to calculate a value when a button is clicked. The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
+Use the formula bar to enter a Power Fx expression as a property of the selected control (for example, to calculate a value when a button is clicked). The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
 
 > [!NOTE]
-> Some expressions that are supported in Power Apps aren't available for cards. For more information, see [Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
+> Some expressions that are supported in Power Apps aren't available for cards. For more information, go to [Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
 
 ### Play button
 

powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md

@@ -29,7 +29,7 @@ The [Power Fx documentation](/power-platform/power-fx/overview) is the main sour
 
 ## Known limitations of using Power Fx in cards
 
-The following table lists the Power Fx formulas that don't work in cards, or have limitations. All other functions are fully supported.
+The following table lists the Power Fx formulas that don't work in cards or have limitations. All other functions are fully supported.
 
 | Power Fx formula | Supported in cards | 
 |---------|:---:|

powerapps-docs/cards/make-a-card/variables/variables.md

@@ -41,7 +41,7 @@ As an example, you've created a card that counts how many times the user presses
 
     You can't change the name or type of a variable. If you need to change them, create a new variable.
 
-    You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing and debugging and using your variable with Power Automate flows and Power Virtual Agents bots.
+    You can also customize sender options and, under **Additional variable information**, the **Title** and **Description** of the variable. This information may be helpful for testing, debugging, and using your variable with Power Automate flows and Power Virtual Agents bots.
 
     :::image type="content" source="../../media/variables/new-variable.png" alt-text="Screenshot of the New variable window in the card designer.":::
 

powerapps-docs/cards/manage-cards/manage-cards.md

@@ -26,7 +26,7 @@ This section shows you how to manage cards using security roles.
 
 Cards are stored as rows in Dataverse within the **Card** table. Administrators can use [security roles to control who can create, read, and update cards](/power-platform/admin/wp-security-cds#tablerecord-ownership).
 
-For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards.
+For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user won't be able to create cards.
 
 Note that a user will still be able to receive and use cards sent in Teams, regardless of the security role assigned to the user, as those cards are accessed by the Cards for Power Apps service.
 
@@ -57,4 +57,4 @@ This section shows you how to delete a card.
 
 ### Delete a card as the administrator
 
-If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.
+If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We're working on enabling this capability.

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -3,7 +3,7 @@ title: "Create your first component using Power Apps Component Framework in Micr
 description: "Learn how to implement code components using Power Apps component framework"
 ms.author: noazarur
 author: noazarur-microsoft
-ms.date: 05/27/2022
+ms.date: 12/15/2022
 ms.reviewer: jdaly
 ms.topic: article
 ms.subservice: pcf
@@ -65,7 +65,7 @@ To create a new project:
 1. At the terminal prompt, create a new component project by passing basic parameters using the [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init) command.
 
    ```CLI
-    pac pcf init --namespace SampleNamespace --name LinearInputControl --template field
+    pac pcf init --namespace SampleNamespace --name LinearInputControl --template field --run-npm-install
    ```
 
 1. The above command also runs the `npm install` command for you to setup the project build tools.

powerapps-docs/developer/data-platform/appendix-add-license-information-to-your-solution.md

@@ -1,7 +1,7 @@
 ---
 title: "Appendix: Add licensing information to your solution | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This article outlines the required steps to take license service IDs created in Partner Center and add them to the table definitions of your Dataverse solution." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 04/01/2022
+ms.date: 12/14/2022
 author: mikkelsen2000
 ms.author: pemikkel
 ms.reviewer: pehecke
@@ -53,6 +53,8 @@ Use Microsoft Power Platform CLI commands to clone the solution. To clone a solu
     pac solution clone --name <your solution name> --outputDirectory <your chosen output directory>
     ```
 
+You should now have a solution project in the specified output folder. 
+
 ## Create licensing files
 
 To add licensing information to your solution, you need to create two `.CSV` files using the text editor of your choice. The following are the two files that you need to create:
@@ -93,7 +95,6 @@ The plan definition file must include the following columns laid out in the form
 
 **More info URL:** This is a URL where you would like to direct users to get more information about your solution, in the event they run into a license check error.
 
-
 ### Plan mapping file
  
 The plan mapping file must include the following columns laid out in the format shown in the example below: 
@@ -105,8 +106,6 @@ The plan mapping file must include the following columns laid out in the format
 
 **Component name:** The solution component that you would like to restrict access to using license management. This name must match the name of the component in the **Name** column in the Power Apps solution viewer (image above).
 
-
-
 Once you have created your own licensing CSV files, the next step is to add the information from these files to your solution. 
 
 ## Add licensing information
@@ -125,11 +124,23 @@ To add the license information from the CSV files (created above) to the solutio
 
 ## Build the solution and create an AppSource package
 
-1. To build a solution, see [Create a managed solution for your app](/powerapps/developer/data-platform/create-solution-app-appsource). 
+1. To create the solution zip file, execute the MSBuild command shown below from the project folder. MSBuild is included in Visual Studio installations.
+
+    ```msbuild
+    msbuild /t:build /restore -p:Configuration=Release
+    ```
+
+    The resulting solution zip file can be found in the bin/Release folder of the project.
 
 1. To validate whether the licensing information is included, after the solution is built, look for the licensing information in your solution `customizations.xml` file.
+
+1. Import the unmanaged solution you just built into an environment, and then export it as a managed solution.  
+
+    You may delete the imported solution from the environment afterwards since it is no longer needed. More information: [Import solutions](../../maker/data-platform/import-update-export-solutions.md), [Export solutions](../../maker/data-platform/export-solutions.md)
+
 1. To create the AppSource package, see [Create an AppSource package for your app](/powerapps/developer/data-platform/create-package-app-appsource).
 
 ## See also
 
+[Step 2: Create a managed solution for your app](create-solution-app-appsource.md)  
 [Appendix: App certification checklist](appendix-app-certification-checklist.md)

powerapps-docs/developer/data-platform/create-solution-app-appsource.md

@@ -2,7 +2,7 @@
 title: "Step 2: Create a managed solution for your app (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about how to create a managed solution for your app to include all the components. This is required for publishing an app to Appsource." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 12/20/2019
+ms.date: 12/14/2022
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -20,8 +20,9 @@ search.app:
 
 Create a managed solution to include all the components for your app. You might find these topics helpful as you plan and create a managed solution to package your app components:
 - [Introduction to solutions](introduction-solutions.md)
-- [Plan for solution development](/dynamics365/customer-engagement/developer/plan-solution-development) 
-- [Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)
+- [Create a solution](../../maker/data-platform/create-solution.md)
+
+You can also work with solutions using code: [Create, export, or import an unmanaged solution](/power-platform/alm/solution-api#create-export-or-import-an-unmanaged-solution)
 
 ## Display name and description of your solution
 
@@ -33,6 +34,10 @@ The **Display Name** and **Description** values for a solution are displayed to
 
 ![Solutions.](media/appsource-solution-names.png)
 
+## Export the solution
+
+Proceed with exporting the solution from the environment. When exporting the solution, choose to export as a managed solution. More information: [Export solutions](../../maker/data-platform/export-solutions.md)
+
 ## Supporting data for your solution
 
 If your solution requires supporting or demo data:
@@ -45,7 +50,7 @@ For detailed information about using the Configuration Migration tool to create
 
 ## At the end of this step
 
-You will have a solution file (example: *SampleSolution.zip*) and optionally a demo data file (example: *SampleData.zip*) for your app.
+You will now have a managed solution file (example: *SampleSolution.zip*) and optionally a demo data file (example: *SampleData.zip*) for your app.
 
 **Optional licensing information:** If you wish to add licensing information to your solution, see [Appendix: Add licensing information to your solution](appendix-add-license-information-to-your-solution.md).
 

powerapps-docs/developer/data-platform/dataverse-odata-dataflows-migration.md

@@ -3,7 +3,7 @@ title: Migrate data between Microsoft Dataverse environments using the dataflows
 author: denisem-msft
 ms.reviewer: jdaly
 description: Migrate data between Microsoft Dataverse environments using dataflows OData connector.
-ms.date: 10/03/2022
+ms.date: 12/09/2022
 ms.topic: article
 ms.subservice: dataverse-developer
 ms.author: demora
@@ -197,8 +197,8 @@ You can manually initiate a dataflow by selecting **(...)** in the dataflows lis
 ## Limitations
 
 - Many-to-many relationship data imports are not supported.
-
 - Parent dataflows must be manually configured to run before child dataflows.
+- Mapping to Status and Status Reason fields is currently not supported.  For more field mapping limitations see [Field mapping considerations for standard dataflows > Known limitations](/power-query/dataflows/get-best-of-standard-dataflows#known-limitations)
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]