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

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/types-of-fields

Reference:
https://docs.microsoft.com/en-us/azure/event-grid/overview

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/customize-entity-views
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/create-edit-quick-create-forms

The catch statement lets you handle the error.
Syntax: catch(err) {
Block of code to handle errors
}
Reference:
https://www.w3schools.com/js/js_errors.asp
Topic 3, Contoso Pharmaceuticals
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.