Building a Visitor Check-In App with Microsoft Power Platform: A Hands-On Success

From Paper Logs to Power Platform: Building a Visitor Check-In App in 60 minutes

Welcome, readers! I recently led a 60-minute hands-on session where I built a Visitor Pre-Registration and Check-In System using Microsoft Power Platform using only standard Microsoft 365 licensing components: Microsoft Forms, SharePoint, Power Automate, and a Power Apps Canvas App. The energy in the room was electric, and by the end, I had a fully functional app that amazed everyone. In this blog post, I’ll walk you through every step of the process, complete with detailed instructions and all the code used, so you can build your own version of this app.

Why Standard Licensing Makes This Special

Since I’m working within the constraints of standard Microsoft 365 licensing, I leveraged components that support connectors under standard licensing. This means no premium connectors or additional costs are required, making this solution accessible to any organization with a Microsoft 365 subscription.

This approach not only saves money but also democratizes access to powerful automation and app-building tools!

The Problem: Visitor Management Challenges

Many organizations struggle with inefficient visitor management—paper logs, Excel spreadsheets, or manually updated SharePoint lists. These methods lack automation and an intuitive interface. My goal was to create a modern solution using Power Platform’s low-code tools, and I succeeded!

The Vision: A Streamlined System

I aimed to build a system where visitors pre-register via a form, staff manage check-ins through an app, and managers access insights via a dashboard. Using Microsoft Forms, SharePoint, Power Automate, and Power Apps, I created a solution that automates pre-registration, notifies hosts, prints badges, and tracks visitor activity—all within standard licensing.

Technical Deep Dive: Step-by-Step Guide

Let’s dive into the details. Below, I’ll break down each component with in-depth instructions and the exact code used.

1. Setting Up the SharePoint List

The SharePoint list "Visitor Records" is the foundation of my app, storing all visitor data securely.

Detailed Steps to Create the SharePoint List:

1. Navigate to your SharePoint site (e.g., https://yourdomain.sharepoint.com/sites/yoursite).
2. In the left navigation, click Site contents.
3. Click + New and select List.
4. In the "Name" field, enter Visitor Records, then click Create.
5. Once created, click + Add column to define the following columns:
• Visitor Name: Select "Single line of text," set as Required.
• Email: Select "Single line of text," set as Required.
• Meeting Purpose: Select "Choice," add options: "Interview," "Review," "Other." Set default to "Interview."
• Host Employee: Select "Person or Group," allow only "People," set as Required.
• Expected Arrival Date: Select "Date and time," include date only, set as Required.
• Expected Arrival Time: Select "Choice," add options: "9:00 AM," "10:00 AM," "11:00 AM," etc. Set default to "9:00 AM."
• Check-In Status: Select "Choice," add options: "Pending," "Checked In," "Checked Out." Set default to "Pending."
• Check-In Time: Select "Date and time," include date and time.
• HostEmail: Select "Single line of text."
6. Click Save after adding each column.

Tip: Ensure column names match exactly as listed, as they’ll be referenced later.

2. Microsoft Forms & Power Automate: Pre-Registration Automation

I used Microsoft Forms for visitor pre-registration and Power Automate to sync form responses to SharePoint and send confirmation emails.

Detailed Steps to Create the Form:

1. Go to forms.office.com and sign in.
2. Click New Form.
3. Set the title to Visitor Registration.
4. Add the following questions:
• Visitor Name: Click "+ Add new," select "Text," mark as Required.
• Email: Add "Text," mark as Required, enable "Restrict to email addresses."
• Meeting Purpose: Add "Choice," enter options: "Interview," "Review," "Other." Mark as Required.
• Host Employee’s Email: Add "Text," mark as Required, enable "Restrict to email addresses."
• Expected Arrival Date: Add "Date," mark as Required.
• Expected Arrival Time: Add "Choice," enter options: "9:00 AM," "10:00 AM," "11:00 AM," etc. Mark as Required.
5. Click Share, copy the link, and save the form.

Detailed Steps to Create the Power Automate Flow:

1. Go to powerautomate.microsoft.com.
2. Click Create > Automated cloud flow.
3. Name it Form to List, search for "When a new response is submitted," select the Microsoft Forms trigger, and click Create.
4. In the trigger, select "Visitor Registration" from the Form Id dropdown.
5. Click + New step, search for "Get response details" (Microsoft Forms), and configure:
• Form Id: Visitor Registration
• Response Id: Select dynamic content Response Id from the trigger.
6. Add a step: Search for "Get user profile (V2)" (Office 365 Users), set User (UPN) to dynamic Host Employee’s Email from the form response.
7. Add a step: Search for "Create item" (SharePoint), configure:
• Site Address: Enter your SharePoint site URL (e.g., https://yourdomain.sharepoint.com/sites/yoursite)
• List Name: Visitor Records
• Map fields using dynamic content:
  • Visitor Name: Visitor Name
  • Email: Email
  • Meeting Purpose: Meeting Purpose
  • Host Employee: Mail from "Get user profile"
  • Expected Arrival Date: Expected Arrival Date
  • Expected Arrival Time: Expected Arrival Time
  • Check-In Status: Type Pending
  • HostEmail: Mail from "Get user profile"
8. Add a step: Search for "Send an email (V2)" (Office 365 Outlook), configure:
• To: Dynamic Email from form response
• Subject: Visitor Pre-Registration Confirmation
• Body (use HTML editor):

  Dear [Dynamic "Visitor Name"],
  
  Thank you for pre-registering for your visit. Here are the details:
  
  Meeting Purpose: [Dynamic "Meeting Purpose"]
  
  Host: [Dynamic "DisplayName" from "Get user profile"]
  
  Expected Arrival Date and Time: [Dynamic "Expected Arrival Date"] at [Dynamic "Expected Arrival Time"]
  
  Please arrive at the front desk upon arrival.
  
  Best regards,
  
  [My Company Name]

9. Click Save and test by submitting a form response.

3. Building the Canvas App

The Canvas App provides an interactive interface for staff to manage visitors. Here’s how I built it.

Detailed Steps to Create the Canvas App:

1. Go to make.powerapps.com.
2. Click Create > Canvas app, select "Tablet layout."
3. Name it Visitor Check-In and click Create.
4. In the left pane, click Data, then Add data, select SharePoint, connect to your site, and add the Visitor Records list.
5. Rename the default screen to scrTodayVisitors (double-click Screen1 in the Tree view).
6. Add a Gallery:
• Click Insert > Gallery > Vertical.
• Set Data Source to Visitor Records.
• Set Items property:

  Filter(
      'Visitor Records',
      DateValue(
          Text(
              'Expected Arrival Date',
              "[$-en-US]yyyy-mm-dd"
          )
      ) = Today(),
      If(
          drpHostFilter.Selected.Value = "All",
          true,
          Host.DisplayName = drpHostFilter.Selected.Value
      )
  )

• Set OnSelect: UpdateContext({conSelectedId: ThisItem.ID})
• Set DisplayMode:

  If(
      frmVisitorDetails.Mode = FormMode.View,
      DisplayMode.Edit,
      DisplayMode.Disabled
  )

• Customize fields: Click "Edit" next to Fields, add "Visitor Name," "Host Employee," "Expected Arrival Time," "Check-In Status."
7. Add a Dropdown (drpHostFilter):
• Click Insert > Dropdown, name it drpHostFilter.
• Set Default: "All"
• Set Items:

  Ungroup(
      Table(
          { Value: "All" },
          Sort(Distinct('Visitor Records', Host.DisplayName), Value, SortOrder.Ascending)
      ),
      "Value"
  )

8. Add a Form (frmVisitorDetails):
• Click Insert > Form > Edit Form, name it frmVisitorDetails.
• Set DataSource: Visitor Records
• Set DefaultMode: FormMode.View
• Set Item: LookUp('Visitor Records', ID = conSelectedId)
• Set OnSuccess:

  ViewForm(frmVisitorDetails);
  Notify(
      "You have updated the record!",
      NotificationType.Success,
      2000
  );
  UpdateContext({conSelectedId: Self.LastSubmit.ID})

• Add fields: Click "Edit fields," add all columns from the list.
9. Add Icons:
• Edit (icoEdit): Insert > Icon > Edit, set OnSelect: EditForm(frmVisitorDetails), DisplayMode:

  If(
      And(
          frmVisitorDetails.Mode = FormMode.View,
          Not(IsBlank(conSelectedId))
      ),
      DisplayMode.Edit,
      DisplayMode.Disabled
  )

• Save (icoSave): Insert > Icon > Save, set OnSelect: SubmitForm(frmVisitorDetails), DisplayMode:

  If(
      And(
          frmVisitorDetails.Mode = FormMode.Edit,
          Not(IsBlank(conSelectedId))
      ),
      DisplayMode.Edit,
      DisplayMode.Disabled
  )

• Cancel (icoCancel): Insert > Icon > Cancel, set OnSelect: ResetForm(frmVisitorDetails), DisplayMode:

  If(
      frmVisitorDetails.Mode in [
          FormMode.Edit,
          FormMode.New
      ],
      DisplayMode.Edit,
      DisplayMode.Disabled
  )

• Print (icoPrint): Insert > Icon > Print, set OnSelect: Print(), DisplayMode:

  If(
      And(
          frmVisitorDetails.Mode = FormMode.View,
          Not(IsBlank(conSelectedId))
      ),
      DisplayMode.Edit,
      DisplayMode.Disabled
  )

I chose to use icons over buttons primarily because of space optimization and visual clarity. Icons are compact and blend well into tight UI layouts like galleries, forms, or headers without overwhelming the screen. They also allow for a more modern and intuitive design—users can instantly recognize actions like edit, delete, print, or save just by the visual cue. While buttons are great for more prominent actions, icons are ideal for contextual or secondary actions where space and clean design are priorities.

10. Save and publish the app.

4. Print Badge Functionality

I added a print feature to generate visitor badges.

Detailed Steps for Print Badge:

1. Click Insert > New Screen, name it scrPrintScreen.
2. Set DataSource to Visitor Records.
3. Set Item: galTodayVisitors.Selected
4. Add labels for Visitor Name, Host Employee, Expected Arrival Date/Time (e.g., galTodayVisitors.Selected.'Visitor Name').
5. Update icoPrint OnSelect:

   Set(varOriginScreen, scrTodayVisitors);
   Navigate(scrPrintScreen);

6. On scrPrintScreen, add a Print button, set OnSelect:

   Print();
   Navigate(varOriginScreen);

5. Power Automate Flows: Check-In and Check-Out

I created two flows to automate check-in and check-out notifications.

Detailed Steps for Check-In Flow:

1. Go to Power Automate, click Create > Automated cloud flow.
2. Name it Visitor Check-In - Update List & Notify Host, select "When an item is created or modified" (SharePoint), click Create.
3. Configure trigger:
   • Site Address: Your SharePoint site URL
   • List Name: Visitor Records
4. Add a "Condition": Check-In Status is equal to Checked In.
5. In "If yes," add "Send an email (V2)":
   • To: Dynamic HostEmail
   • Subject: Visitor Check-In Notification
   • Body:

     Your visitor [Dynamic "Visitor Name"] has checked in at [Dynamic "Check-In Time"].
     
     Meeting Purpose: [Dynamic "Meeting Purpose"]

6. Save and test.

Detailed Steps for Check-Out Flow:

1. Create a new flow named Visitor Check-Out - Update List & Thank You Email.
2. Use the same SharePoint trigger.
3. Add a "Condition": Check-In Status is equal to Checked Out.
4. In "If yes," add "Update item" (SharePoint):
   • Site Address and List Name as above
   • ID: Dynamic ID
   • Check-Out Time: utcNow()
5. Add "Send an email (V2)":
   • To: Dynamic Email
   • Subject: Thank You for Visiting
   • Body:

     Dear [Dynamic "Visitor Name"],
     
     Thank you for visiting! You checked out at [Dynamic "Check-Out Time"].
     
     Best regards,
     
     [My Company Name]

6. Save and test.

6. Dashboard & Reporting

I added a dashboard for insights.

Detailed Steps for Dashboard:

1. In the Canvas App, add a new screen named scrDashboard.
2. Bar Chart: Insert > Chart > Column chart, set Items:

   GroupBy('Visitor Records', "Meeting Purpose", "Count")

3. Gallery: Add a gallery, set Items: 'Visitor Records', display Check-In Time, Check-Out Time.
4. Late Arrival Label: Add a label, set Text:

   "Late Arrivals: " & CountIf('Visitor Records', 'Check-In Time' > 'Expected Arrival Date' + Time(Value(Left('Expected Arrival Time', 2)), Value(Mid('Expected Arrival Time', 4, 2)), 0))

Conclusion

This Visitor Check-In App demonstrates the power of Microsoft Power Platform, all built within standard Microsoft 365 licensing for zero additional cost. With these detailed steps and code, you can build your own app. Try it out and let me know how it goes!

Snapshots:

Comparing Approaches for Power Apps Model Driven Apps Form Notifications

Comparing Approaches for Power Apps Notifications: Why JavaScript Is the Best Solution

In this blog, we’ll explore different approaches to implementing dynamic notifications in Power Apps model-driven apps, specifically for notifying users. By comparing JavaScript, Business Rules, and Power Fx, we’ll determine which is the best-suited solution for our scenario. Our requirement involves displaying a notification with a 5-second timeout when the linked Address is Inactive, ensuring a seamless user experience. Spoiler: JavaScript emerges as the most flexible and powerful choice. Let’s dive into the details to understand why.

The Requirement

Our Power Apps model-driven app uses two Dataverse tables:

• Address: Contains address records with a status (statecode and statuscode), where Active is statecode = 0 and Inactive is statecode = 1 (e.g., statuscode = 2 for “Inactive/Retired”).
• Site: Includes a lookup field (cr123_addressid) linking to an Address record in a one-to-many relationship.

We needed to:

1. Create a system view in the Site table to show Sites linked to Inactive Addresses.
2. Display a notification on the Site main form when the linked Address is Inactive, suggesting an Active Address, with the notification clearing after 5 seconds.

We implemented the system view using the Power Apps maker portal’s view designer, filtering for Sites with an Inactive Address (statecode = 1). For the notification, we evaluated JavaScript, Business Rules, and Power Fx to find the best approach.

Approach 1: JavaScript Solution

The JavaScript solution uses a web resource attached to the Site form’s OnLoad event to check the Address status and display a notification. Here’s the code:

// Function to display a notification if the related Address is Inactive
// Ensure schema names and status codes are updated:
// - Replace 'cr123_addressid' with the actual Address lookup field schema name
// - Replace 'cr123_address' with the actual Address table logical name
// - Replace '1' with the actual statecode for Inactive (typically 1)
// - Replace '2' with the actual statuscode for Inactive reason (e.g., Inactive/Retired)
function showInactiveAddressNotification(executionContext) {
    var formContext = executionContext.getFormContext();
    
    // Check if running on the main form (2 = Update form)
    if (formContext.ui.getFormType() !== 2) {
        return;
    }

    // Get the Address lookup field
    var addressLookup = formContext.getAttribute("cr123_addressid");
    if (!addressLookup || !addressLookup.getValue()) {
        // Clear any existing notification if no Address is selected
        formContext.ui.clearFormNotification("InactiveAddressWarning");
        return;
    }

    // Get the Address ID
    var addressId = addressLookup.getValue()[0].id;

    // Retrieve the Address record's statecode and statuscode
    Xrm.WebApi.retrieveRecord("cr123_address", addressId, "?$select=statecode,statuscode").then(
        function (result) {
            // Clear any existing notification
            formContext.ui.clearFormNotification("InactiveAddressWarning");

            // Check if Address is Inactive
            if (result.statecode === 1 && result.statuscode === 2) {
                // Set notification
                formContext.ui.setFormNotification(
                    "The related Address record is Inactive. Please consider selecting an Address with Active status.",
                    "WARNING",
                    "InactiveAddressWarning"
                );
                // Clear notification after 5 seconds
                setTimeout(function() {
                    formContext.ui.clearFormNotification("InactiveAddressWarning");
                }, 5000);
            }
        },
        function (error) {
            console.log("Error retrieving Address: " + error.message);
            formContext.ui.setFormNotification(
                "Failed to verify Address status. Please try again or contact support.",
                "ERROR",
                "AddressError"
            );
            setTimeout(function() {
                formContext.ui.clearFormNotification("AddressError");
            }, 5000);
        }
    );
}

// Optional: Add OnChange handler for dynamic updates
function registerAddressLookupOnChange(executionContext) {
    var formContext = executionContext.getFormContext();
    var addressLookup = formContext.getAttribute("cr123_addressid");
    if (addressLookup) {
        addressLookup.addOnChange(showInactiveAddressNotification);
    }
}
  

How It Works

• OnLoad Event: Runs on form load, ensuring it only executes on the main Update form (formType = 2).
• Lookup Check: Verifies the Address lookup field (cr123_addressid) has a value, clearing notifications if empty.
• Web API Query: Fetches the Address’s statecode and statuscode via Xrm.WebApi.
• Notification: Displays a banner notification for Inactive Addresses, clearing after 5 seconds via setTimeout.
• Dynamic Updates: Attaches an OnChange handler to the Address lookup for real-time updates.
• Dependencies: Ensures the cr123_addressid field is available via a table column dependency.

Implementation Steps

1. Create a JavaScript web resource (new_showInactiveAddressNotification) with the code above, updating schema names.
2. Add the web resource to the Site form’s Form Libraries and register both functions under OnLoad, enabling “Pass execution context.”
3. Add a dependency for cr123_addressid.
4. Test across scenarios (Inactive Address, Active Address, no Address, lookup changes).

Approach 2: Business Rules

Business Rules provide a no-code way to apply form logic, such as showing error messages or locking fields.

Limitations

• Intrusive Messages: Error messages block form saving, unlike JavaScript’s non-intrusive banner notification.
• Limited Logic: Cannot query related records’ statecode/statuscode or implement timeouts.
• Static Behavior: Lacks support for dynamic updates on field changes without form reloads.

When to Use

Business Rules suit simple, no-code tasks (e.g., locking fields) but are inadequate for dynamic notifications.

Approach 3: Power Fx

Power Fx is a low-code formula language used in canvas apps and some model-driven app features (e.g., command bar rules).

Limitations

• No OnLoad Support: Power Fx cannot run on model-driven form OnLoad events, which rely on JavaScript’s Xrm API.
• Custom Page Needed: Requires a modal custom page, which is intrusive and complex to integrate.
• No Native Notification: Power Fx’s Notify function doesn’t support form banner notifications in model-driven apps.
• Integration Complexity: Combining Power Fx with JavaScript for form events adds unnecessary overhead.

When to Use

Power Fx is ideal for canvas apps or command bar logic but unsuitable for model-driven form events.

Why JavaScript Is the Best-Suited Solution

JavaScript outperforms Business Rules and Power Fx due to its unmatched flexibility and capability:

1. Comprehensive Feature Support

• Handles all requirements: notification, timeout, and dynamic updates within a single script.
• Uses setFormNotification for native banner notifications that integrate seamlessly with the app’s UI.

2. Advanced Logic and Integration

• Queries related records via Xrm.WebApi for dual statecode/statuscode checks.
• Supports OnChange handlers for real-time updates, unlike Business Rules.
• Integrates with model-driven app forms via the Xrm API.

3. User Experience

Delivers a polished experience with non-intrusive notifications and precise timeout control.

4. Robustness and Extensibility

• Includes error handling for Web API failures and form type checks for compatibility.
• Supports accessibility (e.g., can add aria-label for screen readers).
• Maintains reliability with table column dependencies.

Compared to Business Rules’ limited scope and Power Fx’s inapplicability to form events, JavaScript’s versatility makes it the clear winner.

Conclusion

By exploring JavaScript, Business Rules, and Power Fx for our Power Apps notification requirement, we’ve seen that JavaScript is the best-suited solution. Its flexibility, integration with model-driven app forms, and ability to handle complex logic and dynamic updates make it far superior to the limited Business Rules and incompatible Power Fx. This solution enhances user awareness, ensures data integrity, and delivers a seamless experience in our app. Try it in your Power Apps project and see the difference!

What’s your preferred approach for Power Apps notifications? Share your insights in the comments!

PowerApps & Dynamics 365 CE Interview Questions

Below is a comprehensive list of 260+ interview questions covering PowerApps and Microsoft Dynamics 365 Customer Engagement (CE).

Section 1: PowerApps Fundamentals and Basics (Questions 1–50)

• What is Microsoft PowerApps, and how does it help in building business applications?
• Can you explain a real-world use case where you implemented PowerApps?
• What is the difference between Canvas apps and Model-Driven apps in PowerApps?
• How do you connect PowerApps to external data sources such as SharePoint, SQL Server, and Dataverse?
• What are connectors in PowerApps, and how do they work?
• What are global variables in PowerApps, and how do they differ from context variables?
• How do you manage collections in PowerApps, and what common pitfalls should you watch out for?
• Can you explain how the Patch function works compared to SubmitForm in PowerApps?
• How do you implement form validation in PowerApps?
• How do you set up error logging in PowerApps for debugging and monitoring?
• What is the role of the Timer control in PowerApps, and how do you use it for asynchronous tasks?
• How do you handle delegation warnings and optimize queries for large datasets in PowerApps?
• How do you manage screen navigation and pass parameters between screens in PowerApps?
• What is the purpose of the StartScreen property in a Canvas app, and how is it configured?
• How do you create responsive layouts in PowerApps that work effectively on different devices?
• How do you incorporate custom controls or components into your PowerApps application?
• What performance optimization techniques do you implement in PowerApps?
• How do you incorporate themes and design principles into your PowerApps development?
• How do you filter data and implement row-level security in PowerApps?
• How do you integrate media (images, video, audio) into a PowerApps application?
• What strategies do you use to reduce loading times when handling heavy data sources in PowerApps?
• What is the Concurrent function in PowerApps, and how is it used to run multiple operations simultaneously?
• How do you implement branching and complex business logic in PowerApps?
• How do you combine Filter and Sort functions effectively on large datasets?
• How do you create a loading spinner or progress indicator in PowerApps?
• How do you use the ForAll function to iterate through and process collections in PowerApps?
• How do you validate user input, especially for numerical and date formats, in PowerApps?
• Explain how you utilize the LookUp function to retrieve specific records in PowerApps.
• How do you manage session-specific data and overall app state in PowerApps?
• How do you design effective forms using Data Cards customization in PowerApps?
• How do you integrate PowerApps with SharePoint as a data source?
• How do you manage complex formulas that involve multiple data sources in PowerApps?
• How do you implement offline capabilities using SaveData and LoadData functions in PowerApps?
• How do you build multilingual support into a PowerApps application?
• How do you design user interfaces with effective error messages and notifications in PowerApps?
• What techniques do you use for testing and debugging PowerApps efficiently?
• How do you ensure accessibility compliance in your PowerApps designs?
• How do you configure connector authentication and secure API integrations in PowerApps?
• How do you address data refresh challenges and maintain up-to-date information in PowerApps?
• How do you manage versioning and updates in your PowerApps projects?
• How do you leverage custom connectors for integrating with external APIs in PowerApps?
• What are your best practices for error handling and rollback operations using Patch in PowerApps?
• How do you design a user-centric navigation flow to ensure a seamless app experience in PowerApps?

Section 2: Advanced PowerApps & Power Automate Techniques (Questions 51–100)

• How do you integrate PowerApps with Power Automate for workflow automation?
• Can you explain the process for triggering a Flow from a PowerApps button?
• How do you pass data between PowerApps and Power Automate flows?
• How do you handle errors in Power Automate flows that are triggered from PowerApps?
• How do you design approval workflows using Power Automate?
• What are the best practices for building complex conditional workflows in Power Automate?
• How do you utilize adaptive cards within Power Automate for enriched notifications?
• How do you use custom connectors within Power Automate to interact with external APIs?
• How do you manage state and concurrency issues in Power Automate flows?
• How do you debug and monitor Power Automate flows for optimal performance?
• How do you implement detailed error tracing and logging in your Power Automate processes?

Section 3: Dynamics 365 CE Customizations, Plugins, and Workflows (Questions 101–200)

• What is Microsoft Dynamics 365 CE, and what are its core modules and functionalities?
• How do you create and manage custom entities within Dynamics 365 CE?
• How do you design forms and views for an optimal user experience in Dynamics 365 CE?
• How do you implement and manage business rules in Dynamics 365 CE?
• How do you configure and implement workflows within Dynamics 365 CE?
• What are the key differences between Dynamics 365 CE workflows and Power Automate flows?
• How do you register, deploy, and debug a Dynamics 365 CE plugin?
• What techniques do you use for exception handling and error logging in Dynamics 365 CE plugins?
• How do you manage synchronous versus asynchronous operations in Dynamics 365 CE workflows?
• How do you implement data validation and error handling on Dynamics 365 CE forms?
• How do you design and manage security roles and business units in Dynamics 365 CE?
• How do you create and manage lookup fields and entity relationships in Dynamics 365 CE?
• How do you use FetchXML for querying records or creating reports in Dynamics 365 CE?
• How do you integrate Dynamics 365 CE with other Microsoft services such as PowerApps and SharePoint?
• How do you extend Dynamics 365 CE functionality using custom workflows?
• How do you manage version control and deployments for Dynamics 365 CE customizations?
• What is your approach to implementing complex business logic with Dynamics 365 CE plugins?
• How do you design efficient data models for Dynamics 365 CE?
• How do you address multi-language and localization requirements in Dynamics 365 CE?
• How do you leverage the Dynamics 365 CE SDK for advanced customizations?
• How do you secure sensitive data within Dynamics 365 CE customizations?
• How do you troubleshoot performance issues in Dynamics 365 CE customizations?
• How do you manage updates and migrations for Dynamics 365 CE solutions?
• How do you implement cascading rules for related entities in Dynamics 365 CE?
• How do you leverage Microsoft Dataverse in conjunction with Dynamics 365 CE?
• How do you optimize search and indexing features in Dynamics 365 CE?
• How do you use business process flows to streamline operations in Dynamics 365 CE?
• How do you integrate Dynamics 365 CE with Office 365 tools like Outlook and Excel?
• How do you manage record ownership and access control in Dynamics 365 CE?
• How do you leverage advanced workflows to automate multi-step business processes in Dynamics 365 CE?
• How do you monitor and analyze system performance in Dynamics 365 CE?
• How do you implement cascading security rules across related entities in Dynamics 365 CE?
• How do you design for scalability in Dynamics 365 CE customizations?
• How do you manage concurrent data updates in Dynamics 365 CE?
• How do you audit and trace changes made to records in Dynamics 365 CE?
• How do you implement and manage custom dashboards and reports in Dynamics 365 CE?
• How do you troubleshoot data integrity issues in Dynamics 365 CE?
• How do you manage Dynamics 365 CE plugins across different environments (development, testing, production)?
• How do you implement integration patterns between Dynamics 365 CE and external systems?
• How do you update lookup values and manage complex entity relationships in Dynamics 365 CE?
• How do you optimize CRM forms for faster load times and improved user experience in Dynamics 365 CE?
• How do you implement custom field validations and business logic in Dynamics 365 CE?
• How do you manage government cloud-specific configurations for Dynamics 365 CE?
• How do you leverage AI Builder within Dynamics 365 CE for intelligent process automation?
• How do you use the Dynamics 365 CE Web API for custom integrations?
• How do you troubleshoot errors during Dynamics 365 CE plugin registration?
• How do you design a robust architecture for customizations in Dynamics 365 CE?
• How do you handle cross-entity workflows in Dynamics 365 CE?
• How do you test and validate Dynamics 365 CE customizations for quality and performance?
• How do you implement dynamic field-level security in Dynamics 365 CE?

Section 4: Leadership & Management (Questions 201–260)

• As a team lead, how do you mentor and guide your team in adopting best practices for PowerApps and Dynamics 365 CE?
• How do you manage code reviews and ensure consistent quality across PowerApps and Dynamics 365 CE projects?
• How do you balance innovation with stability when introducing new features into established Dynamics 365 CE environments?
• How do you facilitate cross-functional team collaborations when implementing end-to-end solutions using PowerApps and Dynamics 365 CE?
• How do you ensure that your team stays up-to-date with the latest Microsoft innovations in PowerApps and Dynamics 365 CE?
• What project management strategies do you employ to handle large-scale Dynamics 365 CE implementations?
• How do you approach risk management and resource allocation in a dynamic PowerApps and Dynamics 365 CE project?
• How do you implement agile methodologies within your PowerApps and Dynamics 365 CE development processes?
• How do you plan for scalability and long-term support when architecting solutions using PowerApps and Dynamics 365 CE?
• What is your leadership approach in fostering a culture of innovation and continuous improvement within your technical team?

Delegable Queries in PowerApps Canvas Apps

Let the Data Source Do the Heavy Lifting: Delegable Queries in PowerApps Canvas Apps

As a PowerApps developer, I’ve come across many performance and functionality issues that stem not from bad intentions, but from a lack of understanding of how data queries work under the hood. One of the most critical – and often misunderstood – aspects of building performant and scalable apps is delegation.

In this post, I want to deep dive into:

• Why I’m writing about delegable queries
• The issues non-delegable queries cause
• Why these issues exist
• How to fix or work around them
• Best practices to keep your apps fast, efficient, and robust

Why I’m Writing About Delegable Queries

When building Canvas Apps that connect to large data sources like SharePoint, Dataverse, or SQL Server, I’ve noticed apps slowing down or failing to return expected results. After some investigation, the root cause is often the same: non-delegable queries.

Too many makers overlook this constraint or don't fully understand its impact. I’m writing this to help other makers avoid the pitfalls I encountered and to promote sustainable development practices within the Power Platform community.

What is Delegation?

In PowerApps, delegation refers to the ability of the app to pass the query to the data source for processing. When a query is delegable, only the result is returned – saving bandwidth, improving performance, and avoiding local processing limits.

Non-delegable queries, on the other hand, mean the app pulls the data into memory (default: first 500 records, max: 2000) and then applies filters or operations locally. This not only limits results but can dramatically reduce performance and scalability.

Are Delegable Queries Part of Power Fx?

Yes — delegable queries are written using Power Fx, the low-code formula language of Canvas Apps. But here's the catch:

Not all Power Fx functions are delegable.

Let’s break it down:

• Power Fx is used to express logic in Canvas Apps — filtering, sorting, updating, etc.
• But for a query to be delegable, PowerApps must be able to convert that Power Fx expression into a query that the backend system (like SQL or SharePoint) understands.

✅ Delegable Power Fx Example (SharePoint):

Filter(Employees, Department = "HR")

This uses delegable functions and operators — processed server-side.

❌ Non-Delegable Power Fx Example:

Filter(Employees, StartsWith(Name, "S"))

Because StartsWith isn't delegable in SharePoint, possibly missing many matching entries.

The Issue: Why Non-Delegable Queries Are a Problem

Let’s say you have a SharePoint list with 50,000 records and you write this formula:

Filter(MyList, StartsWith(Title, "S"))

This will not return all the records starting with "A". It will only apply to the first 500 or 2000 rows, depending on your app settings, because StartsWith is not delegable for SharePoint. That means records beyond the delegation limit are not evaluated – potentially causing missing data and misleading outputs.

Symptoms of Non-Delegable Queries:

• Partial results
• "Delegation warning" yellow triangle in the formula bar
• Slower performance
• Data inconsistencies
• Errors in large data sets

Why Does This Happen?

PowerApps is a low-code platform that connects to a variety of data sources, each with its own capabilities. Microsoft must abstract the query language (like OData, T-SQL) to Power Fx.

But not all Power Fx functions can be translated into native data source queries. If PowerApps can’t delegate a function, it falls back on retrieving data locally – up to the configured delegation limit.

Each connector has a documented set of delegable functions and operators, which you can refer to on Microsoft Learn.

Fixes and Workarounds

While not all functions are delegable, there are techniques to work around these limitations.

1. Use Delegable Functions When Possible

Learn which functions are delegable for your data source. Common ones:

• Filter
• Search
• LookUp
• SortByColumns

Avoid:

• StartsWith, Mid, Len, Left (for SharePoint)
• Complex nested logic

Instead of:

Filter(MyList, StartsWith(Title, "A"))

Use:

Filter(MyList, Title >= "A" && Title < "B")

2. Index Your Columns

Especially for SharePoint, indexing columns used in filtering significantly improves performance and helps delegation succeed.

3. Use Views or Stored Procedures

If using SQL Server or Dataverse, offload complex queries into views or stored procedures and call them from your app.

4. Combine Client-Side and Server-Side Filtering

When full delegation isn’t possible, use delegable filtering first, then a local filter:

Filter(
    Filter(MyList, Title >= "A" && Title < "B"), 
    AnotherClientSideFilter
)

5. Paginate or Virtualize Large Datasets

Use techniques like pagination, galleries with lazy loading, or loading records in chunks via Concurrent or With constructs.

Best Practices for Delegable Queries in PowerApps

• Always check for delegation warnings. Don't ignore the yellow triangle – it's there for a reason.
• Keep delegation in mind during design. Plan app logic around what your data source supports.
• Set realistic delegation limits. Increase the limit from 500 to 2000 only if necessary – but don’t rely on it.
• Minimize on-the-fly filtering on non-indexed columns.
• Test with production-sized data.
• Educate your team. Make delegation part of your code review or governance checklist.
• Refer to the Delegation Cheat Sheet. Microsoft maintains updated lists for each connector’s delegable functions.

Conclusion

Delegation is not just a PowerApps quirk – it’s a fundamental performance principle. Think of it as letting the database do what it’s good at: filtering, sorting, searching. Your app should only worry about displaying the final results.

By mastering delegation, you’ll:

• Improve app speed
• Prevent missing data
• Reduce support tickets
• Build scalable enterprise-grade apps

Learn what’s delegable:

• Watch for the yellow warning triangle in the formula bar
• Reference Microsoft’s docs:
  • Delegation Overview
  • Delegation Function List

---

Have you implemented similar solutions in Power Apps? Share your thoughts or questions in the comments below!

Canvas Apps vs. Model-Driven Apps: Picking the Best Fit for Your Microsoft Power Platform Project

Hey there, app creators! If you’re diving into the world of Microsoft Power Platform, you’ve probably heard about Canvas Apps and Model-Driven Apps. These two approaches let you build awesome apps with minimal coding, but they’re pretty different in how they work and what they’re best for. Choosing the right one can make or break your project, so let’s break it down in a simple way. We’ll explore what makes each app type special, share some real-world examples, and look at the latest 2025 updates to help you decide which one fits your needs.

What Are Canvas Apps? Your Creative Playground

Canvas Apps are like a blank sketchbook where you get to design every detail. Using Power Apps Studio, you can drag and drop buttons, images, and forms to create an app that looks exactly how you want. It’s all about freedom and creativity!

Cool Features of Canvas Apps

• Design Your Way: You control where everything goes—perfect for making apps that match your brand or fit specific devices like phones or tablets.
• Power Fx Magic: This is Microsoft’s easy-to-use formula language that lets you add smart features, like filtering lists or triggering actions.
• Tons of Connections: Link your app to over 1,000 data sources, like SharePoint, Excel, Dynamics 365, or even non-Microsoft tools like Google Workspace.
• What’s New in 2025:
  • Better Undo/Redo (April 2025): You can undo up to 100 actions, and each one comes with a description to keep things clear.
  • Copilot Helper (April 2025): Update data or tweak layouts without leaving the canvas—super handy for quick edits.
  • Smart Paste (March 2025): Paste a screenshot or handwritten note, and AI fills in forms for you, cutting data entry time by 29%, per Microsoft’s tests.
  • Teamwork Mode (March 2025): Work on apps with your team in real time, so you don’t have to merge changes manually.

Real-Life Examples

Canvas Apps are great when you need a custom look or mobile-friendly features:

• Field Service App: A delivery company might build an app for drivers to log orders, scan barcodes, or upload photos, all with a sleek mobile design connected to SharePoint.
• Event Lead Tracker: Sales teams can create an app to collect leads at a conference, syncing them instantly to Dynamics 365.
• Inventory Dashboard: A store could design a custom dashboard with charts and buttons to track stock levels, tailored for managers.

Why They Rock

• Super Customizable: Make your app look unique and match your company’s vibe.
• Flexible Connections: Works with tons of data sources, not just Microsoft ones.
• Mobile-Friendly: Perfect for apps that need to shine on phones or tablets.

Things to Watch Out For

• Takes Some Learning: You’ll need to get comfy with Power Fx and data connections to build complex apps.
• Data Limits: By default, you can only pull 500 records for some queries. Fix: Use “delegable” queries to let the data source handle the heavy lifting.
• Offline Glitches: The Connection.Connected formula might act up offline in Power Apps for Windows. Fix: Add a Timer control to delay certain actions.

What Are Model-Driven Apps? Your Structured Superhero

Model-Driven Apps are all about keeping things organized and quick. Instead of focusing on design, you set up your data and processes, and the platform builds a clean, consistent app for you. It’s perfect for big, data-heavy projects.

Cool Features of Model-Driven Apps

• Data-First Design: Built on Microsoft Dataverse, these apps handle complex data like customer records or project tasks with ease.
• Ready-Made Layouts: The app creates a user-friendly interface that works on any device, so you don’t have to design every screen.
• App Designer: Add forms, charts, or dashboards with a simple visual tool, making development fast.
• What’s New in 2025:
  • Copilot Chat with Multimedia (March 2025): Interact with your data using text, images, or videos for a richer experience.
  • Managed Availability (March 2025): Keeps your app running with automatic backups and disaster recovery, great for big teams.
  • Power CAT Tools (March 2025): A set of tools to make building apps easier with proven tips and tricks.

Real-Life Examples

Model-Driven Apps are awesome for structured, process-focused projects:

• Employee Onboarding: HR can build an app to track new hires, training, and IT setup, with all data neatly linked in Dataverse.
• Sales Tracking: Sales teams can manage leads, deals, and customer info, moving smoothly between related records.
• Healthcare Management: Clinics can create apps to handle patient records, appointments, and treatments, keeping everything secure and organized.

Why They Rock

• Fast to Build: Prebuilt layouts and tools mean you’re up and running quickly.
• Great for Big Data: Handles complex data relationships like a pro.
• Consistent Look: The same clean interface works everywhere, making it easy for users to learn.

Things to Watch Out For

• Less Design Freedom: You can’t tweak the look as much as with Canvas Apps.
• Custom Page Issues: Adding Canvas features to Model-Driven Apps (called custom pages) might not show updates until you republish. Fix: Republish the app after changes.
• Mobile Limits: Custom pages don’t support offline mode or features like barcode scanning on mobile. Fix: Stick to online mode or avoid those features.
• Hierarchy Tool Going Away (October 2025): A feature for showing data relationships is being removed. Fix: Turn it on in settings for now, but plan to switch soon.

Canvas vs. Model-Driven: A Quick Comparison

Feature	Canvas Apps	Model-Driven Apps
Design Style	Build your own UI, total control	Data-driven, auto-generated UI
Customization	Tons of design and logic options	Limited design, focused on data
Build Speed	Slower for complex apps due to custom work	Faster with prebuilt components
Data Connections	1,000+ sources, very flexible	Mainly Dataverse, great for complex data
Best For	Custom mobile apps, unique designs	Enterprise apps, structured processes
Learning Curve	Moderate (Power Fx, connectors)	Easier (app designer, less design work)
2025 Updates	Smart Paste, Coauthoring, Copilot	Copilot Chat, Managed Availability

Real-World Examples: Which One to Pick?

Choosing between Canvas and Model-Driven Apps depends on what you’re trying to do. Here are two examples to help you decide:

Example: Mobile App for Field Workers

• What You Need: A mobile app for technicians to log job details, take photos, and scan barcodes, with a custom look.
• Best Choice: Canvas App
• Why? You can design a mobile-friendly interface and add features like camera support. The 2025 Smart Paste feature makes data entry faster, and you can connect to SharePoint or Dynamics 365. For instance, a delivery company cut job logging time by 25% with a Canvas App tailored for drivers.

Example: Sales Management System

• What You Need: An app to manage leads, deals, and customer data for a big sales team.
• Best Choice: Model-Driven App
• Why? It’s perfect for handling complex data like customer relationships in Dataverse. The 2025 Copilot Chat feature makes data exploration easy, and Managed Availability ensures the app stays online for global teams. A company might reduce sales cycle time by 20% with this setup.

Common Issues and Fixes

Both app types have some quirks, but here’s how to handle them:

• Canvas Apps:
  • Problem: Some queries only pull 500 records. Fix: Use delegable queries or split up your data.
  • Problem: Offline mode can glitch with connection checks. Fix: Add a Timer to delay actions.
• Model-Driven Apps:
  • Problem: Custom pages don’t update until republished. Fix: Republish the app after changes.
  • Problem: Custom pages don’t work offline on mobile. Fix: Use online mode for now.

Try the Monitor tool for both app types to track down issues like slow loading or data errors.

Tips to Choose the Right App Type

1. Go for Canvas Apps if:
   • You want a custom, branded design.
   • Your app needs mobile features like camera or GPS.
   • You’re connecting to various data sources.
   • Example: A retail app with a unique loyalty dashboard.
2. Go for Model-Driven Apps if:
   • You need to manage complex data or business processes.
   • You want a fast build with a standard look.
   • You’re using Dataverse or Dynamics 365.
   • Example: A CRM app for customer management.
3. Try a Mix:
   • Use custom pages to add Canvas features to a Model-Driven App, like a quick-entry form in a sales app. Just remember to republish after updates (a 2025 quirk).
4. Test New Features:
   • Set up a Developer Environment to play with 2025 features like Canvas Coauthoring or Copilot Chat. Check out make.powerapps.com and enable the “Try the new Power Apps experience” option.

Wrap-Up

Canvas Apps and Model-Driven Apps are both amazing tools in the Microsoft Power Platform, but they serve different purposes. Canvas Apps are your go-to for creative, custom designs, especially for mobile users. Model-Driven Apps are the way to go for quick, data-heavy apps with a consistent look. With cool 2025 updates like Copilot, Smart Paste, and better teamwork tools, both options are more powerful than ever.

Ready to start building? Head to make.powerapps.com to try things out, or check Microsoft’s guides for step-by-step help. If your project’s complex, consider chatting with a Power Apps pro to get it just right. Which app type are you leaning toward? Drop your thoughts or project ideas in the comments!

Power Apps and Dynamics 365 Licensing

🔹 Dynamics 365 and Power Platform Licensing – Detailed Breakdown

I will be honest — Microsoft licensing wasn’t always my favorite topic. Like many Power Apps developers, I focused on building solutions, not figuring out who’s allowed to use what.

A few months ago, I was leading a Power Apps project, during a project review meeting, questions started piling up:

• “Can’t we just give everyone Power Apps licenses instead of Dynamics licenses to save cost?”
• “Can a Team Member run this flow?”
• “Is this Dataverse table covered by our license?”
• “Do we need a Sales license just to store contact data?”

That’s why I’m writing this post. I’m writing this post because I’ve seen firsthand how confusing licensing can be. I’ve seen organizations spend weeks in building apps, and realize later that users aren’t even licensed to run them. Others overspend on licenses just to be safe, or under-license out of ignorance. In this blog i tried to break down the licensing into plain English — grounded in real project experience — so you can make decisions right from the start.

🔹 1. Power Apps Per User License: What Can You Do?

If a user has a Power Apps per user license, they can:

• Build and run unlimited custom apps using Dataverse.
• Use premium connectors (like SQL Server, Dataverse, HTTP, etc.).
• Create workflows using Power Automate.

Important note: If you're building apps that use data from the same tables used by D365 Sales, that's fine — as long as you don’t use the full Sales app experience.

Dynamics 365 Sales is a packaged solution. So while Power Apps lets you read/write Sales data through your own custom apps, it does not give access to the full Sales interface or built-in processes.

✅ OK: Custom canvas or model-driven apps using Dataverse.
❌ Not OK: Using the full D365 Sales app UI or mimicking its full functionality.

🔹 2. Dynamics 365 Sales Enterprise License: What’s Included?

The D365 Sales Enterprise license gives users:

• Full use of the packaged Sales app.
• Rights to build and use custom Power Apps.
• Access to Power Automate and premium connectors.

This means users can build apps, automate flows, and extend the Sales module — all without needing a separate Power Apps license.

🔹 3. D365 Customer Service Enterprise: Same Rules Apply

The Customer Service Enterprise license works the same way as Sales Enterprise.

Users can:

• Use the full Customer Service app.
• Build custom apps and flows for service-related tasks.
• Access Dataverse and premium connectors.

No additional licensing needed for building extended solutions here either.

🔹 4. Dynamics 365 Team Member License: What Can’t You Do?

This is a lightweight license meant for basic tasks like:

• Viewing data
• Entering notes or time entries
• Reading dashboards

However, users with this license cannot:

• ❌ Build or run custom apps that access restricted tables (like Opportunity or Case).
• ❌ Use Power Automate flows with premium connectors.
• ❌ Run apps that replicate full D365 Sales/Service features.

Bottom line: This is for occasional users only — not for app builders or power users.

✅ Quick Summary Table

User License	Can Use Custom Apps?	Can Use D365 Apps?	Use Premium Connectors?	Custom Flows Allowed?
Power Apps Per User	✅ Yes, for custom data	❌ No, for full D365 apps	✅ Yes	✅ Yes
D365 Sales Enterprise	✅ Yes	✅ Yes	✅ Yes	✅ Yes
D365 Customer Service	✅ Yes	✅ Yes	✅ Yes	✅ Yes
D365 Team Member	⚠️ Limited	⚠️ Limited	❌ No	⚠️ Very Limited

Fixing the “No Name” Issue When Setting RegardingObjectId in Dataverse Plugins

When building plugins for Microsoft Dataverse, setting lookup fields like regardingobjectid can be tricky—especially with polymorphic lookups. A common issue developers face is seeing “No Name” in the UI even after setting the lookup value. This blog post explores why this happens and how to handle it properly in your plugin code.

The Problem

Suppose you’re assigning a broker to an Appointment record using a plugin. Your code might look like this:

EntityReference brokerRef = (EntityReference)appointmentEntity["crm_broker"];
appointmentEntity["regardingobjectid"] = new EntityReference(brokerRef.LogicalName, brokerRef.Id);

This sets the lookup correctly in terms of entity and ID, but the regardingobjectid shows up as “No Name” in the UI. Why?

The Cause

The EntityReference object also has a Name property, which is what the UI uses to display the label. In a Pre-Operation plugin, the record isn’t fully committed to the database yet, so Dataverse doesn’t resolve or populate this display name automatically for polymorphic lookups like regardingobjectid.

The Fix

To resolve this, explicitly retrieve the name, and all dependent attributes of the target record and assign it when setting the EntityReference:

EntityReference brokerRef = (EntityReference)appointmentEntity["crm_broker"];
Entity broker = service.Retrieve(brokerRef.LogicalName, brokerRef.Id, new ColumnSet("name"));
string brokerName = broker.GetAttributeValue<string>("name");

appointmentEntity["regardingobjectid"] = new EntityReference(brokerRef.LogicalName, brokerRef.Id)
{
    Name = brokerName
};

Why This Works

• UI rendering depends on the Name property of the lookup reference. If it's missing, the form defaults to displaying "No Name".
• In the Pre-Operation stage, the record and its references haven’t been persisted yet—so polymorphic lookups can't be resolved unless you provide the metadata yourself.
• By manually setting the Name, you ensure the UI has what it needs to render the label correctly.

Additional Tips

• ✅ Stage Awareness: Consider setting the regardingobjectid in a Post-Operation plugin if possible. This guarantees the record is committed and lookups are more reliably resolved.
• ✅ Check Permissions: Ensure your plugin has adequate permissions to retrieve the broker entity’s name field.
• ✅ Avoid UI Confusion: Even after correcting the plugin, browser caching or form loading issues might delay UI updates. Refresh the form or clear the cache to see changes.

Final Thoughts

Handling lookup fields—especially polymorphic ones like regardingobjectid—requires attention to detail. By explicitly setting the Name in your EntityReference, you ensure smoother user experiences and cleaner data presentation.

Still seeing “No Name”? Drop a comment or reach out—I’m happy to help you debug it further!