Description:
Reporter: Benedict Kabahar ([Benedict.Kabahar@alorica.com])
Summary:
When a Code App is deployed via "pac solution import" or "npx power-apps push", the cdsdependencies JSON field on the canvasapp Dataverse record is NOT updated to reflect the connection references defined in the solution. It retains stale logical names from when the app was originally created.
Impact:
Power Platform Pipeline deployments fail with:
"The dependent component connectionreference (Id=new_conRef_SharePoint) does not exist. Failure trying to associate it with CanvasApp (Id=...) as a dependency."
Steps to reproduce:
Create a Code App with connection references using one publisher prefix (e.g. new_conRef_SharePoint)
Rename the connection references to a new prefix (e.g. pac_conRef_SharePoint) in [power.config.json] and dataSourcesInfo.ts
Run "npx power-apps push"
Export the solution — customizations.xml correctly shows pac_conRef_*
Query cdsdependencies on the canvasapp Dataverse record — it still shows new_conRef_SharePoint
Workaround:
Manually PATCH the cdsdependencies field via the Dataverse Web API after each push.
Expected behavior:
"pac solution import" and "npx power-apps push" should update cdsdependencies to match the connection references in the solution being imported/pushed.
Description:
Reporter: Benedict Kabahar ([Benedict.Kabahar@alorica.com])
Summary:
When a Code App is deployed via "pac solution import" or "npx power-apps push", the cdsdependencies JSON field on the canvasapp Dataverse record is NOT updated to reflect the connection references defined in the solution. It retains stale logical names from when the app was originally created.
Impact:
Power Platform Pipeline deployments fail with:
"The dependent component connectionreference (Id=new_conRef_SharePoint) does not exist. Failure trying to associate it with CanvasApp (Id=...) as a dependency."
Steps to reproduce:
Create a Code App with connection references using one publisher prefix (e.g. new_conRef_SharePoint)
Rename the connection references to a new prefix (e.g. pac_conRef_SharePoint) in [power.config.json] and dataSourcesInfo.ts
Run "npx power-apps push"
Export the solution — customizations.xml correctly shows pac_conRef_*
Query cdsdependencies on the canvasapp Dataverse record — it still shows new_conRef_SharePoint
Workaround:
Manually PATCH the cdsdependencies field via the Dataverse Web API after each push.
Expected behavior:
"pac solution import" and "npx power-apps push" should update cdsdependencies to match the connection references in the solution being imported/pushed.