Power Platform Community Forum Thread Details

Hello Power Apps Community,

I am new to PCF and things out. I've encountered a challenge with making a Power Apps Component Framework (PCF) control available in my Canvas app. Despite following the standard procedures for pushing the PCF control to my environment, the control is not appearing in the Power Apps editor as expected.

Here's a summary of the steps I've taken and the current status:

I developed a PCF control and used the pac pcf push command to push the control to my Power Apps environment.
The CLI indicated a successful push, and I verified this through the Power Apps CLI and the solution history within the Power Apps portal.
The control was wrapped in a temporary solution named PowerAppsToolsTemp_dev during the push process.
When checking the solutions list in the Power Apps portal, the PowerAppsToolsTemp_dev solution does not appear, despite the solution history indicating a successful import.
In the Power Apps editor, I do not see a "Custom" tab or my PCF control listed under the available components for import in a Canvas app.

Additional details:

The environment in question is correctly selected.
The manifest file for the PCF control has been configured with the control-type set to standard, which I understand is required for Canvas app compatibility.

I am seeking advice or solutions from the community on the following points:

Confirmation on whether there might be a propagation delay that I need to account for.
Any additional steps or checks that I might have missed or should perform to troubleshoot this issue.
If there are known issues with the pac pcf push command or the import process into unmanaged solutions.

I appreciate any insights or guidance you can provide to help resolve this issue and successfully integrate my PCF control into the Canvas app.

Thank you for your time and assistance!

Categories:

Power Apps Pro Dev & ISV

Hi @Tade_AI ,

I suspect your issue being linked to the "pac pcf push" issue I had too (https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/PCF-Push-eror/m-p/2476718#M9545). It is a confirmed issue for now, and will be fixed soon.

For us who have deployed previously using "pac pcf push" , we couldn't import the solution because of "PowerPlatformTooldTemp_dev" (it was PowerPlatformTools_dev before).
I cannot test your case (because I have the PowerPlatformTools already in all my environments), but maybe it helps to try to downgrade the pac cli (like posted in the other thread ).

I would propose to delete the component imported already (or the generated PowerPlatformToolsTemp solution) before trying again, but I understand that you don't see the solution... :-(. Hope you don't run in other issues.🤞