updates to power-fx

Author: mduelae

powerapps-docs/maker/data-platform/low-code-plug-ins.md

@@ -278,14 +278,14 @@ For a few examples of how to create a low-code plug-in, go to [Example Dataverse
 - Nested support. Plug-ins can only call first-party actions published by Microsoft from Power Fx expressions.
 - Some `Collect` scenarios require `Patch`. There are some scenarios where `Collect()` doesn't work. The workaround is to use `Patch()` as shown in the populating regarding column example below. If you're creating an automated plug-in, prepend @ to each table referenced in the Power Fx formula.
 
-    ```powerapps-dot
+    ```power-fx
     Patch(Faxes,
         Collect(Faxes, { Subject : "Sub1" } ),
         { Regarding : First(Accounts) }
     )
     ```
 - When low-code plug-ins interact with connectors and DLP is employed, the admin can block creation of connections using DLP. However, existing connection references in the Dataverse environment continue to function. In case the admin needs to block all low-code plug-in interactions with any connectors, they can disable the organization setting `Allowconnectorsonpowerfxactions`. This setting is enabled by default and can be disabled by usual SDK methods (WebAPI, SDK, PowerShell, and so on). You can disable this using a low-code instant plug-in as follows:
-   ```powerapps-dot
+   ```power-fx
    Patch(Organizations, First(Organizations), { 'Enable connectors on power fx actions.': 'Enable connectors on power fx actions. (Organizations)'.No })
    ```
 - Plug-ins that use connectors can only output results from specific fields. Due to this, you need to map specific primitive values from the connector response to output values.

powerapps-docs/maker/data-platform/lowcode-plug-ins-examples.md

@@ -34,15 +34,15 @@ This example uses the [Abs() function](/power-platform/power-fx/reference/functi
 1. Create an `Out` parameter to validate expected behavior that makes sense, such as a string Optionally use input parameters to make testing easier, that makes sense with the formula. 
 1. In the formula editor, wrap the `Out` parameter in curly brackets: 
 
-   ```powerapps-dot
+   ```power-fx
    {Out: "" }
    ```
 
 1. Enter an expression that tests the formula: 
    - Validate that intellisense accepts the formula (text turns light blue).
    - Implement an expression that provides an output to help validate the result, for example.
 
-   ```powerapps-dot
+   ```power-fx
    {Out: "Abs(-5) = 5: " & Text( Abs(-5) = 5 )  }
    ```
 
@@ -60,7 +60,7 @@ Implement server-side input validation, such as duplicate error detection that t
 1. For **Table**, select **Contact**.
 1. For **Run this plugin when the row is**, select **Created**.
 1. In the **Formula** box, enter this formula:
-  ```powerapps-dot
+  ```power-fx
    If( !IsBlank(LookUp([@Contacts],'Last Name'=ThisRecord.'Last Name' && 'First Name'=ThisRecord.'First Name')),
   	  Error("You have existing contacts with the same first name and last name")
   )
@@ -88,7 +88,7 @@ Display specific types of errors using the _ErrorKind_ enumeration.
    - **Run this plugin when the row is**: **Updated**
 1. Enter the formula below:
 
-   ```powerapps-dot
+   ```power-fx
    If(ThisRecord.'Due Date' < Now(), 
    	Error({ Kind: ErrorKind.Validation , Message: "The due date cannot be in the past" })
    );
@@ -136,7 +136,7 @@ Here's an email template example that you can create for the SenMail based data
    - **Run this plugin with the row is**: **Created**
    - **Formula**: Paste the code below into the **Formula** box. For more information abut the SendEmailFromTemplate function, to [SendEmailFromTemplate Action](/power-apps/developer/data-platform/webapi/reference/sendemailfromtemplate?view=dataverse-latest&preserve-view=true ).
 
-     ```powerapps-dot
+     ```power-fx
      XSendEmailFromTemplate(
          LookUp('Email Templates',StartsWith(title,"Order Thank You")).'Email Template',
 	 ThisRecord,
@@ -162,7 +162,7 @@ In-app notifications enable makers to configure contextual, actionable notificat
    - **OrderID**: **String**
    - **TechnicianEmail**: **String**
 1. **Formula**. Paste the following code in the **Formula** box. For more information about this function, go to [SendAppNotification Action](/power-apps/developer/data-platform/webapi/reference/sendappnotification?view=dataverse-latest&preserve-view=true ).
-   ```powerapps-dot
+   ```power-fx
     XSendAppNotification(
     	"New service",
     	LookUp(Users,'Primary Email'=TechnicianEmail),
@@ -187,7 +187,7 @@ In-app notifications enable makers to configure contextual, actionable notificat
 1. Select screen on the left navigation pane, or create a new one.
 1. On the **Insert** menu, add a **Button** to the page using the **Text** *Notify technician*.
 1. Select the button, and enter the following in the **fx** formula bar, where *DataCardValue17* is the column that contains the Order ID, and *DataCardValue15* is the column that contains the technician’s email address. In this example, a canvas app named **Service Order App** is used.
-	```powerapps-dot
+	```power-fx
 	Environment.cr8b8_Notifytechnician1({
            OrderID: DataCardValue17.Text,
 	   TechnicianEmail: DataCardValue15.Text 
@@ -227,7 +227,7 @@ Prerequisites:
 > Use the [With()](/power-platform/power-fx/reference/function-with) function to capture the entire response from one action if you want to access different properties the response might have. In the example below, there's an input parameter `Location` (string) and an output parameter `Out` (string).
 >
 
-```powerapps-dot
+```power-fx
 With({ /* Capture current weather response from connector */
 c: new_MsnWeather.CurrentWeather( Location, "Imperial" ).responses.weather.current
 },{	/* Return concatenated weather details */

powerapps-docs/maker/model-driven-apps/commanding-use-powerfx.md

@@ -58,7 +58,7 @@ To define visibility logic, select the command. Then select **Visibility** on th
 
 ### Patch (update) the current selected record
 
-```powerapps-dot
+```power-fx
 Patch(Accounts, Self.Selected.Item, {'Account Name': "Changed Account name"})
 ```
 
@@ -67,25 +67,25 @@ Patch(Accounts, Self.Selected.Item, {'Account Name': "Changed Account name"})
 > [!NOTE]
 > If the related table is not already in the command component library you'll need to open it in canvas studio and add the data source there.
 
-```powerapps-dot
+```power-fx
 Patch(Tasks,Defaults(Tasks),{Regarding:Self.Selected.Item},{Subject:"Subject of the Task"})
 ```
 
 ### Check and edit a date property
 
-```powerapps-dot
+```power-fx
 If(Self.Selected.Item.'Last Date Included in Campaign'>DateAdd(Now(),-3), Patch(Accounts,Self.Selected.Item,{'Last Date Included in Campaign':Date(2021,10,19)}))
 ```
 
 ### Visible property: Only show the command if one or more records is selected in a grid view
 
-```powerapps-dot
+```power-fx
 CountRows(Self.Selected.AllItems) > 0
 ```
 
 ### Control visibility based on record data
 
-```powerapps-dot
+```power-fx
 //Button will be visible for accounts with Account Rating > 20
 Self.Selected.Item.'Account Rating'>20
 ```
@@ -99,39 +99,39 @@ Self.Selected.Item.'Account Rating'>20
 
 To navigate to a custom canvas page within a model-driven app, pass the page name as the first argument.
 
-```powerapps-dot
+```power-fx
 Navigate( myCustomPage )
 ```
 
 ### Navigate to the default view of the table
 
 To navigate to the default view of the table, pass the table name as the first argument.
 
-```powerapps-dot
+```power-fx
 Navigate( Accounts )
 ```
 
 ### Navigate to specific system view of the table
 
 To navigate to a specific system view of the table, pass the table's `Views` enum.
 
-```powerapps-dot
+```power-fx
 Navigate( 'Accounts (Views)'.'My Active Accounts' )
 ```
 
 ### Navigate to the default form of the table
 
 To navigate to the default form of the table, pass the record as the first argument.
 
-```powerapps-dot
+```power-fx
 Navigate( Gallery1.Selected )
 ```
 
 ### Navigate to the default form of the table in create mode
 
 To navigate to the default form of the table, pass a Dataverse record created from the [Defaults](../canvas-apps/functions/function-defaults.md) function. This opens the default form with the record as a new record. The **Defaults** function takes the table name to create the record.
 
-```powerapps-dot
+```power-fx
 Navigate( Defaults( Accounts ) )
 ```
 
@@ -141,14 +141,14 @@ Use the [**DataSourceInfo** function](/power-platform/power-fx/reference/functio
 
 For example, use **RecordInfo** to determine if the current user has permission to modify a record and appropriately show or hide an "Edit" button using its **Visible** property:
 
-```powerapps-dot
+```power-fx
 EditButton.Visible = 
    RecordInfo( Gallery1.Selected, RecordInfo.EditPermission )
 ```
 
 For example, use **DataSourceInfo** to determine if the current user has permission to create a record and appropriately show or hide a "Create" button using its **Visible** property:
 
-```powerapps-dot
+```power-fx
 CreateButton.Visible = 
    DataSourceInfo( Accounts, DataSourceInfo.CreatePermission )
 ```
@@ -157,7 +157,7 @@ CreateButton.Visible =
 
 Use the [**Confirm** function](/power-platform/power-fx/reference/function-confirm) to display a dialog box on top of the current screen.
 
-```powerapps-dot
+```power-fx
 Notify( Confirm( "Are you sure?", 
                  { ConfirmButton: "Yes", CancelButton: "No" } 
         ) 
@@ -174,7 +174,7 @@ A notification can be shown to app users by calling the [Notify function](../can
 > [!NOTE]
 > `NotificationType.Success` is not currently supported and will result in an informational notification type.
 
-```powerapps-dot
+```power-fx
 Notify( "Model-driven app notification message" )
 ```
 

powerapps-docs/maker/model-driven-apps/page-powerfx-in-model-app.md

@@ -22,14 +22,14 @@ This article outlines how the common [Microsoft Power Fx](../canvas-apps/formula
 
 A notification can be shown to the user in a custom page by calling the [Notify function](../canvas-apps/functions/function-showerror.md).  When the notification messages appear, they're docked above the default page to stay visible until disabled. If a timeout interval is provided, the notification message will disappear after the timeout interval. It is recommended not to use a timeout interval of 10, as this is no longer considered as a timeout interval. More information: [Notify function](../canvas-apps/functions/function-showerror.md).
 
-```powerapps-dot
+```power-fx
 Notify( "Custom page notification message" )
 ```
 
 > [!div class="mx-imgBorder"]
 > ![Custom page notify information message bar](media/page-powerfx-in-model-app/custom-page-notify-information.png "Custom page notify information message bar")
 
-```powerapps-dot
+```power-fx
 Notify( "Custom page notify warning message", NotificationType.Warning )
 ```
 
@@ -48,15 +48,15 @@ The [Navigate function](../canvas-apps/functions/function-navigate.md) allows th
 
 To navigate from one custom page to another, pass the display name of the custom page as the first parameter.
 
-```powerapps-dot
+```power-fx
 Navigate( CustomPage2  )
 ```
 
 ### Navigate to the default view of the table
 
 To navigate to the default view of the table, pass table name as the first parameter.
 
-```powerapps-dot
+```power-fx
 Navigate( Accounts )
 ```
 
@@ -67,23 +67,23 @@ Navigate( Accounts )
 
 To navigate to a specific system view of the table, pass the GUID of the view.
 
-```powerapps-dot
+```power-fx
 Navigate( 'Accounts (Views)'.'My Active Accounts' )
 ```
 
 ### Navigate to the default form of the table
 
 To navigate to the default form of the table, pass the record as the first parameter.
 
-```powerapps-dot
+```power-fx
 Navigate( Gallery1.Selected )
 ```
 
 ### Navigate to a specific form of a table
 
 To pass a Dataverse record to a specific form, pass the form name in the second parameter's Page attribute.
 
-```powerapps-dot
+```power-fx
 Navigate( 
   AccountGallery.Selected, 
   { Page: 'Accounts (Forms)'.Account  } )
@@ -93,7 +93,7 @@ Navigate(
 
 To pass a Dataverse record to a specific custom page, pass the custom page name in the second parameter's Page attribute.
 
-```powerapps-dot
+```power-fx
 Navigate( 
   AccountGallery.Selected, 
   { Page: 'Account Record Page'  } )
@@ -103,7 +103,7 @@ In the target custom page, the record is retrieved using **Param** function to g
 
 Below is an example of loading the record into an **EditForm** control.
 
-```powerapps-dot
+```power-fx
 AccountEditForm.DataSource = Accounts
 AccountEditForm.Item = 
   LookUp( Accounts, accountid = GUID( Param("id") ) )
@@ -113,15 +113,15 @@ AccountEditForm.Item =
 
 To navigate to the default form of the table in create mode, pass a Dataverse record created from the [Defaults](../canvas-apps/functions/function-defaults.md) function. This opens the default form with the record as a new record. The **Defaults** function takes the table name to create the record.
 
-```powerapps-dot
+```power-fx
 Navigate( Defaults( Accounts ) )
 ```
 
 ### Navigate to the default form of the table in create mode with field defaulted
 
 To navigate to a new record with some fields defaulted, use **Patch** function to set fields on the default record for the table. 
 
-```powerapps-dot
+```power-fx
 Navigate(
 	Patch(
 		Defaults(Accounts), { 'Account Name': "My company", Phone: "555-3423" } ) 
@@ -132,7 +132,7 @@ Navigate(
 
 To navigate back to the last page or to close a dialog, the [Back](../canvas-apps/functions/function-navigate.md) function is called in a custom page. The **Back** function closes the current page and returns to the last model-driven app or custom page in the model-driven app. If the custom page has multiple screens, see the article [Navigating back when custom page has multiple screens](#navigating-back-when-custom-page-has-multiple-screens).
 
-```powerapps-dot
+```power-fx
 Back()
 ```