Microsoft Power Platform — Examples

Power Apps · Apps

The app, published. JPV Job Tracker — a model-driven Power Apps app I built and own, live in my environment. A real, published app, not a mock-up.

JPV Job Tracker · Active Job Applications

The running app showing the Active Job Applications list with two records and their status and dates.

The app in use. The live list of applications, with status and the dates that matter — add, edit and sort. Real data, not a demo.

New Job Application

Adding an application. The form Power Apps builds from the table — including the “next action” fields the reminder automation watches.

Dataverse · Job Application table

Field	Type	Purpose
Company	Text	The organisation (primary field)
Role title	Text	The advertised position
Advert ref	Text	The employer’s reference
Status	Choice	ResearchingAppliedInterviewOfferRejected
Applied / closing / interview	Date	The dates that matter
Next action	Text	The one thing to do next
Next action due	Date	The field the reminder flow watches
Advert URL · Notes	URL · Multiline	Link to the advert, and free notes

The data behind it. A deliberately plain Dataverse table — one row per application. The low-code equivalent of the database tables I design on AWS.

Power Automate · Morning job-hunt reminders

The Power Automate flow: Recurrence, then List rows, then For each with a Condition whose True branch sends an email and False branch is empty.

The automation. Daily at 08:00, for each application it emails only those whose action is due — True sends, False skips. Null-safe, so rows with no due date are ignored. Verified end-to-end.

Gmail · the reminder that arrives

The reminder email received in Gmail: subject Job application — action due today, with a short body pointing to the Job Tracker.

The reminder it sends. The actual email that lands the morning an action is due — one per item, so the tracker chases me.

Notes · decisions & a real debugging story

I stood up my own tenant, on purpose.: The platform needs a work/school account, so I created my own Microsoft Entra directory and a developer environment — covering the governance side (licensing, environments, permissions), not just the drag-and-drop.
No mailbox? Design around it.: A developer tenant has no Exchange mailbox, so the Outlook action wasn’t available. I used the Gmail connector instead — knowing why (a licensing boundary) is the judgement that matters.
I debugged a real failure.: First runs failed with a flat “bad request”. I’d put filter logic in a field that expects column names. I read the run history, traced it to the exact action, and re-tested to green.

Decisions & a real debugging story. The parts a tutorial doesn’t teach — governance, the right connector for a constraint, and reading a failure to fix it.

Microsoft Power Platform — Examples

Job Application Tracker