Standard Operating Procedure: Power Apps Enterprise Timesheet Template

STANDARD OPERATING PROCEDURE: Power Apps Enterprise Timesheet Template Deployment

DOCUMENT CONTROL BLOCK:
  Document ID: SOP-TR-PA-8802
  Effective Date: October 24, 2023
  Version: 3.2.0
  Review Cadence: Semi-Annual
  Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional engineering standard for deploying, configuring, and maintaining the Enterprise Timesheet Template within Microsoft Power Apps. The objective is to establish a secure, scalable, and audit-compliant time-tracking infrastructure integrated with Microsoft Dataverse and Azure DevOps/Active Directory, mitigating payroll discrepancies and data drift.

---

2. Scope & Prerequisites

2.1 Scope

This document applies to all enterprise environments utilizing the Template Registry Timesheet Canvas/Model-driven Power App across global operations.

2.2 Prerequisites & Tooling

• Licensing: Power Apps Per User / Per App license or Microsoft 365 E3/E5 subscription.
• Permissions: Power Platform Administrator, Environment Maker, and System Customizer roles within the target environment.
• Data Source: Microsoft Dataverse (Preferred) or SharePoint Online (Legacy fallback).
• Tooling: Power Apps Studio, Visual Studio Code (for PCF component updates), PowerShell (Power Apps Admin module).

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Environment Provisioning & Solution Import

• 1.1 Verify target environment is provisioned with a Dataverse database and appropriate security groups.
• 1.2 Download the certified Timesheet Template solution package (.zip) from the Template Registry secure repository.
• 1.3 Navigate to the Power Apps Maker Portal, select the target environment, and click Solutions.
• 1.4 Click Import, select the solution file, and click Next.
• 1.5 Map connection references to active organizational service principals or administrative credentials.
• 1.6 Click Import and wait for the verification success banner. Confirm zero dependency errors.

Phase 2: Data Schema & Security Configuration

• 2.1 Open the imported solution and navigate to the Timesheet Header and Timesheet Line Items tables.
• 2.2 Validate column schemas: Ensure msft_totalhours is set to calculated roll-up, and msft_approvalstatus uses the global Choice set (Draft, Submitted, Approved, Rejected).
• 2.3 Assign Dataverse Security Roles: Associate Timesheet Standard User to all employees and Timesheet Approver to line managers.
• 2.4 Enable row-level security (RLS) filters on the Timesheet Header table based on the Owner field (Owner = User()).

Phase 3: Canvas App Configuration & Formula Optimization

• 3.1 Launch the Timesheet Canvas App in Power Apps Studio.
• 3.2 Update the OnStart property of the App object to optimize data caching:

  Set(varUserEmail, User().Email);
  ClearCollect(colProjects, 'Project Registry');
  ClearCollect(colTimeCodes, 'Time Type Definitions');
  

• 3.3 Verify Delegation limits: Ensure all gallery items querying Dataverse use delegable functions (e.g., Filter, Sort) without exceeding the 2,000-row threshold limit.
• 3.4 Test the grid matrix control for input validation (restrict hours entry per day to 0 <= x <= 24 and total weekly hours to 168).

Phase 4: Power Automate Approval Workflow Integration

• 4.1 Open the associated cloud flow: TR_Timesheet_Approval_v3.
• 4.2 Configure the trigger condition to execute strictly on Dataverse row creation/modification where Approval Status equals Submitted.
• 4.3 Update the "Start and wait for an approval" action to route dynamically using Azure Active Directory manager hierarchy (Office 365 Users connector -> Get Manager (V2)).
• 4.4 Implement error handling (Scope/Configure run after) to catch rejection timeouts and route unhandled exceptions to the IT Service Desk.

Phase 5: User Acceptance Testing (UAT) & Deployment

• 5.1 Execute test script TS-UAT-01: Create, edit, submit, recall, and approve a standard 40-hour weekly timesheet.
• 5.2 Validate offline persistence behavior using Power Apps Mobile on iOS and Android test devices.
• 5.3 Publish the application production version and share with the pilot user group.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Delegation Hygiene: Always construct galleries using delegable parameters. Avoid non-delegable functions like Search() on large datasets exceeding 50,000 rows.
• Variable Scoping: Minimize the use of global variables (Set); leverage context variables (UpdateContext) within screens to preserve memory overhead.

5.2 Common Pitfalls

• Hardcoding GUIDs: Never hardcode environment-specific GUIDs for Choice options or Project references within Canvas App formulas; utilize environment variables instead.
• Concurrent Editing: Failing to implement optimistic concurrency checks can lead to data overwrites during simultaneous manager-employee edits.

5.3 Metric Thresholds

• App Load Time (Cold Start): < 3.5 seconds.
• Dataverse Query Response: < 800 milliseconds.
• Workflow Execution Time: < 5.0 seconds from submission to approval notification dispatch.

---

6. Frequently Asked Questions

Q1: Why are users experiencing delegation warnings on the timesheet line-item gallery?

A: This occurs when using non-delegable functions like Search or complex Text operations on unindexed Dataverse columns. Ensure search inputs target indexed columns (e.g., Name, CreatedOn) or refactor queries to use delegable Filter logic.

Q2: How do we handle retro-active timesheet adjustments after payroll has locked the period?

A: Financial locks are enforced via Dataverse business rules and plugin logic. To adjust a locked period, an authorized payroll administrator must execute the Unlock Timesheet canvas command, which automatically generates an audit log entry referencing the administrative override ID.