Microsoft PL-400 Korean Actual Free Exam Questions & Community Discussion

Explanation:

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.
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields

Explanation:

Box 1: Change settings in app to preload app
You can optionally preload your app within Teams to increase performance.
Box 2: Change the permission for the custom app in Teams
As an admin, you can use app permission policies to control what apps are available to Microsoft Teams users in your organization. You can allow or block all apps or specific apps published by Microsoft, third-parties, and your organization. When you block an app, users who have the policy are unable to install it from the Teams app store.
You manage app permission policies in the Microsoft Teams admin center. You can use the global (Org-wide default) policy or create and assign custom policies. Users in your organization will automatically get the global policy unless you create and assign a custom policy. After you edit or assign a policy, it can take a few hours for changes to take effect.

Reference:
https://docs.microsoft.com/en-us/powerapps/teams/embed-teams-app
https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:

Step 1: Run pac pcf init -namespace ..
This is the first command which creates basic folder structure of PCF control project.
Run the following command to create the control. The format of the control is:
pac pcf init -namespace <specify your namespace here> -name <put component name here> -template
<component type>
Step 2: Run the npm install command
Install Dependencies
Once 'init' sets up the basic folder, as a next step install all the PCF control dependencies using 'npm install' command.
Example:

Now at this point, there is nothing we have actually created. However, the solution created contains sample PCF control code.
Step 3: Run the following np run build command
Build PCF Component.
Once you implement the PCF component, build the code for any syntax errors.
Syntax:
npm run build

Reference:
https://rajeevpentyala.com/2020/03/21/power-apps-component-framework-pcf-demystify/
https://carldesouza.com/creating-a-custom-component-using-the-powerapps-component-framework/

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation:
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.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/clientapi-form-context
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext- data-process/eventhandlers/addonstagechange
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext- data-process/eventhandlers/addonstagechange