Explanation:

Topic 5, Northwind Traders
Case study
Background
Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective.
Environment
* The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production.
* Each environment has an application user that can be used for integrations.
* The company must use solutions to perform all customization and configuration deployment.
Data
* Researchers are responsible for creating account records.
* Researchers have permissions on the Account table to create records, read all records, and update records they own.
* A synchronous plug-in runs when an account record is created and could reassign the record to a different user.
* Users must access data as themselves to enforce security and audit changes.
* A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive.
* Researchers have researched only the top 20 percent of account records.
Web API
* The company creates an Azure Function to run a RESTful .NET Web API.
o Data can be retrieved by placing a GET request to the URL https://dataservice-tENVIRONMENTNAIvlEl.
azurewebsites.net/enrich/IDATAID].
# [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data.
# [DATAID] is the new.dataid column in the Account table.
o The Web API response will return a 200 response plus data if the Datald is found. Otherwise, a 404 response is returned.
* Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform.
Custom connector
* The Web API definition used to create The custom connector must be generated based on a low-code technology.
* The URL used by the custom connector must incorporate the current environment name without hardcoding values.
* Errors generated by the custom connector must not cause downstream processes to fail.
* Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers.
Process
* All account records must be updated with data from the Web API once automatically.
* Only account records that contain a Datald should be updated by the Web API.
* Researchers must create Power Automate flows to specify data analysis priority.
* The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors.
Issues
* A tester attempts to connect to the production instance of the Web API with a Datald that should return data.
The tester receives an error stating that the remote name could not be resolved.
* A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment.

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:
Box 1 = northwind_ValidateAddress
Box 2 = Synchronous

Topic 3, Contoso Pharmaceuticals
Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
Contoso Pharmaceuticals manufactures and sells drugs to retail and wholesale pharmacies, hospitals, and research facilities.
The company plans to implement Dynamics 365 Sales and Dynamics 365 Finance.
Current environment
* Contoso maintains a Microsoft Excel workbook that lists all drugs they supply.
* Pharmacies submit order requests through email.
* All information at customer locations is handwritten by customer representatives.
* Contoso uses Cerner, which is a medical industry application that uses a proprietary database.
* Some accounts are referrals from other pharmacies.
* Every pharmacy has its own Dynamics 365 Sales instance.
Requirements
General
Contoso wants to ensure that there is minimal custom code and custom connectors in the system.
Accounts
* Ensure that the names of the pharmacies are synced between the accounting and the customer management systems.
* Account numbers should be entered automatically into the pharmaceutical system that is in a Cerner database and kept in sync.
* When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.
* A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.
* A field named Priority_Trigger must be created to trigger the Priority field.
* A field named Facility type field must be added in order to select whether a customer is a retail pharmacy, wholesale pharmacy, research facility, or hospital.
Users
* UserA must be able to create and publish Power Apps apps.
* UserB must be the owner of all the systems and be able to provide permissions and create all new environments.
* UserC must be able to create apps connected to the systems and update the security roles and entities.
* Pharmacy representatives must only be able to run the apps and access their own records.
* Access to the accounting Power Apps app must be restricted to accounting team members.
* End users must have minimum access to the required systems.
* Only supervisors must be able to view phone numbers in the Accounts form.
* Developers must be able to create new apps for all users.
* Sales users must only have access to their own records.
Reporting
Pharmacy orders must be displayed in four graphs as follows:
* Annual revenue over $100,000
* Annual revenues under $100,000
* Research facilities
* Hospitals
The graphs must be interactive, and users must be able to drill down on any dimension.
Customizations
* Ensure that notifications are sent to the sales team when a lead is added by using Slack.
* Ensure that leads have a review stage added to the sales process.
* Doctors must be manually added to a custom entity named Doctor if the doctor is not listed.
* Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.
* Fields for the doctor's name and phone number must be displayed in the customer record.
* The doctor entered on the customer's record must be validated against doctors that exist in the system.
* The new solution will be sold to other pharmacies for use. The application must not allow changes to be made.
* The solution must be error free so that when it is installed in other environments it does not cause issues.
* A custom mobile app must be created to allow salespeople to add or search by pharmacy name.
* Pharmacy records must be uniquely identified by pharmacy name, address, contact name, and phone number.
* When a pharmacy is added by using the mobile app, the phone number must be validated to be all digits.

Explanation:

Box 1: Add &ribbondebug=true to the end of the application URL.
Scenario: The captions for the New and Save buttons do not render properly on the form.
You can use the an in-app tool called the Command Checker to inspect the ribbon component definitions to help us determine why the button is not rendered correctly.
To enable the Command Checker, you must append a parameter &ribbondebug=true to your D365 application URL. For example: https://yourorgname.crm.dynamics.com/main.aspx?appid=9ab590fc-d25e-ea11-a81d-
000d3ac2b3e6&ribbondebug=true
Box 2: Use the Ribbon Workbench
Adding Buttons to Ribbons
* Download and install Ribbon Workbench.
* Select a suitable ICON for your button.
* Create a solution.
* Edit the button in Ribbon Workbench.
* Publish and test.
Reference:
https://support.microsoft.com/en-us/help/4552163/ribbon-troubleshooting-guide
https://neilparkhurst.com/2015/10/19/adding-buttons-to-ribbons/