Bind source inputs and custom approval fields
A workflow can contain valid actions but still lack the form input or task output consumed by a later step. Resolve the actual data contract under Required Settings; do not replace missing values with blank defaults.
Bind form inputs deliberately
Choose the HTTP-body mapping only when the replacement form or caller will send that payload. Opening the settings panel does not apply a mapping. Review each source-variable-to-body-property mapping and confirm the caller integration. The generated request validates the schema and requires consumed properties; it preserves explicitly blank strings, false and zero instead of using source defaults.
This option generates a workflow input contract, not a replacement form. Implement the caller, secure the HTTP endpoint and validate trigger permissions before activation. Do not combine it with an unrelated trigger override. Uploaded files require a further explicit choice: the caller resolves them to real name/contentBytes objects with base64 bytes, preserving collections.
Custom approval fields are separate from native comments
A field such as Manager Comments is not automatically equivalent to express/native approval comments. For supported declared text fields, an explicit commercial Teams option sends a second adaptive-card interaction to each native approval responder. It retains the original decision and native comments separately and verifies the returning object and tenant IDs before publishing custom values.
This changes the interaction into an approval followed by a separate custom-field request. Confirm that behavior. The Teams connection, Workflows app and original responder identities must be available; validate timeout, notification and multi-responder behavior in the target tenant. This Flow bot option is not offered for GCC, GCC High or DoD. Other field types and system language fields remain blocked.
Correct a source reference only after confirming the source defect
Advanced source-reference corrections require the exact action ID, old variable and path, declared replacement variable and path, and matching occurrence count. The correction is tied to the analyzed source signature. It changes only those input tokens, not declarations, literal text, disabled branches or other actions. Similar variable names are not automatically reconciled.
Cascading, stale, unknown-target and incompatible-type corrections are rejected. The complete choice is recorded in migration metadata and reports; reanalyze and reconfirm after a source change.
Supported recursive JSON selectors
Literal named descendant selectors such as $..Title, $..Email and $..UserPrincipalName use a native bounded JSON scanner, not a guessed SharePoint envelope or first-row approximation. FirstMatch and AllMatches remain distinct. Null values, duplicate matching values and array order are retained by the generated operation.
Wildcard, filter, union and script selectors outside the supported grammar remain configuration requirements. Parsing or scan-limit failure stops the operation before it publishes partial results. Measure representative large payloads and Power Platform request consumption before deployment; local package generation is not runtime verification.
Read the result without weakening validation
Known source/configuration rejections return a structured non-success 400 response with their original error code rather than a generic 500. Unknown internal faults remain server errors. This reporting improvement does not make a blocked workflow exportable.
A successful local export does not establish tenant import, connection binding, licensing or business-process runtime correctness. Revalidate generated packages and complete a tenant pilot before activation.