**TECHNICAL HANDOVER**

# ContosoFieldService

_Power Platform Solution Handover_

**RELEASE READINESS — HIGH RISK**

- **Solution:** ContosoFieldService
- **Version:** 1.4.2.0
- **Managed:** unmanaged
- **Publisher prefix:** con
- **Engine:** 0.5.0

> Confidential — internal use only

## Document control

| Field | Value |
| --- | --- |
| Document | Technical Handover — ContosoFieldService |
| Solution | ContosoFieldService |
| Version | 1.4.2.0 |
| Managed state | unmanaged |
| Publisher prefix | con |
| Prepared by | Solvana — automated solution analysis |
| Analysis engine | 0.5.0 |
| Classification | Confidential — internal use only |
| Status | For handover review |
| Companion documents | Analysis Report (report.docx / .md) — the risk assessment, with the evidence behind every finding. Build Book (buildbook.html) — the build walkthrough: each formula at its full recovered length (a rare formula past the storage cap is clipped there too, and labelled), every flow step, and every control a finding in this document points at. Both are produced by the same scan as this document and downloaded beside it in the Solvana app. |

## Scope & method

This handover is generated by static analysis of the exported solution package — its component metadata and, where available, the formulas and definitions inside it. No live environment, telemetry, or runtime behaviour was inspected.

**In scope**

- Dataverse tables (1)
- cloud flows (2)
- canvas apps (1)
- model-driven apps (1)
- connection references (1)
- environment variables (2)

Coverage: every component family present in the export was read in full.

> **Method & acceptance**
>
> Method: deterministic parsing of solution.xml / customizations.xml, flow definitions, and canvas .msapp sources; the same input always yields the same document.
>
> Acceptance: verify the component inventory below against the source environment, confirm the connection references and environment variables are rebound per target environment, and work the Import checklist before go-live.

## Executive summary

This solution ships 2 cloud flows (none active), 1 canvas app, 1 Dataverse table, 1 model-driven app. Overall readiness is assessed as “High risk” — set by EV-01 Environment variable has no value — 1 high, 1 medium and 1 low risk findings on components that run today. Resolve that and this reads “Needs work”. The build walkthrough follows; the full risk assessment is the companion Analysis Report.

## At a glance

- **0 / 2** Cloud flows active
- **1** Canvas app
- **1** Model-driven app
- **1** Table
- **2** Env variables
- **1** Connection ref

## Import checklist

The ordered first steps to take this solution over in a new environment. These are deployment steps, not defects — every deployment prerequisite the scan raised is stated here and nowhere else.

**1. Set 1 blank environment variable**

These ship without a value; set each for the target before the solution runs — flows and apps that read an unset variable will fail until it has a value.

con_ApiBaseUrl (String)

**2. Bind 1 connection reference**

Point each connection reference at a connection (with credentials) in the target environment — an unbound reference leaves its flows and apps non-functional. Bind all 1: "no consumer found" below means no FLOW or CANVAS APP in this package uses it — Copilot-agent and model-driven usage is not resolved from an export, so it is not evidence the reference is spare.

| Connection reference | Logical name | Used by |
| --- | --- | --- |
| SharePoint (Field docs) | con_sharepoint_ref | no consumer found in this package |

**3. Review 1 high-severity finding**

Address or consciously accept the strongest risks before go-live; each is listed below with the components it sits on, and the companion Analysis Report carries the full evidence and a fix for each.

EV-01 — Environment variable has no value · con_ApiBaseUrl

**4. Re-own and enable 1 cloud flow**

After import a flow is owned by the importing user and is often turned off; verify each flow's owner and connections, then enable it.

Sync Work Orders

**5. Switch off or remove 1 non-production flow shipped ACTIVATED**

These are named as test / retired / copies, and they ship switched ON — so they start running in the target environment at import, against whatever they are wired to. Decide per flow whether it belongs in this solution at all, and switch off the ones that do not.

Cleanup (TEST)

## How it works

The solution end-to-end, one story at a time: each card is a trigger → what runs → its steps in order → its decisions. The complete step lists are in the Cloud flows table below and, in depth, in the Build Book.

*How it works — 4 stories, each a trigger → what runs → its steps → decisions.*

- #1 Sync Work Orders (cloud flow) · triggered by On a schedule — Scheduled · touches: reads con_workorder · reads con_project · calls SharePoint · calls Dataverse
- #2 Field Hub (model-driven app) · triggered by A user — uses the app
- #3 con_dispatchboard (canvas app) · triggered by A user — opens the app · touches: reads Work Orders · reads Field docs
- #4 Cleanup (TEST) (cloud flow · non-production) · triggered by On request — HTTP request is received · touches: reads con_workorder

## Inventory

### Missing dependencies (1)

> **The target environment must already contain these before this solution imports. All 1 are Microsoft first-party components — the export names the solution that ships each one (see “Shipped by”), so they arrive with the platform rather than with this package. Nothing here needs chasing before import.**
>
> By type: Entity (1)

The full list is in the Solvana app and the Build Book.

### Data model

*Custom tables and their directly-connected standard tables (1 of 1).*

The tables and relationships below are every table this solution PACKAGES — not every table it touches. One table is used by a flow or app here but not shipped by it, so it is absent from this section and from the diagram above: con_project. Confirm it exists in the target before import. 

A table marked “shell” is one the manifest includes without its subcomponents (the same tables DV-03 raises). “—” in Audit or Columns means this export carries no column data for that table — unknown, not zero or off.

### Tables

| Schema | Display | Kind | Audit | Columns | Custom columns |
| --- | --- | --- | --- | --- | --- |
| con_workorder | Work Order | custom | on | 12 | con_priority (choice), con_scheduledon (datetime) |

### Relationships

- 1:N con_account_workorder — account → con_workorder

### Option sets

- con_workorderstatus (4 options)

### Model-driven apps

- Field Hub (con_fieldhub)

### Custom connectors

- Contoso Dispatch API

### Root components

- Entity ×3
- Workflow ×2

## Environment variables

| Schema name | Type | Points at | Used by | At import |
| --- | --- | --- | --- | --- |
| con_ApiBaseUrl | String | nothing yet | — | No value — must be set for the target |
| con_DispatchKey | Secret | — | — | Has a default |

## Connection references

| Logical name | Display name | Connector | Used by |
| --- | --- | --- | --- |
| con_sharepoint_ref | SharePoint (Field docs) | SharePoint (shared_sharepointonline) | no consumer found |

1 of these references has no consumer among the flows and canvas apps in this package. Copilot-agent and model-driven usage is not resolved here, so confirm before assuming it is unused.

## Cloud flows

The cloud flows at a glance — each flow's step-by-step logic is in the “How it works” storyboard above and, in depth, in the Build Book. In the Data column, “(writes)” marks a source the flow creates or updates rows in; untagged means read-only in this package.

| Flow | State | Trigger | Actions | Connectors & endpoints | Data (tables / lists) |
| --- | --- | --- | --- | --- | --- |
| Sync Work Orders | — | Scheduled | 8 | SharePoint, Dataverse | Work Order (con_workorder), con_project |
| Cleanup (TEST) (non-production) | — | When an HTTP request is received | 3 | (none) | Work Order (con_workorder) |

## Canvas apps

### con_dispatchboard

1 screen · 63 controls · OnStart: 6 Set/Collect, no Concurrent()

#### Data sources

| Data source | Kind | Observation |
| --- | --- | --- |
| Work Orders | Connected | — |
| Field docs | Connected | — |

#### Screen inventory

| Screen | Controls | Predominant control types |
| --- | --- | --- |
| BoardScreen | 63 | Gallery ×3, Label ×28, Button ×12 |

## Risk summary

> **Readiness: High risk**
>
> 1 high · 1 medium · 1 low findings on components that run today. The band is set by EV-01 Environment variable has no value. Resolve that and this reads “Needs work”.
>
> This handover documents how the solution is built; the full risk assessment lives in the companion Analysis Report, and the AI review (per-finding notes) in the Solvana app.

## Remediation evidence

1 findings resolved since the previous scan · 1 introduced · 0 persisting.

**Resolved**

- Notify Dispatcher — Hard-coded recipient address

## Glossary

| Term | Meaning |
| --- | --- |
| Dataverse | Microsoft’s cloud data platform — the tables, columns and relationships behind model-driven apps and flows. |
| Canvas app | A Power Apps app designed on a blank canvas, wired to data sources through Power Fx formulas. |
| Model-driven app | A Power Apps app generated from the Dataverse data model (forms, views, sitemap). |
| Cloud flow | A Power Automate automation: a trigger followed by a sequence of actions, running in the cloud. |
| Connection reference | A solution-aware pointer to a connector connection, rebound to a real connection per environment. |
| Environment variable | A solution parameter whose value is set per environment (e.g. a URL, key, or toggle). |
| Solution | The deployable unit that packages these components; exported as managed (locked) or unmanaged (editable). |
| List name (list xxxxxxxx) | Two SharePoint lists can share a display name, so where one is ambiguous the first eight characters of its id are appended. It is a disambiguator, not part of the list’s name. |
| Build Book | The companion walkthrough of how the solution is BUILT. Where this document clips a formula to keep the section readable, the Build Book carries it at its full recovered length — a rare formula past the storage cap is clipped there too, and labelled. It lists every control a finding here points at. It still ranks what it shows: a screen with dozens of behavioural controls says how many it did not list. |
| Analysis Report | The companion risk assessment: every finding with its evidence, severity and remediation. This document describes the build; that one grades it. |
| Readiness | This document’s one-word verdict on the export. Four bands, best to worst: Ready, Needs work, High risk, Exposed. Exposed is set by a packaged credential alone — the secret is already in every copy of the zip — whatever else is or is not wrong; the Risk summary says what is underneath it. |
| Delegation | Whether a Power Fx query runs inside the data source (scalable) or downloads a capped set of rows to the app. |

## Warnings appendix

- FLOW_JSON_MISSING — Referenced flow definition is not present in the export. (Workflows/legacy-sync-9f2c.json)


---

Generated by Solvana · 0.5.0
