Reference:
https://powerusers.microsoft.com/t5/Building-Flows/How-to-determine-status-code-for-a-condition/td-p/355653
https://blogs.msmvps.com/windsor/2019/04/25/microsoft-flow-error-handling/

Explanation
A: When you import a managed solution, all component changes will be brought into the environment in a published state.
B: You can apply patches to either managed or unmanaged solutions and include only changes to entities and related entity assets. Patches do not contain any non-customized system components or relationships that it dependents upon because these components already exist in the deployed-to organization. At some point in your development cycle, you can roll up all the patches into a new solution version to replace the original solution that the patches were created from.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/import-update-export-solutions
https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates

Scenario: The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups. Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.
Reference:
https://docs.microsoft.com/en-us/dynamics365/field-service/overview
https://us.hitachi-solutions.com/blog/canvas-vs-model-driven-apps/

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/event-framework
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/handle-exceptions

Organization information is stored in the Instance entity of the Discovery service. To see the kind of information contained in that entity, send an HTTP GET request to the service for one of your instances.
GET https://dev.{servername}/api/discovery/v9.0/Instances(UniqueName=’myorg’) Example: Get the details of a specific instance. If you leave out the GUID, all instances that the authenticated user has access to are returned.
GET https://dev.{servername}/api/discovery/v9.0/Instances(<guid>)
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/webapi/discoverurl-organization-web-api

Reference:
https://docs.microsoft.com/en-us/power-automate/run-scheduled-tasks

The version number are <major>.<minor>.<build>.<revision>.
When we create patches in Dynamics 365, the system will automatically increment the build version (you can overwrite the chosen number when you create the patch). For example, if our solution starts at 1.0.0.0, we export it to become 1.0.0.1. We then create a patch, and the version of the patch is 1.0.1.1. If we export it now, it might become 1.0.1.2. In all cases, the build or version number has been incremented. Patches require the build or version number to increment, but not the major or minor version.
Reference:
https://carldesouza.com/how-solution-version-numbers-work-in-the-microsoft-power-platform/

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/define-alternate-keys-entity

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities
https://docs.microsoft.com/en-us/power-platform/admin/database-security
https://docs.microsoft.com/en-us/power-platform/admin/database-security
https://docs.microsoft.com/en-us/power-platform/admin/manage-teams – types-of-teams
https://docs.microsoft.com/en-us/power-platform/admin/manage-teams#types-of-teams

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.
Create and configure Power Apps
Testlet 2
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
Current environment
Adventure Works Cycles wants to replace their paper-based bicycle manufacturing business with an efficient paperless solution. The company has one manufacturing plant in Seattle that produces bicycle parts, assembles bicycles, and distributes finished bicycles to the Pacific Northwest.
Adventure Works Cycles has a retail location that performs bicycle repair and warranty repair work. The company has six maintenance vans that repair bicycles at various events and residences.
Adventure Works Cycles recently deployed Dynamics 365 Finance and Dynamics 365 Manufacturing in a Microsoft-hosted environment for financials and manufacturing. The company plans to leverage the Microsoft Power Platform to migrate all of their distribution and retail workloads to Dynamics 365 Unified Operations.
The customer uses Dynamics 365 Sales. Dynamics 365 Customer Service and Dynamics 365 Field Service.
Retail store information
* Adventure Works Cycle has one legal entity, four warehouses, and six field service technicians.
* Warehouse counting is performed manually by using a counting journal. All warehouse boxes and items are barcoded.
* The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups.
* Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.
* Adventure Works Cycles uses a Power Apps app for local bike fairs to attract new customers.
* A canvas app is being developed to capture customer information when customers check in at the retail location. The app has the following features:
– Customer selects yes or no if they are on the mailing list.
– Customer selects the amount of times they have visited the store.
– Customer selects the type of service needed.
– The search result returns all last name records that match the search term.
Technology
Requirements
* A plug-in for Dynamics 365 Sales automatically calculated the total billed time from all activities on a particular customer account, including sales representative visits, phone calls, email correspondence, and repair time compared with hours spent.
* A shipping API displays shipping rates and tracking information on sales orders. The contract allows for
3,000 calls per month.
* Ecommerce orders are processed in batch daily by using a manual import of sales orders in Dynamics
365 Finance.
* Microsoft Teams is used for all collaboration.
* All testing and problem diagnostics are performed in a copy of the production environment.
* Customer satisfaction surveys are recorded with Microsoft Forms Pro. Survey replies from customers are sent to a generic mailbox.
Automation
* A text message must be automatically sent to a customer to confirm an appointment and to notify when a technician is on route that includes their location.
* Ecommerce sales orders must be integrated into Dynamics 365 Finance and then exported to Azure every night.
* A text alert must be sent to employees scheduled to assist in the repair area of the retail store if the number of repair check-ins exceeds eight.
* Submitted customer surveys must generate an email to the correct department. Approval and follow-up must occur within a week.
Reporting
* The warehouse manager’s dashboard must contain warehouse counting variance information.
* A warehouse manager needs to quickly view warehouse KPIs by using a mobile device.
* Power BI must be used for reporting across the organization.
User experience
* Warehouse counting must be performed by using a mobile app that scans barcodes on boxes.
* All customer repairs must be tracked in the system no matter where they occur.
* Qualified leads must be collected from local bike fairs.
Issues
* Warehouse counting must be performed by using a mobile app that scans barcodes on boxes.
* All customer repairs must be tracked in the system no matter where they occur.
* Qualified leads must be collected from local bike fairs.
Internal
* User1 reports receives an intermittent plug-in error when viewing the total bill customer time.
* User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.
* User2 reports that sales orders have increased.
* User5 receives the error message: ‘Endpoint unavailable’ during a test of the technician dispatch ISV solution.
* The parts department manager who is the approver for the department is currently on sabbatical.
External
* CustomerB reports that the check-in app returned only one search result for their last name, which is not the correct name.
* Nine customers arrive in the repair area of the retail store, but no texts were sent to scheduled employees.
* Customers report that the response time from the information email listed on the Adventure Works Cycles website is greater than five days.
* CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Scenario: A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.
DIFFINDAYS (date and time, date and time): Returns the difference in days between two Date and Time fields. If both dates and times fall on the same day, the difference is zero.
Note: Whenever we talk about history, the bone of contention are the below four fields:
CreatedOn
ModifiedOn
CreatedBy
ModifiedBy
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/define-calculated-fields

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/css
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/html

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