Scenario:
Qualified leads must be collected from local bike fairs.
Adventure Works Cycles uses a Power Apps app for local bike fairs to attract new customers.
By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365, or some other service, which then performs an action in Dynamics 365, or some other service.
In Power Automate, you can set up automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.
Reference:
https://docs.microsoft.com/en-us/power-automate/connection-dynamics365
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.

Access Team template
The privileges assigned to the access team through Access Team Templates. Access Team template allows you to create a template for the entities on which "Access Teams" option is enabled. You can grant or restrict access to the entity records through "Access Rights". Essentially, this is like a record-based security model on an entity record for specific users.
Once the access team template is created and added to the entity form, you can start adding users. For example, on an opportunity record add a new user in the Access Team Template sub-grid.
Reference:
https://community.dynamics.com/crm/b/crmdevmigrationconfigandcustomization/posts/access-teams-and-access-team-templates

Explanation:

Box 1: Site Map validation
When you validate the app, the app designer canvas shows you details about the assets that are missing.
In the app designer, select Validate.
A notification bar appears and shows you whether the app has any errors or warnings. The notification bar shows warnings in cases where, for example, an entity has no forms or views, or the app doesn't contain any components. An error might appear if a site map isn't configured for the app.

Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/validate-app
https://community.dynamics.com/crm/b/crminthefield/posts/monitoring-the-power-platform-canvas-driven- apps---power-apps-analytics

Explanation:

Box 1: Yes
If you are creating an attribute editor you will need to retrieve entity data that has been saved but not published. For other scenarios you will want to only retrieve published metadata.
* Set this value to true to include unpublished changes, as it would look if you called publish.
* Set this value to false to include only the currently published changes, ignoring the changes that haven't yet been published.
Box 2: AttributeMetadata
AttributeMetadata class is returned in the RetrieveAttributeResponse.
Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.messages.retrieveattributerequest.
retrieveasifpublished?view=dynamics-general-ce-9
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.metadata.attributemetadata?view=dynamics- general-ce-9