Fix PAC PCF Push Errors in CLI 1.28.3+ Easily
Resolve pac pcf push errors in PAC CLI post 1.28.3: Quick fixes & workarounds revealed!
Key insights
Diana Birkelbach [MVP] has shared insights and workarounds for a persistent issue with the "pac pcf push" command in "pac cli" version 1.29.6 and onward, causing difficulties for PCF developers when uploading debug versions of the PowerApps component framework due to a publisher error.
- When the PCF with the same publisher has already been uploaded, users may encounter deletion issues related to a cascade restrict relation between the Publisher and Solution.
- If it is the first time uploading a PCF with a publisher in the environment, the PCF may land in the default solution and become invisible due to the temporary solution being deleted post-import.
- To workaround, users might need to downgrade the PAC CLI using the "pac use" command or via the VSCode extension in order to utilize the "pac pcf push" command.
- If previous uploads have been made with the same publisher prefix, a potential fix includes moving all PCFs to a new solution with the same publisher and prefix, then deleting the "PowerAppsTools_" to allow "pac pcf push" to function correctly.
- The community is awaiting a solution to these issues, and in the meantime, this workaround might help those facing similar difficulties with PCF deployment.
Additional Perspective on PCF Deployment Issues
Developing and deploying custom components within Microsoft's PowerApps ecosystem using the PowerApps Component Framework (PCF) can be technical and sometimes challenging. The process typically involves utilizing the PowerApps CLI tool for tasks such as pushing updates to the PCF. However, developers have encountered significant challenges with specific versions of 'pac cli', particularly those after 1.28.3, where the deployment process encounters publisher errors leading to deployment failures.
The core of the issues seems to stem from the way newer versions handle the clean-up process of temporary solutions and publisher associations. The workaround solutions, as highlighted by Diana Birkelbach [MVP], involve either downgrading to a stable version of the CLI or restructuring the way solutions and PCF components are managed within the development environment. The community is hopeful for an official fix, reflecting the importance of robust and reliable tooling for streamlined component deployment in professional PowerApps development workflows.
Are you facing issues with the 'pac pcf push' command and the Power Apps CLI (PAC)? A common problem since PAC version 1.29.6 is an error message when trying to push PowerApps components. A workaround is available until a fix is issued by MVP Diana Birkelbach.
THE ISSUE:
- From PAC CLI version 1.29.6 onwards, uploading PowerApps components using 'pac pcf push -pp ' ceased functioning.
- Using the ‘--solution-unique-name’ parameter did not resolve the problem either.
THE SYMPTOMS:
If a component with your publisher prefix was already in the environment, a failure occurs when using the push command. The error indicates an issue with deletions involving the ‘Publisher’ entity in Dataverse.
An open GitHub issue addresses it, but it’s unresolved. Alternatively, if no components had been uploaded using your publisher, the 'pac pcf push' might work, but the component does not appear as expected in your environment or the list of components to be added to a solution, possibly indicating latency in the environment.
THE SOLUTIONS:
- One option is to downgrade the PAC CLI to a previous version that works ('pac use 1.28.3').
- If using Visual Studio Code's Power Platfo
Read the full article How to fix “pac pcf push” issues with pac cli newer than 1.28.3 – publisher error or solution delete
Keywords
pac pcf push fix, pac cli 1.28.3 errors, resolve pac pcf publish issues, troubleshoot pac pcf command, pac cli update problems, PowerApps CLI fix, PowerApps component framework push error, resolve publisher error pac cli, delete solution pac cli issue, pac command line interface errors