This article is contributed. See the original author and article here.
Shine with a Power Apps Challenge for Contoso Estate!
Learn by doing! Join this beginner challenge to develop your Power Platform skills.
Benefits:
– Create a portfolio-worthy project
– Chance to be featured in Power Apps Gallery
– Boost your Power Apps development confidence
About the Challenge:
Contoso (Fictional), a real estate company, needs a Power Apps Developer to automate their Estate Management Operations.
Scenario:
To ensure security, visitors need a passcode to enter the estate. The passcode comprises:
Passcode = Street Unique Shortcode + House Number + Word for the day (randomly generated).
Challenges:
- Costly and time-consuming phone calls for passcode requests
- Delay due to multiple callers
- Security team burnout from handling numerous calls daily
- Human resources needed for this task
Your Task:
Part 1: Create a Dataverse table for the solution.
Part 2: Develop the Power Apps Screen/Screens to meet the following requirements:
- Allow registered residents to access the application
- Generate a passcode with a button click
- Store the randomly generated word of the day in a table
- Display the passcode without the option to generate a new one on the same day
- Use an Azure Function or any public API to generate the word of the day
- Store passcode requests with requester details
- Design admin and resident screens with request history and basic statistics
Requirements List:
- Only registered residents in the database can access the application.
- Residents should be able to generate a passcode with a click of a button.
- The passcode format must follow this pattern: Street Unique Shortcode + House Number + Randomly generated Word for the day, stored in a table.
- If a resident generates a passcode for the day, opening the app again on the same day should only reveal the code without an option to generate a new one.
- Utilize an Azure Function or any public API to generate the Word for the day. The nuget library “Bogus” in .NET can be used for this purpose, or any other library, API, or service the developer prefers.
- All passcode requests should be stored in a table with detailed information about the requester.
- The admin should have access to a screen displaying a list of all request history on a table, including requester details. This screen should also feature basic statistics, such as the total number of requests, and include a filter button for dates.
- Residents should have access to a screen displaying a list of all their request history on a table, along with basic statistics like the total number of requests. The screen should also have a filter button for dates.
- Developers can make other assumptions regarding the implementation, but they must document these assumptions.
What are you waiting for? Time to get started!
Get started and document your solution following the provided guide!
Additional Resources
Participate in the Microsoft Learn AI Skill Challenge. Click to participate
Microsoft Learn: https://aka.ms/learnstudent
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments