Explanation
Box 1: Option Set
Box 2: Date only
When team members create tournament records they must enter the start date for a tournament. The end date of the tournament must be automatically calculated.
Box 3: Lookup
Customer information is stored in the Accounts entity. Each tournament record must list the associated sales representative as the tournament owner.
Note: When you create a new lookup column you are creating a new Many-to-One (N:1) table relationship between the table you're working with and the Target Row Type defined for the lookup. There are additional configuration options for this relationship that are described in Create and edit relationships between tables.
But all custom lookups can only allow for a reference to a single row for a single target row type.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/types-of-fields
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 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 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.
