Free PL-400 Exam Dumps Preview

Box 1: Hides the control in the body of the form. The Client API form context (formContext) provides a reference to the form or to an item on the form, such as, a quick view control or a row in an editable grid, against which the current code is executed.

setVisible sets a value that indicates whether the control is visible.

Box 2: Add an event handler to enable a function named TestFunction to run when the business process flow stage changes.

addOnStageChange adds a function as an event handler for the OnStageChange event so that it will be called when the business process flow stage changes.

Requirements. Historical Information Scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.

The execution context defines the event context in which your code executes.

The execution context defines the event context in which your code executes. The execution context is passed when an event occurs on a form or grid, which you can use it in your event handler to perform various tasks such as determine formContext or gridContext, or manage the save event.

The execution context is passed in one of the following ways:

1. Defining event handlers using UI: The execution context is an optional parameter that can be passed to a JavaScript library function through an event handler. Use the Pass execution context as first parameter option in the Handler Properties dialog while specify the name of the function to pass the event execution context. The execution context is the first parameter passed to a function.
2. Defining event handlers using code: The execution context is automatically passed as the first parameter to functions set using code.

References:
https://docs.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/clientapi-execution-context
https://docs.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/execution-context

Box 1: Microsoft flow
Using Microsoft Flow, you can automatically post to Slack when an event happens in Dynamics 365, enabling similar functionality that is available with the Microsoft Yammer integration with third-party collaboration tools.

Box 2: Workflow
Box 3: Business process flow
A business process flow is composed of Stages, and within each stage there are Steps to complete which are fields. In the business process flow heading, a user can see which stage they are at in the process, and which steps they need to complete before they proceed in the process.

Business process flows enable you to require users to complete certain steps before completing the process and if needed you can also allow users to jump stages.

Box 1: PageRule
Website link to the current form

Page Rule
Uses the <PageRule> element. This type of rule checks the URL of the page being displayed. It returns true if the Address matches

Incorrect:
* Value Rule
Uses the <ValueRule> element. Use this rule to check the value of a specific column in the record being displayed in the form. You must specify the Field and the Value to check.

* Entity Rule
Uses the <EntityRule> element. EntityRule allow for evaluation of the current table. This is useful when you define custom actions that apply to the table template instead of for specific tables. For example, you may want to add a ribbon element to all tables except for several specific tables. It is easier to define the custom action for the table template that applies to all tables and then use an EntityRule to filter out those that should be excluded.

The EntityRule also includes an optional context parameter to specify whether the table is being displayed in the form or a list (HomePageGrid).

Box 2: ValueRule
Sum of two form fields

Value Rule
Uses the <ValueRule> element. Use this rule to check the value of a specific column in the record being displayed in the form. You must specify the Field and the Value to check.

Incorrect:
* Selection Count Rule
Uses the <SelectionCountRule> element. Use this kind of rule with a ribbon displayed for a list to enable a button when specific maximum and minimum numbers of records in the grid are selected. For example, if your button merges records, you should make sure at least two records are selected before enabling the ribbon control.

* Custom Rule

Uses the <CustomRule> element. Use this kind of rule to call a function in a JavaScript web resource that returns a Promise (Unified Interface) or boolean (Unified Interface and web client).

References:
https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/define-ribbon-enable-rules

A file column is used for storing file data up to a specified maximum size. A custom or customizable table can have zero or more file columns plus a notes (annotation) collection with zero to one attachment in each note.

References:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/file-attributes

Box 1: DIFFINMINUTES(Created on, Delivery Time) DIFFINMINUTES (date and time, date and time) returns the difference in minutes between two Date and Time columns.

Box 2: Duration

References:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/define-calculated-fields

The @odata.deltaLink Uri returned from the below example can be used to fetch changes in tables. In this example a new account was created and an existing account deleted. The delta link returned from the previous request fetches these changes, as shown in the example below.

{
"@odata.context":"[Organization URI]/api/data/v9.0/$metadata#accounts (name,accountnumber,telephone1,fax)","@odata.deltaLink": "[Organization URI]/api/data/v9.0/
accounts?$select=name,accountnumber,telephone1,fax&$deltatoken=919042%2108%2f22%2f2017%
2008%3a10%3a44","value":[
{
"@odata.etag":"W/\"915244\"",
"name":"Monte Orton",
"accountnumber":null,
"telephone1":"555000",
"fax":"10101",
"accountid":"60c4e274-0d87-e711-80e5-00155db19e6d"

}
]
}

References:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/use-change-tracking-synchronize-data-external-systems

Scenario:
1. Customers report that the response time from the information email listed on the Adventure Works
Cycles website is greater than five days.
2. Microsoft Teams is used for all collaboration.

Microsoft teams support email notifications.

References:
https://support.microsoft.com/en-us/office/manage-notifications-in-teams-1cc31834-5fe5-412b-8edb-43fecc78413d

B: To associate new table records to existing table records, set the value of single-valued navigation properties using the @odata.bind annotation

Example:
var data =
{
"name": "Sample Account",
"[email protected]": "/contacts(465b158c-541c-e511-80d3-3863bb347ba8)"
}

A: For mobile clients in the offline mode, you cannot use the @odata.bind annotation, and instead have to pass a lookup object (logicalname and id) pointing to the target record.

var data =
{
"name": "Sample Account",
"primarycontactid":
{
"logicalname": "contact",
"id": "465b158c-541c-e511-80d3-3863bb347ba8"
}
}

Note Syntax:
Xrm.WebApi.createRecord(entityLogicalName, data).then(successCallback, errorCallback);

entityLogicalName: Logical name of the table you want to create. For example: "account".
Data: A JSON object defining the columns and values for the new table record.

References:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi/
createrecord

Instead use position hierarchy security and define the two departments as positions.

References:
https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security

D: Use OAuth authentication with Microsoft Dataverse OAuth 2.0 is the industry-standard protocol for authorization. After application users provide credentials to authenticate, OAuth determines whether they are authorized to access the resources.

Client applications must support the use of OAuth to access data using the Web API. OAuth enables two-factor authentication (2FA) or certificate-based authentication for server-to-server application scenarios.

OAuth requires an identity provider for authentication. For Dataverse, the identity provider is Azure Active Directory (AAD). To authenticate with AAD using a Microsoft work or school account, use the Microsoft Authentication Library (MSAL).

Note: Since Dataverse users are authenticated using Azure Active Directory, MSAL.js is the supported way to authenticate SPA users.

C: Microsoft Azure Active Directory Authentication Library (ADAL) is a tool in the . NET framework that lets client applications developers authenticate users to an on-premises Active Directory deployment or to the cloud. ADAL will then secure API calls by locating tokens for access.

Note: Azure Active Directory Authentication Library (ADAL) is no longer actively receiving updates and is scheduled to be supported only until June, 2022. MSAL is the recommended authentication library to use for projects.

References:
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/oauth-cross-origin-resource-sharing-connect-single-page-application

When you export a managed solution, it contains all the changes that have been applied for that solution into a file that you can then import into a different Dataverse environment.

References:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/introduction-solutions

Box 1: Yes
The CrmServiceClient.Retrieve(String, Guid, ColumnSet) method issues a retrieve request to CRM

Parameters
EntityName String
Entity name to request

Id Guid ID of the entity to request

ColumnSet ColumnSet
ColumnSet to request

Box 2: No
The numberofemployees column is not updated.
The customersizecode is updated.

Box 3: No
The code is in C#.

In C#: When you perform comparisons with nullable types, if the value of one of the nullable types is null and the other is not, all comparisons evaluate to false except for != (not equal).

References:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient.retrieve
https://stackoverflow.com/questions/15777745/how-does-comparison-operator-works-with-null-int

References:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/walkthrough-register-app-azureactive-directory

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.

Getting User Details To Use In Power Virtual Agents In Teams After enabling the Authentication, you will now have access to Two variables, bot.UserDisplayName bot.UserId

References:
https://powerusers.microsoft.com/t5/Power-Virtual-Agents-Community/Getting-User-Details-To-Use-In-Power-Virtual-Agents-In-Teams/ba-p/744934

Box 1: No.
An alternate key is needed, not a new field for the record identifier.

Box 2: Yes
The specified key attributes are not a defined key for the account entity.

Name: EntityKeyNotDefined
Message: The specified key attributes are not a defined key for the {0} entity

Box 3: Yes
One way to create an entity is by using the UpsertRequest class. An upsert will create a new entity when there is no existing record that has the unique identifiers included in the entity passed with the request.

Box 4: No

References:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/org-service/web-service-error-codes
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/org-service/entity-operations-update-delete#use-upsert

Box 1: Display Rule
When configuring ribbon elements, you can define specific rules to control when the ribbon elements will display.

Box 2: Action
Define the actions to be performed by a command bar or ribbon control in a <CommandDefinition> element together with rules that control whether the control is enabled or visible in the ribbon.

Box 3: Enable Rule
When configuring ribbon elements, you can define specific rules to control when the ribbon elements are enabled.

Box 1: Decimal
Latitudes range from -90 to +90 (degrees), so DECIMAL is ok.

Decimal - Up to 10 decimal points of precision can be used for values between -100,000,000,000 and - 100,000,000,000 can be in this column. You can specify the level of precision and the maximum and minimum values.

Note: of-type-group - In some cases, we will need to configure a property that may be of different types (Eg: You need to configure a property with a Decimal or whole number CRM field in such cases you can use type-group).

of-type-group - Name of the type-group as defined in manifest.

The list of property types that can be created are Whole.None, TwoOptions, DateAndTime.DateOnly, DateAndTime.DateAndTime, Decimal, Enum, FP,
Multiple, Currency, OptionSet, SingleLine.Email, SingleLine.Text, SingleLine.TextArea, SingleLine.URL,
SingleLine.Ticker, SingleLine.Phone

Incorrect:
* Whole.None - This option simply displays a number.

* Floating point
No such option. There is FP - Up to 5 decimal points of precision can be used for values between - 100,000,000,000 and -100,000,000,000 can be in this column. You can specify the level of precision and the maximum and minimum values.

Box 2: Web API
uses-feature indicates which feature the code components want to use.

Web API provides properties and methods to use Web API to create and manage records.
Available for Model-driven apps, canvas apps, & portals.
Available for Model-driven apps, canvas apps, & portals.

Incorrect:
* Client is not an option.
* Utility provides a container for useful methods.
It is available for Model-driven apps.

References:
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/manifest-schema-reference/property
https://blog.magnetismsolutions.com/blog/jaredjohnson/2019/09/27/new-uses-feature-manifest-element-in-powerapps-component-framework-controls
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/reference/webapi
https://docs.microsoft.com/en-us/power-apps/developer/component-framework/reference/utility

Box 1: Webhook
With Dataverse, you can send data about events that occur on the service to a web app by using webhooks. A webhook is a lightweight HTTP pattern for connecting web APIs and services with a publish-and-subscribe model. Webhook senders notify receivers about events by making requests to receiver endpoints with some information about the events.

Webhooks enable developers and ISVs to integrate Dataverse data with their own custom code hosted on external services.

Box 2: Azure Service Bus
Service Bus provides a secure and reliable communication channel between Dataverse runtime data and external, cloud-based line-of-business apps. This capability is especially useful in keeping disparate Dataverse systems or other Dataverse servers synchronized with business data changes.

Box 3: Azure Event hub
Azure Event Hubs is a big data streaming platform and event ingestion service. It can receive and process millions of events per second. Data sent to an event hub can be transformed and stored by using any real-time analytics provider or batching/storage adapters.

Note: The most popular approaches in Dataverse involve webhooks, Azure messaging (Service Bus, Event Hubs), Azure Logic Apps, or Power Automate.

References:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/why-cds-any-type-app

Step 1: Add another step to the business process flow.
Configure custom controls on a related entity form

In this version of the preview, the easiest way to add custom controls to a BPF is to begin by adding them to a form of the entity that the BPF stage is defined on.

In our example, the Budget Amount and Decision Maker steps of the Qualify stage are defined on the Lead entity. We begin by adding these fields to the Lead main form, and then configure the radial knob and flip switch custom controls for them.

Step 2: Open the business process in the Business Process Flow designer and select Activate/Update.
Generate and export the BPF form

To generate the form for a business process you want to add custom controls to, open the business process in the BPF designer and click on Activate/Update.

Step 3: Copy custom control configurations to the business process flow FormXML for the related entity form.
Copy custom control configurations to the BPF FormXML

To add custom controls to the BPF, we begin by copying the custom control configurations from the Lead entity form that we just exported. To do this, we begin by viewing the FormXML for the Lead entity form, which can be found in the 'customizations' file in the solution zip file.

Step 4: Import the solution into Dataverse.
Import customizations into the CDS (aka Dataverse) environment

Now that we're done making our changes, save the customizations.xml document and add it to the managed solution zip file containing the BPF, replacing the file within it.
Next, import these changes into your CDS environment by going to the Solutions tab in the PowerApps portal and click 'Import'.

References:
https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Preview-Custom-Controls-in-Business-Process-Flows/ba-p/263237

Box 1: Yes
We see the code:
If (!service.IsReady)
{
Console.WriteLine(service.LastCrmError);
Etc.

Box 2: Yes
We see ["SupressDuplicationDetection"] = false for account creation, but not for contact creation

Box 3: No

Before you are able to run it, make sure you have the proper Security Roles in your Microsoft Dataverse environment. Two of the required permissions are Export Customizations and Solution Checker.
References:
https://learntoinspire.ca/2020/01/18/leveraging-the-power-of-solution-checker/

Instead use asynchronous communication.

References:
https://www.tpein.dk/?page_id=210

Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers' accessing data outside of their business units.
However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.

Note: The hierarchy security model is an extension to the existing security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models. The hierarchy security offers a more granular access to records for an organization and helps to bring the maintenance costs down.

References:
https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security

References:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/introduction-solutions

Need a plug-in or a custom workflow.

Note: Plug-ins are one of two methods used to initiate posting the message containing the data context to the Azure Service Bus, the other method being a custom workflow activity.

References:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/azure-integration

References:
https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/transfer-solution#example-procedure-part-3-import-a-solution

Box 1: associate

Box 2: contact
Customers are allowed to add up to three countries/regions to their travel preferences from the website.
Their preferences must be stored in the Contact entity.

Box 3: country

Box 4: synchronous

Box 1: EntityReference
Lookup

Associate table rows on create
You can associate any new row with an existing row when you create it in the same way you would when updating it. You must use an EntityReference to set the value of a lookup column (attribute).

This lookup assignment is the same for both early and late-bound styles.

//Use Entity class with entity logical name var account = new Entity("account");

// set attribute values
//string primary name
account["name"] = "Sample Account";

Guid primarycontactid = new Guid("e6fa5509-2582-e811-a95e-000d3af40ae7");

account["primarycontactid"] = new EntityReference("contact", primarycontactid);

//Create the account
Guid accountid = svc.Create(account);

Box 2: OptionSetValueCollection
Choices

Dataverse, Choices columns
Customizers can define a column that allows selection of multiple options. The MultiSelectPicklistAttributeMetadata class defines a column type that inherits from the EnumAttributeMetadata class. Just like the PicklistAttributeMetadata class, this column includes an OptionSetMetadata.Options property that contains the valid options for the column. The difference is that the values you get or set are an *OptionSetValueCollection* type that contains an array of integers representing the selected options. Formatted values for this column are a semi-colon separated string containing the labels of the selected options.

Note: Create choices with code
The easiest way to create choices is to use the column editor in the customization tools. More information: How to create and edit columns

But if you need to automate creation of this kind of column you can use C# code like the following with the SDK for .NET that creates choices to allow choices of outdoor activities to the contact table. More information: Create columns private const int_languageCode = 1033; //English

MultiSelectPicklistAttributeMetadata outDoorActivitiesAttribute = new MultiSelectPicklistAttributeMetadata()
{
SchemaName = "sample_OutdoorActivities",
LogicalName = "sample_outdooractivities", DisplayName = new Label("Outdoor activities", _languageCode),
RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None), Description = new Label("Outdoor activities that the contact likes.", _languageCode), OptionSet = new OptionSetMetadata()
{
IsGlobal = false,
OptionSetType = OptionSetType.Picklist, // Picklist
Options = { new OptionMetadata(new Label("Swimming",_languageCode),1),
new OptionMetadata(new Label("Hiking",_languageCode),2), new OptionMetadata(new Label("Mountain Climbing",_languageCode),3),
new OptionMetadata(new Label("Fishing",_languageCode),4), new OptionMetadata(new Label("Hunting",_languageCode),5),
new OptionMetadata(new Label("Running",_languageCode),6), new OptionMetadata(new Label("Boating",_languageCode),7),
new OptionMetadata(new Label("Skiing",_languageCode),8), new OptionMetadata(new Label("Camping",_languageCode),9)}
}
};

CreateAttributeRequest createAttributeRequest = new CreateAttributeRequest
{
EntityName = "contact",
Attribute = outDoorActivitiesAttribute
};

var response = (CreateAttributeResponse)service.Execute(createAttributeRequest);

Step 1: Create a new component in the department app.
First create a new component.

Step 2: Create a connection to the engineering issues list and retrieve the total number of critical issues Retrieve the required data.

Step 3: Create an output parameter and set the value of the parameter to the total number of critical issues.

Custom properties
A component can receive input values and emit data if you create one or more custom properties.
Output property is used to emit data or component state. For example, the Selected property on a Gallery control is an output property. When you create an output property, you can determine what other controls can refer to the component state.

Step 4: Import the counter component in the other apps from the first department app
Use the new component in your apps.

References:
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/create-component

With the Common Data Service connector, you can create Power Automate flows that are initiated by create and update events within Dataverse. Additionally, you can perform create, update, retrieve, and delete actions on records within Dataverse.

You can use scopes to determine if your flow runs if you create a new record, if a new record is created by a user within your business unit, or if a new record is created by any user in your organization.

References:
https://docs.microsoft.com/en-us/power-automate/connection-cds

Share the flow and the custom connector with users.

B: Share a custom connector in your organization.
If you have a custom connector, you might want to enable other people to use it. People within your organization can use the custom connector just like they use other Microsoft-managed connectors.

C: Also share the flow.

References:
https://docs.microsoft.com/en-us/connectors/custom-connectors/share

https://netwoven.com/dynamics-365/quick-steps-to-replicate-data-from-dynamics-365-online-to-azure-sql-database/

Box 1: Set the test environment security group to TestSG and assign test users the app security role.
PowerApps apps use role-based security for sharing. The fundamental concept in role-based security is that a security role contains privileges that define a set of actions that can be performed within the app. All app users must be assigned to one or more predefined or custom roles.

Box 2: Assign the manager the app security role.

Box 3: Set the production environment security group to TestSG

Box 4: Add all users in the department to the TestSG security group.

References:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/share-model-driven-app

Box 1: 1
The css order element is the order in which the CSS files should load.

Box 2: 1
The html order element is the order in which the HTML files should load.

You can create a Single-Page Application (SPA) which uses JavaScript to work with Microsoft Dataverse (Common Data Service) data. To provide this, Cross-Origin Resource Sharing (CORS) is enabled so that your SPAs can bypass browser restrictions that normally prevent requests that cross domain boundaries.

References:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/oauth-cross-origin-resource-sharing-connect-single-page-application

Step 1: Select the Search Company custom connector in the Microsoft Flow portal under Custom connectors and select edit.
Login to the Microsoft Flow portal, and on right top corner click on the settings icon and then click on custom connectors option.

Step 2: Select the Definition tab Policy template are available only for custom connectors. To use a policy template, open Power Automate portal and either create a new custom connector or edit an existing one.

In the custom connector wizard, select the Definition page.
From the Definition page, select New Policy.Etc.

Step 3: Select New Policy

Step 1: Select a test suite

Step 2: Select Copy play link

Playing tests in a browser
You can copy a link to play a test in separate browser outside Test Studio. It helps integrate your tests in a continuous build and release pipeline such as Azure DevOps.

The play link for the selected test is persisted. It doesn't change for the test suite or test case. You can update your tests without the need to modify build and release processes.

To play tests in your browser:

1. Select a test suite or test case in the right pane.
2. Select Copy play link.
3. You're prompted to publish your tests if there are any unpublished changes.
4. You can select to skip the publish process and copy the play link. New test changes don't play if you skip.
5. Open a browser and paste the URL into the address bar to play the test.
6. View your test playing back.

Step 3: Publish the test

Step 4: Open a browser and paste the URL for the app inte the address bar

References:
https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-test-studio

Maximum number of processes, stages, and steps: To ensure acceptable performance and the usability of the user interface, there are some limitations you need to be aware of when you plan to use business process flows:
1. Multi-entity processes can contain no more than five entities. There can be no more than 10 activated business process flow processes per entity.
2. Each process can contain no more than 30 stages.

References:
https://docs.microsoft.com/en-us/power-automate/business-process-flows-overview

There are two steps to set up security permissions for a column.

1. Enable column security on one or more columns for a given table.
2. Associate one more existing security profiles, or create one or more new security profiles to grant the appropriate access to specific users or teams.

References:
https://docs.microsoft.com/en-us/power-platform/admin/set-up-security-permissions-field

Box 1: Yes
LoadData and SaveData combine to form a simple mechanism to store small amounts of data on a local device. By using these functions, you can add simple offline capabilities to your app.

Box 2: No

Box 3: No

Box 4: Yes

Step 1: Entity followuptask = new Entity("task");
Followuptask["subject"] = "Send e-mail to the new customer";
Followuptask["regardingobjectid"] = account.ToEntityReference();

The Entity.ToEntityReference method gets an entity reference for this entity instance.

Example

RetrieveRequest request = new RetrieveRequest
{
Target = account.ToEntityReference(),
ColumnSet = new ColumnSet(),
RelatedEntitiesQuery = new RelationshipQueryCollection()
};

Incorrect:
* Entity followuptask = new Entity("task");
Followuptask["subject"] = "Send e-mail to the new customer";
Followuptask["regardingobjectid"] = account;

Step 2: Entity account = (Entity)context.InputParameters["Target"];
Setup the input parameters.

Example:
The plug-in will create a task activity that will remind the creator of the account to follow up one week later.

// Create a task activity to follow up with the account customer in 7 days.
Entity followup = new Entity("task");

followup["subject"] = "Send e-mail to the new customer.";
followup["description"] =
"Follow up with the customer. Check if there are any new issues that need resolution.";
followup["scheduledstart"] = DateTime.Now.AddDays(7);
followup["scheduledend"] = DateTime.Now.AddDays(7);
followup["category"] = context.PrimaryEntityName;

// Refer to the account in the task activity. if (context.OutputParameters.Contains("id"))
{
Guid regardingobjectid = new Guid(context.OutputParameters["id"].ToString());
string regardingobjectidType = "account";

followup["regardingobjectid"] =
new EntityReference(regardingobjectidType, regardingobjectid);
}

// Create the task in Microsoft Dynamics CRM.
tracingService.Trace("FollowupPlugin: Creating the task activity.");
service.Create(followup);

Step 3: service.Create(followup);
Create the task.

References:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.entity.toentityreference
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/tutorial-write-plug-in

Because this service requires access to an external Microsoft Azure SQL Database from Dynamics 365 (online), a number of prerequisites must be satisfied before you can successfully access this service including:

Global / Tenant Admin access, or an Azure Key Vault must be provisioned and the setup user must have permissions on Secrets.

References:
https://blog.crgroup.com/dynamics-365-latest-feature-the-data-export-service/

With Azure AD Conditional Access the users are authenticated by Azure Active Directory (Azure AD).

References:
https://docs.microsoft.com/en-us/power-platform/admin/wp-security

Box 1: Conditional access
You can limit access to users with block access by location to reduce unauthorized access. By using Conditional Access policies, you can apply the right access controls when needed to help keep your organization secure and stay out of your user's way when not needed. Conditional Access analyses signals such as user, device, and location to automate decisions and enforce organizational access policies for resources.

Box 2: DLP policy
DLP policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow. Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked.

Box 3: Exfiltration blocking
Email exfiltration controls for connectors Microsoft Exchange enables admins to disable email autoforwards and autoreplies to remote domains for external recipients. Exchange does this by using message-type headers, such as Auto Forward received from Outlook and Outlook on web clients.

Box 1: Lookup
Fields for the doctor's name and phone number must be displayed in the customer record.

Lookup: A field that allows setting a reference to a single record of a specific type of entity.

Box 2: Calculated
Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.

Calculated field: Contains calculations that use fields from the current entity or related parent entities.

Box 3: Text
Field data type: Single Line of Text: This field can contain up to 4,000 text characters. You can set the maximum length to be less than this.
This field has several format options that will change the presentation of the text. These options are Email, Text, Text Area, URL, Ticker Symbol, and Phone.

References:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields

Step 1: Open the app in a browser on the phone.

Step 2: Add the following text to end of the URL for the app: "&monitor=true" You can start a Monitor session from a model-driven app. To do this, append &monitor=true to the end of the URL in the browser.
This displays the Monitor command on the model-driven app global command bar. Select Monitor to open a monitoring session in a new tab.

Step 3: Perform the steps to generate the errors and download the results from Monitor.

Step 4: Open the application in a browser on a laptop computer when they return to the office

References:
https://powerapps.microsoft.com/en-us/blog/monitor-now-supports-model-driven-apps/

PowerApps Portal or CRM Portal don't support Business Rule that apply on the Forms.

A: Business rules defined for a table apply to both canvas apps and model-driven apps if the table is used in the app.

D: PostSave event occurs after the OnSave event is complete. This event is used to support or execute custom logic using web resources to perform after Save actions when the save event is successful or failed due to server errors.

References:
https://docs.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-create-business-rule
https://powerusers.microsoft.com/t5/Power-Apps-Portals/Business-rules-in-a-PowerApps-Portal/td-p/404588

Correct:
* Set the HTTP connection KeepAlive property to false.

* Set the HTTP connection timeout value explicitly to limit how long each connection can remain open

Incorrect:
* Assign the IOrganizationService object to a member variable.
* Register the plug-in step once for each web service request.
* Register the plug-in to run synchronously.
* Send requests to use multiple threads

Note:
* Set the HTTP connection KeepAlive property to false
Set KeepAlive to false when interacting with external hosts in a plug-in Category: Performance
Impact potential: High

Symptoms
If a plug-in makes external web requests and is trying to use KeepAlive on a closed connection, the plug-in will ultimately fail to execute the web request. If the plug-in is registered:

* Synchronously, users may experience:
Unresponsive model-driven apps
Slow client interactions
The browser stops responding

* Asynchronously, plug-in executions may take an extended period of time before failing.

Guidance
In HTTP 1.1, all connections are considered persistent (KeepAlive is true) unless declared otherwise. Due to the fact that plug-ins run in isolation, the Sandbox service translates into them being short-lived executions that generally would not benefit from KeepAlive. To avoid problems with connecting to external services we recommend disabling KeepAlive within plug-ins. If your specific external service would benefit from using persistent sessions for performance reasons, actively send a KeepAlive at an interval of half the idle timeout (30 seconds) to keep the connection from closing.

Problematic patterns
In order to override the default value of KeepAlive for the non-WCF interactions, the approach should be taken to leverage HttpWebRequest to perform the interactions with the web server, but first setting the KeepAlive property to false.

* Set the HTTP connection timeout value explicitly to limit how long each connection can remain open

Power Apps Dataverse, Set Timeout when making external calls in a plug-in Category: Performance

Impact potential: High

Symptoms
If a plug-in makes external web requests that fail to respond quickly, the plug-in will wait for the full default timeout period before failing. This duration may cause a long transaction that can effect other operations. If the plug-in is registered:

Synchronously, users may experience:

Unresponsive model-driven apps
Slow client interactions
The browser stops responding Asynchronously, plug-in executions may take an extended period of time before failing.

Guidance
The default timeout value for .Net Http clients is 100 seconds, just 20 seconds short of the time available for the plug-in to complete. It is best to establish an expected baseline time that a calling service will respond. The longer it exceeds this normal response time, the higher the probability it will ultimately fail. As a performance best practice, it is best to fail quickly rather than allow the default timeout period to expire.
You should control the period that your call to the external service will wait.

The timeout value you should set will depend on the service. For example, if you can monitor the performance of the service you may determine a duration where 99.999% of requests succeed and set your timeout period to that duration with a few seconds buffer. This will prevent the occasional outliers from having an inordinate impact on the performance of your plug-in.

If you are using System.Net.Http.HttpClient Class, you can set the Timeout value explicitly, as shown in this example setting the timeout to 15 seconds.

C#

Copy using (HttpClient client = new HttpClient())

{ client.Timeout = TimeSpan.FromMilliseconds(15000); //15 seconds
client.DefaultRequestHeaders.ConnectionClose = true; //Set KeepAlive to false

Etc.

Configure an event handler
The following procedure describes how to configure an event handler for a form.

1. Sign in to Power Apps, open the table that you want, and then open the form in the form designer where you want to configure an event handler.
2. Depending on the library state, choose from the following...
3. On the Events tab, select Event Handler and complete the following information to configure the form event, and then select Done:

* Event Type:
On Save: When a record is saved after a form field change.
On Load: When the form opens.

* Library: The JavaScript web resource.
* Etc.

References:
https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/configure-event-handlers-legacy

Box 1: Lookup
The LookUp function finds the first record in a table that satisfies a formula. Use LookUp to find a single record that matches one or more criteria.
Besides the normal formula operators, you can use the in and exactin operators for substring matches.

[!INCLUDE [record-scope]../../includes/record-scope.md)]

Example:
Filter(IceCream, OnOrder > 0) - Returns records where OnOrder is greater than zero.

Box 2: Global choice and Lookup

Box 3: Global choice
A choice column provides a list of values for users to pick from. They help streamline data entry in turn ensuring clean data. There are two types - local and global. Local choices can are local to the table and column that they are created for. They cannot be reused on other tables. For example, a list of statuses for an application may not apply anywhere else (e.g. Submitted, In Review, Approved, Rejected). On the other hand, global choices are available across all tables and columns allowing them to be reused.

References:
https://docs.microsoft.com/en-us/power-platform/power-fx/reference/function-filter-lookup
https://thepoweraddict.com/how-to-work-with-choice-columns-in-dataverse/