Merge remote-tracking branch 'origin/main' into matp-2561253

Author: Mattp123

powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md

@@ -72,7 +72,7 @@ After you enable the Power Apps component framework feature in your environment,
    > [!div class="mx-imgBorder"]
    > ![Insert components.](media/insert-code-components-using-get-more-components.png "Insert components")
 
-4. Select the **Code** tab, select a component from the list, and then select **Import**.<!--note from editor: Here and in step 5, I deleted "sample" because maybe the reader is adding a component they truly want, not necessarily a sample.-->
+4. Select the **Code** tab, select a component from the list, and then select **Import**.
 
     > [!div class="mx-imgBorder"]
     > ![Import a component.](media/insert-component-add-sample-component.png "Import a component")
@@ -83,9 +83,9 @@ After you enable the Power Apps component framework feature in your environment,
    > ![Add a component.](media/add-sample-component-from-list.png "Add a component")
 
    > [!NOTE]
-   > You can also add components by selecting **Insert** > **Custom** > **Import component**. This option will be removed in a future release, so we suggest using the flow described above.<!--note from editor: Recommend deleting this unless there's a mechanism in place to revisit this topic in tandem with the future release. This is especially not a good candidate for note format, since it draws extra attention to this step that won't work before long.-->
+   > You can also add components by selecting **Insert** > **Custom** > **Import component**. This option will be removed in a future release, so we suggest using the flow described above.
+   > 
 
-<!--note from editor: The following isn't really a step, so I removed the numbering and indent. -->
 On the **Properties** tab, you'll notice the code component properties are displayed. 
 
 > [!div class="mx-imgBorder"]
@@ -107,10 +107,10 @@ On the **Properties** tab, you'll notice the code component properties are displ
 
 ## Update existing code components
 
-Whenever you update the code components and want to see the runtime changes, you need to change<!--note from editor: I don't think "bump" is going to necessarily be well-understood by non-native English readers. Maybe this should be "increase"?--> the `version` property in the manifest file. We recommend that you change the version of the component whenever you make changes.
+Whenever you update the code components and want to see the runtime changes, you need to change the `version` property in the manifest file. We recommend that you change the version of the component whenever you make changes.
 
 > [!NOTE]
-> Existing code components are updated only when the app is closed or reopened in Power Apps Studio. When you reopen the app, it asks you to update the code components. Simply deleting or adding code components back into the app won't update the components.
+> Existing code components are updated only when the app is closed or reopened in Power Apps Studio. When you reopen the app, it asks you to update the code components. Simply deleting or adding code components back into the app won't update the components. Publish all the customizations in the updated solution first, otherwise updates made to the code component won't appear.
 
 ### See also
 
@@ -119,4 +119,4 @@ Whenever you update the code components and want to see the runtime changes, you
 [Learn Power Apps component framework](/learn/paths/use-power-apps-component-framework)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/component-framework/reference/formatting.md

@@ -39,6 +39,7 @@ Model-driven and canvas apps
 | [formatUTCDateTimeToUserDate](formatting/formatUTCDateTimeToUserDate.md)     | [!INCLUDE [formatUTCDateTimeToUserDate-description](formatting/includes/formatUTCDateTimeToUserDate-description.md)]     |
 | [formatTime](formatting/formattime.md)                                       | [!INCLUDE [formattime-description](formatting/includes/formattime-description.md)]                                       |
 | [getWeekOfYear](formatting/getweekofyear.md)                                 | [!INCLUDE [getweekofyear-description](formatting/includes/getweekofyear-description.md)]                                 |
+| [parseDateFromInput](formatting/parseDateFromInput.md)                       | [!INCLUDE [parseDateFromInput-description](formatting/includes/parseDateFromInput-description.md)]                       |
 
 ## Example
 

powerapps-docs/developer/component-framework/reference/formatting/includes/parseDateFromInput-description.md

@@ -0,0 +1 @@
+Returns parsed string as date.

powerapps-docs/developer/component-framework/reference/formatting/parseDateFromInput.md

@@ -0,0 +1,45 @@
+---
+title: parseDateFromInput | Microsoft Docs
+description: Returns parsed string as date.
+keywords:
+ms.author: nabuthuk
+author: Nkrb
+manager: kvivek
+ms.date: 01/05/2022
+ms.service: "powerapps"
+ms.suite: ""
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+ms.assetid: 148964b5-106e-4f2e-8038-9086d29dc54f
+---
+
+# parseDateFromInput
+
+[!INCLUDE [parseDateFromInput-description](includes/parseDateFromInput-description.md)]
+
+## Syntax
+
+`context.formatting.parseDateFromInput(input, controlAttributes);`
+
+## Available for
+
+Model-driven and canvas apps
+
+## Parameters
+
+| Parameter Name | Type                                           | Required | Description   |
+| -------------- | ------------------ | -------- | ------------------------------- |
+| input          | `string`                                       | Yes      | User input.  |
+| behavior       | [`ControlAttributes`](../Controlattributes.md) | Yes      | `controlAttributes` control attributes used by the formatter. |
+
+## Return Value
+
+Type: `Date`
+
+### Related topics
+
+[Formatting](../formatting.md)<br/>
+[Power Apps component framework API reference](../../reference/index.md)<br/>
+[Power Apps component framework overview](../../overview.md)
+
+[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/event-framework.md

@@ -65,7 +65,7 @@ $filter=iscustomprocessingstepallowed eq true and isvisible eq true)
 ```
 
 > [!TIP]
-> You can export this data to an Excel worksheet using this query and the instructions provided in this blog post: [Find Messages and tables eligible for plug-ins using the Dataverse](https://powerapps.microsoft.com/blog/find-messages-and-entities-eligible-for-plug-ins-using-the-data-platform/)
+> You can export this data to an Excel worksheet using this query and the instructions provided in this blog post: [Find Messages and tables eligible for plug-ins using the Dataverse](https://powerapps.microsoft.com/blog/find-messages-and-entities-eligible-for-plug-ins-using-the-common-data-service/)
 
 
 You can also use the following FetchXML to retrieve this information. The [FetchXML Builder](https://fxb.xrmtoolbox.com) is a useful tool to execute this kind of query.

powerapps-docs/maker/canvas-apps/mixed-reality-component-measure-distance.md

@@ -6,7 +6,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 3/25/2021
+ms.date: 01/03/2021
 ms.subservice: canvas-maker
 ms.author: anuitz
 search.audienceType: 
@@ -16,12 +16,13 @@ search.app:
 contributors:
   - tapanm-msft
   - anuitz
+  - Alex-MSFT
 ---
 # Take measurements in mixed reality
 
-You can use the **Measure in MR** control in your app to let users measure distance, area, and volume. During measurement, you create two-dimensional and three-dimensional polygons that can be used to confirm how a certain-sized object would fit within a space.
+You can use the **Measure in MR** control in your app to let users measure distance, area, and volume. During the measurement, you create two-dimensional and three-dimensional polygons that can be used to confirm how a certain-sized object would fit within a space.
 
-The control creates a button in your app. When app users click the button, it shows a live camera feed of the device. App users can then identify a starting point and then individual points to measure from. The distances of measured segments are shown directly on the live camera feed.
+The control creates a button in your app. When app users select the button, it shows a live camera feed of the device. App users can then identify a starting point and then individual points to measure from. The distances of measured segments are shown directly on the live camera feed.
 
 
 :::image type="content" source="./media/augmented-overview/measure-in-mixed-reality.png" alt-text="Photo showing a corner between two construction walls being measured with a mobile device.":::
@@ -49,7 +50,7 @@ With an app open for editing in [Power Apps Studio](https://create.powerapps.com
 :::image type="content" source="./media/augmented-measure/augmented-measure.png" alt-text="Select Measure in MR.":::
 
 
-You can modify the control with a number of properties.
+You can modify the control with many properties.
 
 
 ### Properties
@@ -58,7 +59,7 @@ The following properties are on the control's **Measure in MR** pane on the **Pr
 
 :::image type="content" source="./media/augmented-measure/augmented-measure-properties.png" alt-text="The Measure in MR pane.":::
 
-Note that some properties are only available under **More options** in the **Advanced** tab on the **Measure in MR** pane.
+Some properties are only available under **More options** in the **Advanced** tab on the **Measure in MR** pane.
 
 Property | Description | Type | Location
 | - | - | - | -
@@ -67,8 +68,10 @@ Measurement type | What type of measurement the user can make, whether point-to-
 Box Draw | Lock captured measurements to rectangular shapes by specifying only a width and a depth. | Boolean | **Properties** (also in **Advanced**)
 Expected Measurements (Items) | Data source (table) that lists a predefined set of measurements that you want the user to capture during a single session. You can map the labels you want to use for each measurement by using the _ItemsLabels_ property. | Not applicable | **Properties** (also in **Advanced**)
 ItemsLabels  | A column in _Items_ with the strings you want to use as the labels for the measurements you want users to capture. | ColumnName | **Advanced**
-Measurements | Table describing the measured distances, volumes and areas, composed of:<ul><li>Label - String that identifies the given measurement</li><li>Id - Number that uniquely identifies this measurement</li><li>Units - String describing the base unit of this measurement</li><li>Height - Number representing the height of the captured volume, or 0 if not a completed volume or 2D area</li><li>Length - Number representing the total length of the perimeter or path of the measurement </li><li>BoundingWidth - Number representing minimum width in units that bounds the shape </li><li>BoundingDepth - Number representing the minimum depth in units that bounds the shape  </li><li>Area - Number representing the estimated area of the enclosed shape in units squared </li><li>Volume - Number representing the estimated volume of the enclosed shape in units cubed </li><li>Segments - Table describing all segments in the given measurement object with the following properties:<ul><li>Length - Number representing the total distance of a given segment in the given units of measure (for example, .52)</li><li>DirectionX - Number specifying the X direction of the segment in world space (for example, 0.5)</li><li>DirectionY - Number specifying the Y direction of the measurement in world space (typically 0)</li><li>DirectionZ - Number specifying the Z direction of the measurement in world space (for example, 0.5)</li></ul></li></ul> | Table | Not applicable (output property only)
-Photos | The photos captured during the mixed reality session.<br/>You can [upload the mixed-reality photos to OneDrive and show them in a gallery](mixed-reality-take-upload-photos.md). | Not applicable | Not applicable (output property only)
+ItemsMeasurementType  | (Optional) A column in _Items_ with strings that specify the measurement type overrides (distance, area, volume, freeform, or blank)  for the measurements you want users to capture.  | ColumnName | **Advanced**
+ItemsBoxDraw	| (Optional) A column in _Items_ that specifies the Box Draw overrides (true, false, or blank) for the measurements you want users to capture. 	| ColumnName | **Advanced**
+Measurements | Table describing the measured distances, volumes, and areas, composed of:<ul><li>Label - String that identifies the given measurement</li><li>Id - Number that uniquely identifies this measurement</li><li>Units - String describing the base unit of this measurement</li><li>Height - Number representing the height of the captured volume, or 0 if not a completed volume or 2D area</li><li>Length - Number representing the total length of the perimeter or path of the measurement </li><li>BoundingWidth - Number representing minimum width in units that bounds the shape </li><li>BoundingDepth - Number representing the minimum depth in units that bounds the shape  </li><li>Area - Number representing the estimated area of the enclosed shape in units squared </li><li>Volume - Number representing the estimated volume of the enclosed shape in units cubed </li><li>Segments - Table describing all segments in the given measurement object with the following properties:<ul><li>Length - Number representing the total distance of a given segment in the given units of measure (for example, .52)</li><li>DirectionX - Number specifying the X direction of the segment in world space (for example, 0.5)</li><li>DirectionY - Number specifying the Y direction of the measurement in world space (typically 0)</li><li>DirectionZ - Number specifying the Z direction of the measurement in world space (for example, 0.5)</li></ul></li></ul> | Table | Not applicable (output property only)
+Photos | The photos captured during the mixed reality session.<ul><li>ImageURI - String indicating the uniform resource identifier (URI) where the saved photo is stored.</li><li>MimeType - String describing the Multipurpose Internet Mail Extensions (MIME) type for the photo (always image/jpeg).</li><li>FileSize - Number describing size of the photo in bytes.</li><li>Label - String that identifies the measurement associated with this photo or "" if unassociated.  This corresponds to the Label property in the returned Measurements Data Set.</li><br/>You can [upload the mixed-reality photos to OneDrive and show them in a gallery](mixed-reality-take-upload-photos.md). | Not applicable | Not applicable (output property only)
 OnMixedRealitySelect | Behavior that is triggered when exiting the MR experience with new results. | Defined action | **Advanced**
 OnChange | Behavior that is triggered when any property on the button is changed. | Defined action | **Advanced**
 
@@ -117,19 +120,19 @@ OnChange | Behavior that is triggered when any property on the button is changed
 
 **[PaddingTop](./controls/properties-size-___location.md)** – The distance between text in a control and the top edge of that control.
 
-**[PressedBorderColor](./controls/properties-color-border.md)** – The color of a control's border when the user taps or clicks that control.
+**[PressedBorderColor](./controls/properties-color-border.md)** – The color of a control's border when the user selects that control.
 
-**[PressedColor](./controls/properties-color-border.md)** – The color of text in a control when the user taps or clicks that control.
+**[PressedColor](./controls/properties-color-border.md)** – The color of text in a control when the user selects that control.
 
-**[PressedFill](./controls/properties-color-border.md)** – The background color of a control when the user taps or clicks that control.
+**[PressedFill](./controls/properties-color-border.md)** – The background color of a control when the user selects that control.
 
 **[TabIndex](./controls/properties-accessibility.md)** – Keyboard navigation order.
 
 **[TextAlignment](./controls/properties-text.md)** – The alignment of the text: **Center**, **Left**, **Right**, or **Justify**
 
 **[Tooltip](./controls/properties-core.md)** – Explanatory text that appears when the user hovers over a control.
 
-**[VerticalAlign](./controls/properties-text.md)** – The ___location of text on a control in relation to the vertical center of that control: **Middle**, **Top**, or **Bottom**
+**[VerticalAlign](./controls/properties-text.md)** – The ___location of text on a control in relation to the vertical center of that control: **Middle**, **Top**, or **Bottom**.
 
 **[Visible](./controls/properties-core.md)** – Whether a control appears or is hidden.
 

powerapps-docs/maker/data-platform/create-edit-configure-settings.md

@@ -25,6 +25,7 @@ Settings are solution components that enable makers and administrators to quickl
   > [!IMPORTANT]
   > - This is a preview feature and may not be available in all regions.
   > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
+  > - This feature is currently available for model-driven apps only.
 
 Settings are made up of three subcomponents: Setting definition, setting environment value, and setting app value.