Live publish

Author: buck1ey

.openpublishing.redirection.json

@@ -1,21 +1,26 @@
 {
   "redirections": [
-   {
+    {
+      "source_path": "powerapps-docs/maker/portals/admin/portal-checker-analysis.md",
+      "redirect_url": "/power-apps/maker/portals/admin/portal-checker#next-steps",
+      "redirect_document_id": false
+    },
+    {
       "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/removeOnPostSave.md",
       "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_document_id": false
-   },
-   {
+    },
+    {
       "source_path": "powerapps-docs/developer/data-platform/org-service/metadata-retrieve-detect-changes.md",
       "redirect_url": "../query-schema-definitions",
       "redirect_document_id": false
-   }, 
-   {
+    },
+    {
       "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/getoutput.md",
       "redirect_url": "getoutputs",
       "redirect_document_id": false

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/maker/canvas-apps/connections/connection-oracledb.md

@@ -23,7 +23,7 @@ List tables, and create, read, update, and delete table rows in an Oracle databa
 
 ## Prerequisites
 * Oracle 9 and later
-* Oracle Data Access Client (ODAC) software 11.2 and later
+* Oracle Data Access Client (ODAC) software 11.2 or later
 * Installation of an on-premises data gateway
 * Installation of the Oracle client SDK
 
@@ -33,7 +33,7 @@ To install a gateway, follow the steps in [this tutorial](../gateway-management.
 An on-premises data gateway acts as a bridge, providing quick and secure data transfer between on-premises data (data that isn't in the cloud) and the Power BI, Power Automate, Logic Apps, and Power Apps services. You can use the same gateway with multiple services and multiple data sources. For more information, see [Understand gateways](../gateway-reference.md).
 
 ### Install Oracle client
-On the same computer as the on-premises data gateway, install the [64-bit ODAC 12c Release 4 (12.1.0.2.4) for Windows x64](https://www.oracle.com/technetwork/database/windows/downloads/index-090165.html). You must choose a windows installer version since xcopy version does not work with on-premises data gateway.  Otherwise, an error will appear if you try to create or use the connection, as the list of known issues describes.
+On the same computer as the on-premises data gateway, install ODAC 11.2 or later. For example, you can install [64-bit ODAC 12c Release 4 (12.1.0.2.4) for Windows x64](https://www.oracle.com/technetwork/database/windows/downloads/index-090165.html) or choose a version that you prefer. You must choose a windows installer version since xcopy version does not work with on-premises data gateway.  Otherwise, an error will appear if you try to create or use the connection, as the list of known issues describes.
 
 ## Create an app from a table in an Oracle database
 

powerapps-docs/maker/data-platform/export-data-lake-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: Get answers to frequently asked questions about Power Apps Azure Synapse Link for Dataverse.
   author: sabinn-msft
   ms.search.keywords: 
-  ms.date: 02/10/2021
+  ms.date: 12/15/2022
   ms.author: sabinn
   ms.reviewer: 
   contributors: JasonHQX
@@ -14,6 +14,9 @@ summary: This article provides information on frequently asked questions about e
 sections:
 - name: General
   questions:
+   - question: Can I create, update or delete the data file in the Azure storage manually?
+     answer: |
+        Data files should not be modified by a customer and no customer files should be placed in the data folders. 
    - question: How can I access my table relationships?
      answer: |
         To access many-to-many relationships, the relationship will be available as a table to select from the **Add tables** page for a new link and from the **Manage tables** for a preexisting link.

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

@@ -2,9 +2,8 @@
 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/16/2022
+ms.date: 12/15/2022
 ms.reviewer: "matp"
-
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "how-to"
@@ -402,8 +401,6 @@ The activity rollup type can be configured for timelines on forms for the accoun
 More information on rollup types is available from [RollupType EnumType](/dynamics365/customer-engagement/web-api/rolluptype).
 
 ![Activity rollup type.](media\activity-rollup-type.png "Activity rollup type")
-
-
 
 ### Timeline performance
 
@@ -591,6 +588,10 @@ Power platform administrators can restrict the file size of attachments users ca
 1.	On the **System Settings** dialog, select the **Email** tab, and then scroll down to find the **Set file size limit for attachments** value.
 1.	Enter the desired size limit for attachments, and then select **Save**.
 
+## Known issues
+  
+- 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: [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)
 
 ### See also