Explanation
Box 1: Connect by using the Dataverse connector from the desktop flow and retrieve the qualification data.
All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface.
Qualification verification
The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified.
A service request can have one or more Qualification records associated with it.
Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete.
When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation's client.
In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place.
Box 2: Send data from the desktop flow to a cloud flow to update the qualification record.
To complete a service request, users perform the following actions:
Send a templated email by using Microsoft Outlook to the client after all qualifications for a service request are checked.
Change the service request status to Completed. Currently, service requests do not indicate when all Qualification records are addressed.

Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests.
Flows with PowerApps steps
Flows that were created via Power Automate in the PowerApps menu or flows that have PowerApps steps added have a different issue then other Power Automate flows. As of the writing of this blog these flows are not able to be imported into another environment. This means that if you create flows with Power Apps steps within them you will need to recreate them in your destination environment.
Topic 3, Bellows College
Overview
Bellows College is a post-secondary school that wants to start a football team. The college uses Microsoft Power Platform to manage its recruiting efforts. The registration team and assistants use model-driven apps. The coaches use canvas apps on their mobile devices.
Prospects are considered underage if they are younger than 18 years old at the time of registration.
Environment
* Custom code is not allowed in the system.
* Server-side synchronization is configured for emails, appointments, contacts, and tasks.
* The database and file storage of Dataverse must be minimized to keep costs low.
Contact table
* Birthdate is a custom date and time field.
* Age at Registration is a calculated Held that displays the age of the prospect at the time of registration.
* Current Age is a calculated field that displays the age of the prospect based on the current date and time.
Evaluation Table
* The Evaluation table is a custom table used to track evaluation criteria.
* Evaluation records cannot be manually created.
* Users must not be able to continue until an evaluation record is created automatically for the prospect.
Consent table
* The consent forms completed by the parents are stored as records in the Consent table.
* Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record.
team website
* The consent forms completed by the parents are stored as records in the Consent table.
* Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record.
Requirements
* The team website is created by using Power Pages.
* A starter layout template was used to create the site.
* The site consists of five pages:
o Home: A page open to everyone to view the announcements from the team, o Schedule: A page open to everyone to view the tryout and game schedule, o Evaluations: A page that displays tracking from the evaluation table.
Prospects are able to view their own information only.
o Forms: A page that displays the consent form,
o Contact Us: A page for anyone to submit questions and comments.
* Two web roles for authenticated users are created: Primary Contact User and Prospect User.
o All primary contacts and prospects are assigned to their respective roles.
Registration
* Parents and prospects are created as contacts and must be linked.
* The registration team must be able to rapidly create prospects without navigating away from the Parents form. Only the First Name, Last Name, and Birthdate fields should be displayed for the team.
* Assistants must be able to update prospect information and add teams that the prospect has previously played on to a subgrid.
Parent consent
* When a prospect is underage, a Primary Contact field will appear. The field must be populated before the prospect record can be saved.
* A view named Underage Prospects that lists all underaged prospects is required.
* The Underage Prospects view must run once a week without requiring modifications to display correct information.
* A consent email must meet the following requirements:
o be sent to the primary contact of each new underage prospect
o contain a link to the team website
o be automatically sent weekly and tracked to the contact record in Dataverse o include the current date using the full month name, date, and year Evaluations
* Coaches rate prospects each day on a scale of 1-10 in three categories: endurance, coordination, and skill.
* The total of the three categories is displayed at the bottom of the form. If the total for the day is greater than 25, the number should appear green.

Explanation
Box 1: Contact table record
In Power Apps portals, each authenticated portal user is associated with a contact record in Microsoft Dataverse.
Box 2: Web roles
Portal users must be assigned to web roles to gain permissions beyond unauthenticated users.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-portal-authentication

Explanation: