A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.
Scenario:
First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.
The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.
The solution must provide a worker appointment booking system that can access worker historical job placement data.
First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-virtual-entities

B: Setting a column to Business Required means that the default behavior of a model-driven or canvas app will enforce this requirement in the app.
C: With alternate keys you can now define a column in a Dataverse table to correspond to a unique identifier (or unique combination of columns) used by the external data store. This alternate key can be used to uniquely identify a record in Dataverse in place of the primary key. You must be able to define which columns represent a unique identity for your records. Once you identify the columns that are unique to the table, you can declare them as alternate keys through the customization user interface (UI) or in the code.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-field-portal
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/define-alternate-keys-entity

Reference:
https://docs.microsoft.com/en-us/azure/architecture/data-guide/relational-data/data-warehousing
https://docs.microsoft.com/en-us/powerapps/teams/use-teams-integration-object

1 - The application makes a service call to the datacentar.
2 - The application receives an exception after attempting the service call.
3 - The application redirects calls to an on-premises server.
4 - If the second call is successful, the application continues normally.

Scenario:
Audit teams must have the ability to view worker information on their mobile devices.
Audit teams must be able to record data during visits to locations where workers are placed.
When you create an app, or someone shares an app with you, you can run that app on the Power Apps mobile app or in a web browser.
Reference:
https://docs.microsoft.com/en-us/powerapps/user/run-app-browser
Topic 1, First Up Consulting
Current environment
Existing systems and processes
First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.
The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.
Employee authentication with the existing system is provided by an on-premises Active Directory instance that is linked to Azure Active Directory.
An appointment record is created for each visit with a worker. The record includes worker contact information, preferred language, the date and time of the appointment, and other relevant data. This information is reviewed by the worker's primary recruiter.
First Up has no current capabilities for forecasting future worker needs based on the data held.
Client company visits
Before First Up signs a contract to place workers at a client company, a member of the audit team visits the company and interviews company management. Audit members use different types of devices including Android and iOS devices. First Up has no plans to require the use of a single type of device. Audit team members currently record information about workers on paper forms. Team members enter information from paper forms into the system when they return to the office.
First Up audits client companies at least once each year but may schedule additional visits based on feedback from workers that they place at a client company.
Requirements
General
There is no standardized communication tool across the company, and this causes communication issues between different teams.
First up employees must be able to contact each other by using a secure system to ask and answer questions about medical cases.
Workers must be able to communicate in near real-time with worker support agents.
Client company visits
Audit team records must be locked after they have been reviewed by a First Up manager. No further edits to the record can be carried out. This must be implemented using standard available system functionality.
Audit teams must be able to enter records of their visits to the companies where they have or may place workers. Audit teams must be able to update any necessary records with the latest information.
The solution must support tracking of security clearance information for a worker including the date, status, and certifying agency.
When a worker makes an appointment, the appointments must appear in the timeline for the worker's contact record.
Job history information
The solution must provide a worker appointment booking system that can access worker historical job placement data.
The solution must allow employees to associate a primary recruiter with each worker. The solution must also allow multiple secondary recruiters to be associated with each worker.
Every worker assessment performed must be validated and countersigned by the primary recruiter for a worker.
Job posting data from previous work engagements must be accessible by the Power Platform solution to ensure that new job postings are accurate.
First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.
Worker access
The solution must support workers that speak different languages. The solution must provide automatic translation capabilities.
The solution must support near real-time communications between workers and recruiters.
Workers must be able to view their records online. Workers must be able to enter any additional information that is required by or may be helpful to recruiters.
The solution must provide workers a way to search for general information about available positions.
Workers must be able to request copies of their records by using a chatbot. Workers must be able to provide information to a recruiter as needed.
Data platform
Audit teams must have the ability to view worker information on their mobile devices.
Audit teams must be able to record data during visits to locations where workers are placed.
The solution must support the ability for a corporate governance auditing team to periodically audit the organization's records, policies, and procedures.
Reporting and analytics
The reporting and analytics team must be able to create reports that include data from all facilities and all workers.
Management reports must present an overview of the entire organization. Other reports may be limited to specific offices.
You must create dashboards that show the status across all groups of workers. The dashboards must be embedded into the Power Platform apps. Updates to data must be displayed in near real time.
Security
Authentication for all user types must be managed by a single platform. IT teams must use PowerShell to apply security permissions for users.
Worker records must only be viewed by the recruiting office that the worker visits.
Worker still records must be archived after ten years and are then removed from the main system. Worker information must not be deleted from the system while skill and job placement history records for the worker exist in the system.
User security roles must be customized to ensure that users are able to interact only with the specific data in which they need access.
Workers must be able to sign into a portal by using their own email address. Workers must be required to use a secure method of authentication to be able to view their data.
Alerts regarding the number of recruited and placed at client companies must be updated as background processes.
Issues
The organization reports the following issues:
Recruiters report that they cannot see historical job placement data for workers.
API usage reports show that the number of API calls made exceeds limits. This causes delays saving data.
Users cannot view Power BI reports within the Power Platform apps.
Some security clearance information for workers not visible from within the Power Platform solution.
Audit teams report that they cannot view or edit worker data when the device on which they access the solution does not have network connectivity.
The testing ream reports that one of the canvas apps is not working as expected. An error message displays as specific pages load.