Explanation:

Step 1:SelectRegister New Web Hook.
Configure Dynamics 365 Sales to Call Your Webhook in Azure Functions
1. Open the Plug-in Registration Tool and connect to your organization.
2. Select Register->Register New Web Hook

Step 2: Enter the endpoint URL

Step 3: Register a New Step for Create of SalesOrder.
Register a new webhook, and then tie that webhook to an event in Dynamics 365 Sales. Select your newly registered webhook, right-click it, and then choose "Register New Step." Note that the webhook here is set to execute whenever a change to an account record is detected within Dynamics 365 Sales.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/tutorial-write-plug-in

Explanation:
Box 1: store_totaldiscount
If the total discount on an order exceeds 30 percent, a manager must approve the order before the order is fulfilled and delivered.
Box 2: @greater(add(triggerBody()..
When to use triggerBody() ? - When you want to fetch attributes from the body of the trigger.
Reference:
https://d365demystified.com/2020/09/06/using-triggerbody-triggeroutput-to-read-cds-trigger-metadata- attributes-in-a-flow-power-automate/

Explanation:

Box 1: Functions
Box 2: Actions
Box 3: Complex types
Complex types are keyless named structured types consisting of a set of properties. Complex types are commonly used as property values in model entities, or as parameters or return values for operations.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/webapi/web-api-types- operations#complex-types

Explanation:

Box 1: No
There is a read error.
Box 2: No
Note: The Environment Maker role can create resources within an environment including apps, connections, custom connectors, gateways, and flows using Power Automate.
Box 3: Yes
The System Customizer role is similar to the System Administrator role which enables non-system administrators to customize Dynamics 365. A Customizer is a user who customizes entities, attributes and relationships.
Box 4: Yes

Explanation:
https://contoso.crm.dynamics.com/main.aspx?etn=contact&extraqs=param_1%3D&pagetype=entityrecord Box 1: main.aspx Example, to open the Active Contacts view.
https://myorg.crm.dynamics.com/main.aspx?etn=contact&pagetype=entitylist&viewid={00000000-0000-
0000-00AA-000010001004}
Box 2: etn
Etn: The logical name of the entity. Important: Do not use the etc (entity type code) parameter that contains an integer code for the entity. This integer code varies for custom entities in different organizations.
Box 3: Extraqs
Extraqs: Optional for forms. This parameter contains encoded parameters within this parameter.
When you open a new form by using the URL address, you can include arguments in the extraqs parameter to set field values Note: You must encode the parameters passed in the extraqs parameter. To encode the parameters, use encodeURIComponent. To use special characters like "=" or "&" in the parameter values, you must double encode (e.g. to set name to A=B&C, it would be extraqs=name%3DA%253DB%2526C).
Box 4: entityrecord
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/open-forms-views-dialogs-reports- url
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/set-field-values-using-parameters- passed-form