Live publish

buck1ey · web-flow · commit a93c86fccb84 · 2023-01-26T11:00:02.000-08:00
diff --git a/powerapps-docs/guidance/fusion-dev-ebook/03-building-low-code-prototype.md b/powerapps-docs/guidance/fusion-dev-ebook/03-building-low-code-prototype.md
@@ -633,7 +633,7 @@ In addition to navigating from the **Home** screen to the other screens in the s
 
 9.  Similarly, add an icon named **IconReturn3** to the **RectQuickActionBar1\_1** control in the **BrowseAppointments** screen.
 
-10. On the **Tree view** pane, select the **App** object. Change the **OnStart** action property to the expression **Navigate(Home, ScreenTransition.Fade)**. This action ensures that the **Home** screen is displayed whenever the app starts:
+10. On the **Tree view** pane, select the **App** object. Change the **StartScreen** property to the expression **Home**. This ensures that the **Home** screen is displayed whenever the app starts:
 
     ![Set App OnStart formula.](media/image74.png)
 
diff --git a/powerapps-docs/maker/common/wrap/code-sign-android.md b/powerapps-docs/maker/common/wrap/code-sign-android.md
@@ -83,7 +83,7 @@ Parameters:
 - **keystore** - the name of the keystore you're using.
 - **openssl** - generates SHA1 key for Android.
 
-Add the generated signature has in the **Redirect URI** while [registering the app](how-to.md#app-registration).
+Add the generated signature hash in the **Redirect URI** while [registering the app](how-to.md#app-registration).
 
 ### Convert SHA1 hex to Base64-encoded signature hash manually
 
diff --git a/powerapps-docs/maker/data-platform/azure-synapse-link-synapse.md b/powerapps-docs/maker/data-platform/azure-synapse-link-synapse.md
@@ -56,11 +56,11 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 
 1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select your preferred environment.
 
-2. On the left navigation pane, select **Data**, select **Azure Synapse Link**, and then on the command bar, select **+ New link to data lake**.
+2. On the left navigation pane, select **Data**, select **Azure Synapse Link**, and then on the command bar, select **+ New link**.
 
     ![Navigate to Power Apps.](media/navigate-to-powerapps.png "Navigate to Power Apps")
 
-3. Select the the **Connect to your Azure Synapse workspace (Preview)** option.
+3. Select the **Connect to your Azure Synapse workspace** option.
 
 4. Select the **Subscription**, **Resource group**, **Workspace name**, and **Storage account**. Ensure that the Synapse workspace and storage account meet the requirements specified in the [Prerequisites](#prerequisites) section. Select **Next**.
 
diff --git a/powerapps-docs/maker/data-platform/export-data-lake-faq.yml b/powerapps-docs/maker/data-platform/export-data-lake-faq.yml
@@ -71,7 +71,6 @@ sections:
      answer: |
         Any table that does not have change tracking enabled will not be supported in addition to following system tables:
         - Attachment
-        - String Map
         - Calendar
    - question: Does Azure Synapse Link support calculated columns?
      answer: |
diff --git a/powerapps-docs/maker/data-platform/migrate-access-datatypes.md b/powerapps-docs/maker/data-platform/migrate-access-datatypes.md
@@ -6,7 +6,7 @@ ms.topic: conceptual
 ms.custom: 
   - model
 ms.reviewer: matp
-ms.date: 01/09/2023
+ms.date: 01/26/2023
 ms.subservice: dataverse-maker
 ms.author: nhelgren
 search.audienceType: 
@@ -67,7 +67,7 @@ In the following table, the data type mappings supported can assist you in plann
 
 ## Access and Dataverse data size comparison
 
-You'll notice some Dataverse columns don't have the same size capacity as Access. As noted above, if a column contains data too large to be migrated, the migration tool alerts the user that the contents can't be migrated. This is to prevent data loss. This decision is not based on the maximum possible size for the column, but rather the size of the actual data in each row.
+You'll notice some Dataverse columns don't have the same size capacity as Access. As noted above, if a column contains data too large to be migrated, the migration tool alerts the user that the contents can't be migrated. This is to prevent data loss. This decision isn't based on the maximum possible size for the column, but rather the size of the actual data in each row.
 
 |Access/Dataverse data type |Access limit  |Dataverse limit  |
 |---------|---------|---------|
@@ -77,8 +77,8 @@ You'll notice some Dataverse columns don't have the same size capacity as Access
 |Date and Time   |  Standard date and time | Standard data and time   |
 |Currency<sup>5</sup>  |  Min/max -922,337,203,685,477/+922,337,203,685,477   |  Min/max -922,337,203,685,477/+922,337,203,685,477   |
 |Decimal Number  | Min/max -10^28-1/+10^28-1 up to 28 decimals   |  Min/max -100,000,000,000/+100,000,000,000 up to 10 decimal places    |
-|Float (Number:Single) | -3.402823E38 to -1.401298E-45 for negative values and 1.401298E-45 to 3.402823E38 for positive values. |Min/max -100,000,000,000/+100,000,000,000 up to 5 decimal places |
-|Float (Number:Double) |-1.79769313486231E308 to -4.94065645841247E-324 for negative values and 4.94065645841247E-324 to 1.79769313486231E308 for positive values.  |Min/max -100,000,000,000/+100,000,000,000 up to 5 decimal places |
+|Float (Number:Single) | -3.402823E38 to -1.401298E-45 for negative values and 1.401298E-45 to 3.402823E38 for positive values. |Min/max -100,000,000,000/+100,000,000,000 up to five decimal places |
+|Float (Number:Double) |-1.79769313486231E308 to -4.94065645841247E-324 for negative values and 4.94065645841247E-324 to 1.79769313486231E308 for positive values.  |Min/max -100,000,000,000/+100,000,000,000 up to five decimal places |
 |Yes/No  |  Boolean   | Boolean   |
 |Int/Whole Number   |  Min/max -2^31/+2^31   | Min/max -2,147,483,647/+2,147,483,647   |
 |Lookup Wizard/ Lookup   | Multiple column return   |  Single column return   |
@@ -134,9 +134,9 @@ To successfully migrate a choice field from Access, the field must be created in
 
 ## Migrate Number:Single and Number:Double columns to Dataverse
 
-Both Access and Dataverse include the ability to store floating point numbers. Access uses `Number:Single` and `Number:Double` for this. These data types are often used for any number column. Dataverse has a **Floating Point Number** data type, but it has some limitations with how it's implemented. Dataverse only allows a maximum of five decimal places. Therefore, there is a danger of losing data when migrating floating point numbers from Access to Dataverse. Because of this possibility of data loss, `Number:Single` and `Number:Double` values can't currently be migrated to Dataverse.
+Both Access and Dataverse include the ability to store floating point numbers. Access uses `Number:Single` and `Number:Double` for this. These data types are often used for any number column. Dataverse has a **Floating Point Number** data type, but it has some limitations with how it's implemented. Dataverse only allows a maximum of five decimal places with a minimum/maximum value of -/+ 100,000,000,000. When migrating, the validator informs you that by migrating this data as a float you'll lose some decimal precision. If that's acceptable, you can migrate the tables automatically. During the migration process any rows that exceed the min/max size limits won't be migrated and will be stored locally in a file in Access just as with any other out of range data type.
 
-However, you can migrate Access `Number:Single` and `Number:Double` data to Dataverse by changing the data type in Access. You can use the Access table designer and change the type of `Number:Single` and `Number:Double` columns to **Decimal**. Then any row that does not exceed the minimum/maximum decimal limits can be migrated.
+However, if you need to migrate but don't want to lose decimal precision, you can migrate Access `Number:Single` and `Number:Double`  by changing the data type in Access. You can use the Access table designer and change the type of `Number:Single` and `Number:Double` columns to **Decimal**, which support up to 10 decimal places in Dataverse. Then any row that doesn't exceed the minimum/maximum decimal limits can be migrated.
 
 ### See also
 
diff --git a/powerapps-docs/maker/model-driven-apps/powerbi-control.md b/powerapps-docs/maker/model-driven-apps/powerbi-control.md
@@ -29,7 +29,7 @@ Add a Power BI report to a model-driven app form using the Power BI report contr
 
 1. In the form designer, select **Components** on the left navigation pane, expand **Power BI**, and then select **Power BI Report**.
 1. Choose from the following properties: 
-   - **Report**. Select the Power BI report that you want displayed on the form.
+   - **Report**. Select the Power BI report that you want displayed on the form. More information: [Create Power BI report and dataset components](create-edit-powerbi-report-dataset-components.md).
    - **Show filter pane**. When **True**, displays the filter pane in the Power BI report.
    - **Expand filter pane by default**. When **True**, expands the filter pane by default.
    - **Save filter updates**. When **True** and someone leaves the report, the filter will be saved and reapplied when the person returns.
