Apps was not deployed completely?

(0) Share

Report

Posted on by PANovice2025

Hi,

For background, I inherited a solution with model driven app and I am not very clear on the history of the solution.

The app has a custom button on command bar to update a column (Column A) in dataverse.

in DEV:
- Dataverse column name: Column A
- Formula in the button: Update Column A
- Main form shows Column A correctly

- App Last Modified 4 days ago

in PROD (deployed using pipeline):
- Dataverse column name: Column A
- Formula in the button: Update Column B (no column B in dataverse table, but no error)
- Main form shows Column A correctly

- App Last Modified 1 year ago (after deployment)

Issue:
- PROD: Button runs but no column was updated (because column B doesnt exist?)
- DEV: Button runs and column A was updated successfully
- PROD: Update button formula from Column B (no intellisense error) to Column A (intellisense error, ie. column not found)
- PROD: App shows "Last modified" as 1 year ago, should be recently
- It is possible someone make changes in PROD in the past without going through pipeline but cannot be confirmed

Troubleshooting done so far (not in order):
- PROD: Update button formula from Column B (no intellisense error) to Column A (intellisense error, ie. column not found)
- PROD: Remove unmanaged app layer
- PROD: Publish all customisations after deployment

- PROD: Add dummy button to update Column A but also error (intellisense error, ie. column not found)

- PROD: Add dummy button to refresh the table (ie. Refresh(table_name)), runs with no error
- DEV: Publish all customisations before deployment
- DEV: Save and publish button formula before deployment

Appreciate any help. Thank you.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Erdi Kudu 9 on at

Like
a
(1)

Report
Copy link

Link copied!
Potential reasons, from most likely to less likely:

Removing the unmanaged app layer may not remove the unmanaged ribbon/command layer. This is the strongest reason why PROD still runs old logic. Use Command Checker and check the active layer. Microsoft specifically says unmanaged ribbon layers can define runtime behavior. https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/create-and-use-apps/remove-an-unmanaged-layer-for-ribbon

Form can show “Column A” correctly, but Power Fx command may require the actual Dataverse logical column name. Compare DEV vs PROD column logical name, schema name, publisher prefix, and solution layer.

Command designer metadata/cache is stale in PROD. Column B not erroring while Column A errors suggests the command designer may be referencing stale metadata. Modern commanding has known limitations around Power Fx command components https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/command-designer-limitations

PROD may already have the field for the form, but the command component’s solution may not include the table/column dependency correctly. Check solution import history for dependency warnings.

If someone edited PROD directly, the active unmanaged layer can remain above the managed layer. Pipeline deployment may succeed but not affect runtime behavior.

Was this reply helpful? Yes No
PANovice2025 9 on at

Like
a
(0)

Report
Copy link

Link copied!

@Erdi Kudu Thank you for the response. It definitely brings me to this solution:

Was this reply helpful? Yes No