Microsoft 365 provides various ways to build forms, ranging from simple tools to advanced development platforms.

Overview The team manages 50–100 specialized technical tools used across multiple teams. Each tool requires a four step approval process, and requests often remain active for several years before all approvals are complete. The legacy system was built on InfoPath, SharePoint 2010 impersonation workflow and 2013 workflows. Item level permission breaking, creating a fragile environment that was difficult to maintain. The goal of this project is to modernize the entire workflow

The Challenge: High-Risk Interaction Users frequently interacted with critical "fatal choice" buttons without a safety net. Meaning, they would reject or approve in one click. The best practice for these fatal choice buttons is to confirm with the user that the click wasn't an accident. Accidental clicks led to submissions with incorrect data or not ready for approval / rejection, causing data errors and broken business processes. The Solution: Dynamic Modal Component I devel

Overview The company's legacy training request process relied on outdated InfoPath Forms, 2010 Impersonation Workflow steps, and 2013 custom workflows. With Microsoft retiring InfoPath, 2010 Workflows, and 2013 custom workflows with SharePoint Designer, the team needed a modern, automated solution to reduced administrative work. The Problem The existing process had several challenges: Requests submitted through outdated forms and emails No centralized tracking or visibility i

Power Apps are a fun and easy way to create forms quickly, but sometimes you need to add extra code for functionality that will improve the user experience. This demonstration shows how to add a pop-up screen based off of the user canceling edits to a form and if they have unsaved data. This same concept could be used for deleting items as well, by asking the user if they are sure they want to delete an item. Pre-requisites - Have an edit form on your app connected to a data