IT systems · Practical guide

Validating offline Power Apps: synchronisation and conflicts

An entry is saved on a mobile device, but the central record has yet to receive it. In a GxP process, the team needs to identify which state applies and when the record is ready for the next decision.

Table of contents

At a glance

How do you validate an offline-capable Power App?

Test the complete path from initial download and local input through synchronisation to central use. Define how conflicting edits, rejected updates, retries and device replacement should behave. This guide covers standalone Dataverse canvas apps using built-in offline-first capability. Other app types need their own assessment.

First define the App type and offline mechanism.

Power Apps includes various application types and offline procedures. A standalone Canvas App with integrated Dataverse offline-first is not equivalent to a Model App, an embedded Canvas App, or a custom solution using LoadData and SaveData. These differences impact data retention and error handling.

Microsoft describes the handling of local data in the integrated offline-first approach, even when a network connection is available. Initially, required data is downloaded; subsequently, synchronization with the server occurs. Therefore, the presence of an online network icon does not automatically indicate that every current local value has already been processed centrally.

Validation considers the intended process with app version, mobile client, device platform, offline profile, tables and extensions. For GMP-relevant applications data integrity, access, traceability and error handling are to be considered. The following test matrix is a separate technical derivative, not a universal Microsoft conformity list.

Sources: [1] [2] [3]

Locally stored, synchronized, and professionally usable differ

Define the states such that users can understand them. A dataset can be locally stored, pending transfer, centrally accepted, or rejected due to a rule. These states must not disappear from a single success message, as different professional actions may follow.

Define when a central decision may be based on documentation. In a testing process, for example, incompletely transferred results should not yet be included in the final conclusion. The app must provide appropriate display and process control for this. A green checkmark should convey a clearly defined statement.

Consider time and identity. Local entry time, server processing, and potentially a professional judgment are distinct events. Verify which time information is actually recorded and how the sequence can be reconstructed post hoc. A server timestamp alone does not always indicate when an observation occurred on-site.

Sources: [2] [3] [1]

Treat the Offline Profile as part of the validated scope

The offline profile determines which data are available on the device. Review not only the main table but also required references and relationships. A sample without the corresponding specification may be visible locally, while the technical evaluation remains incomplete.

Microsoft identifies limitations of the integrated workflow, for example with other connectors, specific table types, and offline usage of Power Automate flows. A server-side workflow is not available offline solely because the app functions online. Review the current limits for the actually utilized workflow capabilities.

Test with a representative user role. An automatically generated profile may allow the download of more data than is actually required for the specific application. Therefore, the scope, device data, and access procedures are jointly evaluated. A technical success in downloading does not confirm the appropriate professional selection.

Sources: [1] [4]

Example scenario: two individuals modify the same inspection dataset

User A uploads inspection dataset P-41 to their device and works offline. User B centrally updates the status. Later, User A modifies a measurement value and synchronizes. It must be determined which combination of measurement value and status is professionally valid and how it is verified.

Microsoft describes, for the considered synchronisation context, a column-wise update: the most recent update for each column is stored; server-side validation or plug-ins may reject changes. Therefore, automatic technical conflict resolution does not automatically prevent a professionally inconsistent combination of values across different fields.

Run two variants. In Variant one, A and B modify the same column. In Variant two, A and B modify different, professionally related columns. Document the sequence, local and central values, as well as the actually achieved outcome. The required value is determined by the internal process rule, not established retrospectively after observing the platform.

Own conflict matrix for P-41
SituationTechnical InquiryObservable evidence
Same column, two changes Which version may be considered decisive? Order, final value, and traceability
Local measurement value, central status Is the resulting combination permissible? Common Consistency and Further Use
Server rejects local modifications How is the process addressed? Sync errors, local drop and processing issues
Repeat upon termination Does a dual procedure occur? Identity and Central Processing
Reference centrally amended May work continue with an outdated local version? Reference baseline and usage limit

Sources: [5] [2]

Error remediation is part of the process.

Microsoft describes a Sync-Error table and the required read rights for its use. For Canvas Apps, the appropriate status display must be configured. Verify that the intended user or the relevant editing role can actually detect, assign, and edit errors.

A repeat button alone does not resolve a professional conflict. If a server plug-in rejects an unauthorized change, the root cause must be investigated. Define who evaluates local entries, central site status, and required corrections. Automated notifications can assist but do not replace manual review.

Investigate the complete error pathway using a targeted invalid update. The record must remain retrievable according to the agreed procedure. Upon correction, verify that the correct central state is achieved and that no additional process is inadvertently created. Also document the business decision regarding rejected or re-entered data.

Sources: [5] [2]

Plan a test sequence from first start to equipment changeover

Begin with the initial download. Perform a complete run and a interruption scenario. The app may only be considered ready for the intended offline process when all required data and references are available. A started download does not constitute verified readiness for use.

Generate local data sets without connectivity, switch the network, and monitor central processing. Also test app restart, locked screen, and actual synchronization conditions. The documentation specifies limits for regular background synchronization; do not rely on an unverified assumption that a powered-off screen fully transfers all data.

In the event of device loss or replacement, a procedure for handling untransferred records must be established. A new device may only utilize data that is actually made available to it. Assess local data protection, potential recovery options, and technical handling of lost inputs within the specific process.

Own inspection procedure for the entire offline lifecycle
Testing phaseTargeted test caseAcceptance criterion in the example
Erst-Sync Download interrupted Incomplete preparation evident
Offline entry The network completely isolated Local record clearly documented
Reconnection Several pending amendments Correct central assignment and status
Server rule A deliberately invalid value Rejection visible and editable
Client-Reset App with pending data to restart The intended data set remains traceable.
Equipment changeover Account for a transaction that has not synchronised Limits and clarification procedures known

Sources: [1] [4]

Define release criteria and subsequent modifications

The evidence package includes app and profile status, data model, roles, process rules, test inputs, and results. The boundaries are explicitly defined: supported devices, required references, permissible offline duration as per internal rules, and prerequisites for central usage.

A professionally defined offline duration is not a general regulatory numerical value. It depends among other factors on how quickly critical references change and the implications of outdated data. Verify whether the application actually supports this rule or whether an additional procedure is required.

New columns, tables, plug-ins, or profile filters may alter the offline statement. Therefore, changes are reviewed for data availability, conflicts, and error handling. Training should address a real-time sync failure: What does the status indicate, which activities can proceed, and which user must be involved?

Sources: [2] [4]

Project experience and collaboration

Locate the locally entered transaction after synchronisation

With users and the app team, we prepare a known transaction offline. After reconnection, we compare the central record and test a concurrent change and a rejected transmission. A clear conflict rule can be tested directly. Uncertain order or mapping needs additional controls. We also check what information the user receives to resolve the issue. The evidence relates to the specific app type and offline procedure in use.

Frequently asked questions about Power Apps: Offline

Can every Power App be used offline?

No. App type, data source, and offline processes are critical. The article covers standalone Dataverse-based Canvas apps with integrated offline-first capabilities. Microsoft outlines limitations, among other things, for embedded apps and non-Dataverse connectors. Review the latest documentation for your specific architecture.

Sources: [4]

Does network connectivity imply that all data are centrally up to date?

Not automatically. Offline-first operates with local data and synchronizes with the server. Verify the actual transmission and processing status. For a business decision, it must be clear whether the required records have already been centrally received or still remain local, or are erroneous and pending.

Sources: [1]

Does automated conflict resolution lead to inconsistent quality data?

Not mandatory. Technical update rules do not supersede professional consistency rules. Check for identical and differing adjacent columns as well as server-side rejections. The desired outcome is derived from the process and specifically validated.

Sources: [5]

Does the conflict detection setting from model apps apply to Canvas apps?

Microsoft explicitly states that this setting does not apply to Canvas apps. Therefore, do not transfer unverified instructions from another app architecture. Document the used procedure and verify its actual behavior.

Sources: [5]

How long may a GxP app remain offline?

There is no universal timeframe applicable to every application. Assess the relevance of required references, documentation risks, and the subsequent decision-making process. Establish a justified policy and verify that it is clearly implemented and adhered to in the application and work procedures.

Sources: [2]

Does a successful synchronisation test suffice?

A single normal case does not cover interruptions, parallel modifications, server-side rejections, or device changes. Select targeted cases based on process risks. The technical transfer must also result in the correct technical outcome and enable traceable documentation.

Sources: [2]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. Microsoft: Mobile offline support for canvas appsDataverse-based independent canvas apps; not all app types.
  2. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  4. Microsoft: Mobile offline limitations for Canvas appsSupported data sources and functional limitations; reviewed on 14.10.2026.
  5. Microsoft: Resolve sync conflicts with the serverColumn-specific update, server-side rejection, Sync Error Table; Model app setting does not apply to Canvas apps.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify the offline process after synchronization.

Provide the App, Offline profile, and a typical work process. Together, we address local data storage, conflicts, and the actual data state achieved upon reconnection.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →