D365ConsultantDivision of Sataware
Talk to an expert
Small apps, real data

A Power Apps developer for the screens your ERP does not have.

A Power Apps developer builds focused apps for tasks that do not justify a full ERP user or a full ERP screen: a receiving check on a tablet, a site inspection form, a simple request portal for staff. Our apps read and write Business Central and Dynamics 365 data directly, so nothing is retyped later. We also tell you when a standard Business Central page or the mobile app already does the job.

Canvas and model-driven
the two main Power Apps types
Power Fx
Excel-style formula language behind canvas apps
Dataverse
the database behind model-driven apps
Hand holding a tablet showing a calendar app

Canvas app or model-driven app?

Canvas app
Model-driven app
Starts from
A blank screen you lay out
Your data model in Dataverse
Best for
Task apps on phones and tablets
Case, request and record management
Data sources
Many connectors, including Business Central
Dataverse, plus virtual tables
Look and feel
Fully custom
Standard forms and views
Typical users
Warehouse, field and shop floor staff
Office teams handling many records
Watch out for
Delegation limits on large lists
Dataverse storage and licence needs

Apps we are asked to build

Warehouse

Receiving and counts

Scan a barcode, confirm quantities against the purchase order in Business Central, 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
Quality

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
Office

Requests and approvals

Purchase requests, new vendor requests or credit applications collected in a structured form, checked, then created in Business Central after approval.

  • βœ“Role-based screens
  • βœ“Approval history
  • βœ“Duplicate checks before creation
Field

Job and time capture

Technicians or consultants record time, materials and notes against jobs or projects, and the lines land in Business Central journals for review.

  • βœ“Job and task pickers
  • βœ“Mileage and expense lines
  • βœ“Manager review before posting
Woman tapping a tablet screen while seated
Tablet apps put ERP data in the hands of people who never sit at a desk

Design decisions that decide whether the app lasts

The first choice is where the data lives. Writing straight to Business Central through its connector or API keeps a single source of truth, but every screen then depends on Business Central permissions and response times. Staging data in Dataverse gives offline support and richer security, at the cost of 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 is applied to the first batch of records the app downloads, which 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 licence for every user. For a shop floor app used by a large crew, that can change the business case, so it is settled on paper before any screen is drawn.

How an app gets built

  1. 1

    Watch the task being done today

    We sit with the people who will use the app, count the taps they need, and note where gloves, poor signal or bright light will get in the way.

  2. 2

    Sketch and agree

    A clickable prototype with your real field names is shown to users before the data layer is built. Changing a sketch is free; changing a finished app is not.

  3. 3

    Build inside a solution

    Apps, flows, tables and environment variables are packaged in one solution, stored in source control, and moved from test to production without manual rebuilding.

  4. 4

    Hand it over with a runbook

    Your administrator gets the solution, a description of each screen and data connection, and 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, a user who does not hold a Business Central licence, or data from several systems in one place.

Can people without a Business Central licence 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 that users reaching Business Central data indirectly still need an appropriate licence. We explain the published rules for your scenario and your licensing partner confirms the detail.

Does it work offline?

Canvas apps can work offline when they are built for it, most reliably with Dataverse as the data source. The app stores records on the device and syncs when a connection returns. Conflicts, where two people change the same record, have to be designed for, not left to chance.

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, and 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.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.