Muhammad Uzair

In many real-world Dynamics 365 / Model-Driven App implementations, Business Process Flow (BPF) stages must reflect the actual business state of a record , not just user clicks. In this blog, I’ll explain how to automatically move a BPF stage on form load based on: Request Status Assigned To field This ensures the BPF always stays in sync with the record’s lifecycle — even when data is updated by background processes, integrations, or workflows. 🎯 Business Requirement When a record is opened: The BPF stage should automatically move to the correct stage The stage depends on: he_requeststatus he_assignedto Example Rules This removes manual stage movement and improves data accuracy and user experience. 🧠 Key Design Challenges Microsoft does not provide a direct API to jump to a specific BPF stage by name . Instead, we only have: moveNext() movePrevious() So the solution: ✅ Determines the target stage ✅ Figures out whether to move forward ...

🚀 Migrating Legacy Data into Power Pages with Entra ID Users (Step-by-Step Guide) When building a Power Pages site, one of the most common challenges teams face is migrating historical data into Dataverse while ensuring that records remain linked to the correct users. In Power Pages, every authenticated user is represented by a Contact record in Dataverse. However, Contacts are created only when users log in for the first time . So what happens when: You are migrating old data Requests were created by users And those users have never logged into the new Power Pages site yet? This blog walks you through a clean, enterprise-grade solution to handle this scenario properly. 🧩 The Problem You are building a Power Pages site and migrating data from a legacy system into Dataverse. Each request record: Was created by a user Must be linked to a Contact record Uses Entra ID (Azure AD) for authentication But: The Power Pages site is new Contacts do not exist yet Users have not logged in yet ...