Building Your First Power App: A Guide for Access Developers
Power Apps looks nothing like Access at first. But the concepts map more closely than you might expect. Here is how to build your first canvas app if you already know Access.
The first time an Access developer opens Power Apps, the reaction is usually some version of: "Where is everything?"
There is no Design View. No query grid. No VBA editor. The interface looks more like PowerPoint than Access. And yet Power Apps can do most of what Access does — often better — once you understand how it thinks.
This post maps Access concepts to Power Apps concepts and walks through building a simple canvas app from scratch.
Canvas Apps vs. Model-Driven Apps
Power Apps has two main types: canvas apps and model-driven apps.
Canvas apps give you a blank canvas. You place controls exactly where you want them, connect to data sources, and write formulas to define behavior. This is the closest equivalent to Access — you design the UI, you control the layout, you write the logic.
Model-driven apps are generated from your Dataverse data model. You define tables and relationships, and Power Apps generates forms and views automatically. Less design control, but faster to build for standard CRUD applications.
For Access developers, canvas apps are the natural starting point. They feel more like building something from scratch, which is what Access developers are used to.
The Power Apps Mental Model
Before building, understand the key conceptual shifts:
Screens, not forms. Power Apps has screens where Access has forms. A screen is a full-page view. You navigate between screens the way you navigate between forms in Access.
Galleries, not continuous forms. A Gallery control displays a list of records — the equivalent of a continuous form or datasheet view in Access. Each item in the gallery is a template that repeats for each record.
Power Fx, not VBA. Power Apps uses Power Fx — a formula language based on Excel functions — instead of VBA. If(Status = "Active", Green, Red) instead of If Me.Status = "Active" Then.... It is reactive: formulas recalculate automatically when data changes, like Excel cells.
Data sources, not linked tables. You connect to data through connectors — Dataverse, SQL Server, SharePoint, Excel, and hundreds of others. The connection is configured once; controls bind to it through formulas.
Setting Up: Connect to Your Data
Start by connecting to your data source. For a migrated Access database, this is typically Dataverse or SQL Server.
- Go to make.powerapps.com
- Click Create > Canvas app from blank
- Name your app and choose Tablet or Phone layout
- In the left panel, click Data > Add data
- Search for your connector (Dataverse, SQL Server, SharePoint)
- Authenticate and select your tables
Your tables are now available as data sources. Reference them in formulas by name.
Building a List Screen
The most common first screen: a list of records with a search box.
Add a Gallery:
- Insert > Gallery > Vertical
- In the Items property, enter your data source name:
Customers - The gallery populates with your data
Bind fields to the gallery template:
- Click the gallery, then click the pencil icon to edit the template
- Select the Title label, set its Text property to
ThisItem.LastName & ", " & ThisItem.FirstName - Select the Subtitle label, set its Text to
ThisItem.Email
Add a search box:
- Insert > Input > Text input
- Name it
txtSearch - Change the gallery's Items property to:
Filter(Customers, StartsWith(LastName, txtSearch.Text) || StartsWith(FirstName, txtSearch.Text))
The gallery now filters in real time as the user types. No VBA, no event handlers — the formula recalculates automatically.
Building a Detail/Edit Screen
When a user taps a record in the gallery, they should see a detail or edit screen.
Add a new screen: Insert > New screen > Blank
Add a Form control:
- Insert > Forms > Edit
- Set the DataSource property to
Customers - Set the Item property to
Gallery1.Selected(the record selected in the gallery on the previous screen) - The form populates with fields from the Customers table automatically
Add navigation from the gallery to the detail screen:
- Go back to the list screen
- Select the gallery's arrow or the template area
- Set the OnSelect property to:
Navigate(Screen2, ScreenTransition.Fade)
Add Save and Cancel buttons on the detail screen:
Save button OnSelect:
SubmitForm(Form1); Navigate(Screen1, ScreenTransition.Back)
Cancel button OnSelect:
ResetForm(Form1); Navigate(Screen1, ScreenTransition.Back)
Add a New Record button on the list screen:
OnSelect:
NewForm(Form1); Navigate(Screen2, ScreenTransition.Fade)
You now have a functional list-and-detail app: browse records, tap to edit, save changes back to the data source.
Power Fx: The Formula Language
Power Fx is the biggest adjustment for Access developers. Here are the most common patterns:
Filtering data:
Filter(Orders, CustomerID = Gallery1.Selected.CustomerID)
Conditional display:
If(ThisItem.Status = "Active", RGBA(0,128,0,1), RGBA(128,0,0,1))
Concatenation:
ThisItem.FirstName & " " & ThisItem.LastName
Date formatting:
Text(ThisItem.OrderDate, "mmm d, yyyy")
Lookup (equivalent to DLookup):
LookUp(Customers, CustomerID = Gallery1.Selected.CustomerID, CompanyName)
Counting records:
CountRows(Filter(Orders, Status = "Pending"))
Patching a single field (equivalent to a targeted UPDATE):
Patch(Orders, Gallery1.Selected, {Status: "Closed"})
Power Fx is case-sensitive and uses semicolons as argument separators in some locales. The formula bar in Power Apps shows errors inline as you type — use it to validate formulas before running the app.
Variables: Global and Context
Power Apps has two types of variables:
Global variables — available across all screens. Set with Set(varName, value). Use sparingly; overuse makes apps hard to debug.
Context variables — scoped to the current screen. Set with UpdateContext({varName: value}). Preferred for screen-level state.
// Set a global variable
Set(gblCurrentUser, User().Email)
// Set a context variable
UpdateContext({locShowDetails: true})
// Use in a formula
If(locShowDetails, DetailPanel.Visible, false)
Collections: In-Memory Tables
Collections are in-memory tables — the Power Apps equivalent of a recordset you build in VBA. Useful for staging data before saving, or for data that does not need to persist.
// Create a collection from a data source
ClearCollect(colPendingOrders, Filter(Orders, Status = "Pending"))
// Add a row
Collect(colPendingOrders, {OrderID: 999, Status: "Pending", CustomerID: 42})
// Clear it
Clear(colPendingOrders)
Common Gotchas for Access Developers
Delegation. Power Apps can only process a limited number of records client-side (500 by default, up to 2,000). For large data sources, filters and sorts must be "delegable" — supported server-side by the connector. Non-delegable formulas show a yellow warning and may return incomplete results. Check delegation warnings carefully.
No transactions. Power Apps does not have the equivalent of BeginTrans / CommitTrans. For multi-table updates, use Power Automate flows, which can handle transactional logic more reliably.
Formulas are not sequential. Unlike VBA where code runs line by line, Power Fx formulas are declarative — they describe what should be true, not what steps to take. This requires a different way of thinking about logic.
Testing is in the browser. Press F5 or the Play button to test your app. Changes save automatically. There is no compile step.
The Learning Curve Is Real — and Worth It
Power Apps takes a few weeks to feel natural if you come from Access. The formula language, the reactive model, the delegation constraints — these all require adjustment.
But the payoff is significant: apps that run on any device, connect to cloud data sources, integrate with Teams and Outlook, and do not require a Windows machine with Access installed. The ceiling is much higher than Access, and the floor — once you get past the learning curve — is not as low as it first appears.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Want hands-on help building your first Power App from an Access database? Schedule a free call and skip the trial-and-error.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Power Platform
Dataverse Explained for Access Developers
Dataverse is the database behind Power Apps. If you are migrating from Access, understanding how Dataverse tables, relationships, and security differ from Access is essential.
Migrating Access Reports to Power BI
Access reports are powerful but static. Power BI replaces them with interactive dashboards that refresh automatically. Here is how to make the transition without losing your reporting logic.
Access to Power Apps Migration: What Actually Takes the Longest
Everyone focuses on the data migration. But in an Access to Power Apps project, the data is rarely what takes the most time. Here is where the hours actually go.