+1 480 485 7373
Microsoft Teams
Canvas or model-driven Power Apps?
Power Apps we are asked to build
Receiving and counts
Scan a barcode and confirm quantities against the purchase order in Business Central. Then take a photo of damage and post the receipt, all from one screen.
- ✓Barcode scanning with the device camera
- ✓Photo capture to SharePoint
- ✓Offline capture where signal is poor
Inspections and checklists
Step-by-step inspection forms with pass or fail rules, signatures and automatic follow-up tasks when something fails.
- ✓Conditional questions
- ✓Signature capture
- ✓Follow-up actions through Power Automate
Requests and approvals
A structured form collects purchase requests, new vendor requests or credit applications. After checks and approval, the app creates them in Business Central.
- ✓Role-based screens
- ✓Approval history
- ✓Duplicate checks before creation
Job and time capture
Technicians or consultants record time, materials and notes against jobs or projects. The lines then land in Business Central journals for review.
- ✓Job and task pickers
- ✓Mileage and expense lines
- ✓Manager review before posting
Power Apps development for Dynamics 365: design choices that decide whether an app lasts
The first choice is where the data lives. Writing straight to Business Central keeps a single source of truth. But every screen then depends on its permissions and response times. Staging data in Dataverse gives offline support and richer security. The cost is a second copy to keep in step. Business Central virtual tables in Dataverse sit between the two.
The second is delegation. Canvas apps push filtering to the data source only for supported functions. Anything else runs on the first batch of records the app downloads. That batch is 500 by default and 2,000 at most. An item lookup that works in testing can silently miss records in production. We design queries so the source does the filtering.
The third is licensing. Apps that use Dataverse or premium connectors need a Power Apps premium or per-app license for every user. For a shop floor app with a large crew, that can change the business case. So we settle it on paper before anyone draws a screen.
How a Power Apps developer builds an app
- 1
Watch the task being done today
We sit with the people who will use the app and count the taps they need. We also note where gloves, poor signal or bright light will get in the way.
- 2
Sketch and agree
As your Power Apps developer, we show users a clickable prototype with your real field names. That happens before we build the data layer. Changing a sketch is free; changing a finished app is not.
- 3
Build inside a solution
We package apps, flows, tables and environment variables in one solution and keep it in source control. Then it moves from test to production without manual rebuilding.
- 4
Hand it over with a runbook
Your administrator gets the solution and a description of each screen and data connection. They also get the steps to add users or change a threshold.
Hiring a Power Apps developer: common questions
Why not just use the Business Central mobile app?
Often you should. The Business Central app on iOS and Android shows the same role centers and pages as the browser. A Power App earns its place when the task needs a simpler screen than a full ERP page. It also helps for users without a Business Central license, or for data from several systems.
Can people without a Business Central license use the app?
Only within Microsoft's licensing rules. The app still connects to Business Central through an account. And Microsoft's multiplexing rules say users who reach that data indirectly still need a suitable license. We explain the published rules for your scenario and your licensing partner confirms the detail.
Does it work offline?
Yes. In Power Apps development for Dynamics 365, canvas apps can work offline if the developer builds them for it. Dataverse makes the most reliable data source. The app stores records on the device and syncs when a connection returns. However, the design must plan for conflicts, where two people change the same record.
Who can maintain the app after you hand it over?
Anyone comfortable with Excel formulas can learn to make small changes in a canvas app. So we show your administrator how. Structural changes, new tables or new integrations are better done in a test environment first, and we document how to do that.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.