Power Apps work tracking.
See the work. Make an update.

Four related Dataverse tables

Companies · 6 records

The company details. One company can have several engagements, or projects. Each engagement in this demo belongs to one company.

Engagements · 12 records

A piece of delivery work, with stage, health, target date, budget hours and actual hours. Each engagement connects its work items and dated updates.

Work items · 36 records

Tasks linked to an engagement, with an assignee, status, due date and estimated hours. The sample has three work items per engagement.

Status updates · 60 records

Five dated reporting snapshots per engagement, each with health, a summary and a next step. These sample snapshots are separate from work-item changes. They are not an audit log created when someone saves in Canvas.

Two private apps, different tasks

Model-driven app: see the full picture

Quintera Operations Demo shows companies and engagements with their related work and updates. A manager can start with the needs-attention or overdue views, then open a flagged record to see more.

Canvas app: update an existing work item

In the September 24 version shown here, Quintera Field Update offers search, selection and four editable fields: Assignee, Status, Due date and Estimated hours. The item name, sample ID and engagement stay read-only. That version does not create or delete work items.

Both apps use the same Dataverse work-item record. A saved status was checked after reloading in both apps. Tests also checked Cancel and what happens when the assignee is left blank. The public explorer above is a separate read-only web example. It does not open or update either app.

Follow one work item

1. Find the project. In the sample explorer, reset the filters and search “approval”. Choose Approval tracker pilot for Beacon Harbor Services. This invented engagement, QE003, is in Build and marked At risk.
2. Inspect the work. Its three work items are QW007, QW008 and QW009. QW008, “Build and review the sample”, is assigned to Nadia Lark, In progress and due September 18, 2026, with 28.8 estimated hours. It is overdue at the fixed demo date.
3. Read the reporting history. Choose Status timeline to see the engagement’s five snapshots, newest first. Past health values may differ from the current one. Use the summary and next step to guide the next discussion.
4. Read how the private app update worked. In the completed app test, QW008 changed from In progress to Blocked in Canvas. The change stayed after a reload and appeared on the same record in the model-driven app. It was then changed back to In progress and checked again. Request a guided walkthrough to see that workflow.

Which records need attention?

• Needs attention: engagement health is At risk or Blocked. Five engagements meet that definition in the sample. Health is set separately from work-item status and delivery stage. The demo does not automatically calculate health from other records.
• Overdue work: status is not Done and the due date is strictly before September 23, 2026. Seven work items meet the rule. Done items are excluded; an unfinished item due on September 23 is due on the demo date, not overdue.
• Above budget: an engagement’s actual hours exceed its budget hours. Two sample engagements meet that rule. Work-item estimates are separate values, not hours to add to the actual total; none of these figures represents measured client performance.

The fixed date keeps the example consistent. For a real project, we would agree the reporting date, what each status means, who updates it and what to do about each flagged issue before building the view.