During the student registration process, we leverage the Face API to automatically zoom in on the user’s face for precision and accuracy. For more details, you can refer to the GitHub repository: ACDC/registerimage at main · sindrejv/ACDC · GitHub.
Additionally, we’ve added a touch of fun to the experience by integrating the easter-egg-collection, which triggers random figures to pop up unexpectedly, keeping the process entertaining and unpredictable. Check out the GitHub repository here for more information: ACDC/eastereggpcf at registerimage · sindrejv/ACDC · GitHub.
We all know that Power BI is a beautiful tool for dashboarding, but it’s always a tricky question of where to get the data from. It needs to be fast, and most importantly, it should be correct.
The traditional way, from what I gather, is using the CDS connector. Here, we get easily visible and editable tables.
Another way, which will also give us Direct Query connection mode, is a connector directly to Dataverse.
But what about Fabric? If we need to create many reports on the same data from the CRM, then it would be perfect to have our data in OneLake, create DataFlow Gen 2 to transform it, and have a shared data model that will be utilized by different reports, dashboards, apps, etc.
For that, there are several ways to do it. The most tempting one is just using a Fabric Premium subscription to create a Lakehouse and using Azure Synapse Link to sync the tables from PowerApps to Fabric.
Unfortunately, when you have a Lab environment, it is not possible to create the OneLake on a Fabric workspace for now. Hopefully, this will be fixed in the future.
Another way is to create a resource group and create Azure storage account in the Azure Portal. If the user has the correct roles and access, then we should, in theory, be able to load tables from Power Apps to this storage and load them into a Storage Blob container. This approach got us much further, and we received a beautiful message on Power Apps.
However, when we try to create a link, the tables get queued but never appear in the Blob Storage.
However, for us, this approach did not work as our work tenant was registered in a different region from the Azure workspace where we are developing our CRM system.
Conclusion: If you are thinking of using Fabric, ensure your solution and Fabric are in the same region and don’t use the lab user.
In the end, to have a beautiful, real-time updating report, we will go for the second approach described here: connecting directly to Dataverse and using Direct Query to have a real-time update of the changes.
We also used SharePoint to get images to visualize in the report, and Excel files (xlsx) for some test data.
At the heart of every wizard’s journey lies the need to explore their magical potential, refine their skills, and discover the path that best aligns with their unique talents. To ensure that every aspiring wizard receives the guidance and feedback they need to thrive, we are developing a comprehensive system of tests designed to evaluate their proficiency in the magical arts.
Our goal is to create a series of engaging and challenging tests that assess various aspects of magical performance. From spellcasting precision to advanced problem-solving under magical constraints, these tests will provide a well-rounded evaluation of each student’s strengths. The tests are tailored to reflect the critical abilities required in the magical world and are designed to immerse students in scenarios where their creativity and expertise are put to the test.
Upon completion of the tests, each wizard-in-training will receive a detailed assessment of their performance. But we’re not stopping there—our system will also include personalized recommendations for their future magical specialties. Whether a student shows promise in potion-making, or flying, they’ll gain insights into the areas where their talents truly shine. These recommendations are aimed at guiding them toward a fulfilling and successful magical career.
This innovative grading and evaluation system is powered by some of the most advanced tools in the tech world. By leveraging these powerful tools, we’re not just modernizing the evaluation process—we’re creating an enchanting and transformative experience for both students and instructors.
This isn’t just about grading; it’s about empowering the next generation of wizards to step into their potential. With a blend of tradition and innovation, these tests serve as a bridge between magical lore and modern technology. They ensure every student is prepared, inspired, and equipped to excel in their magical journey.
When the time comes for young wizards to take their Ordinary Wizarding Levels (O.W.L.s), they must pass a theory test to demonstrate their knowledge. With the help of AI, we leverage this technology to generate advanced questions in the field of wizardry, saving valuable time for teachers.
Example of an exam question: Can you answer this?
With the help of OpenAI hosted in Azure AI Foundry, we can seamlessly integrate AI into a canvas app, where the questionnaire is created. This integration is achieved using an Azure Function that processes the OpenAI response data and transforms it into a format that is easily handled with Power Fx. This approach not only enhances the functionality of the app but also saves time and effort for developers and users alike.
To ensure students are fully aware of each stage in their journey, we’ve implemented a Power Automate connector that sends automated SMS notifications every time a new challenge begins. The connector is integrated directly to Linkmobility APIs through an Azure function, and the connector is connected to the Azure function. This keeps them informed and ready to tackle each step with confidence.
Example of the registration flow:
The SMS received upon completing the registration:
PowerFx has undoubtedly cemented its place as a key tool for the future. Yet, the low-code approach of the Ribbon Workbench continues to prove its worth, offering a seamless and efficient way to achieve great results. By leveraging this approach, we’re saving valuable time—no need to create a button for every app, making our workflows smoother and more streamlined than ever.
Wizards from all corners of the nation in their 5th semester must take the mandatory Ordinary Wizarding Level (O.W.L.s) exams to showcase their knowledge and performance in the magical arts. As these tests are mostly done manually with pen and paper, we believe that with technologies like Dataverse, Power Apps, PCF, AI, and more, we can automate these processes to create a more efficient and streamlined system. By collecting test result data, we can provide dashboards and tools for teachers and school administration to showcase data effectively.
How this will work:
With a fresh model-driven app, we want students to navigate the challenges through a business process flow (BPF). Each step is a new challenge, and these challenges will be created in different ways, such as using canvas apps, custom pages, PCF, or just the standard model-driven app user interface.
Draft of the BPF:
Example of one of the minigames:
Once the challenge is completed, Dumbledoor must sign the grading card, which includes the scores from the challenges. A draft of the grading card is shown below:
Overflowing with excitement, we’re thrilled to once again embark on the incredible journey of the Arctic Cloud Developer Challenge! This year, we’ve leveled up, armed with fresh strategies and sharpened skills, ready to tackle whatever challenges come our way. The energy is electric, the team spirit is soaring, and we can’t wait to see where this adventure takes us!
We’ve also brought along our trusty companion, Gilderoy Lockhart, to add a touch of flair and exceptional storytelling to our journey. Every post we share is genuinely our own—crafted with care and originality, never borrowed or stolen from others 😉
