Unanswered

Failing to Import Code Components into the Environment

(1) Share

Report

Posted on by ialexandridis

I have been working with code components for the last two months without any issues. Without changing my actions to create, build, and push a component, all of a sudden, I am not able to update or import new components as I used to be able to.

Steps followed to import or update a component:

Connect to environment
Build my component (update manifest control version if is an update)
Import with

pac pcf push --publisher-prefix prefixhere

By following these steps, a solution named "PowerAppTools_prefixhere" was created once, including my code components.

Now no matter what I do, following the same steps, when I use the import command I noticed while Packing the zip file it has the name of "PowerAppToolsTemp_prefixhere" and I think that causes the behavior to not be able to see my new components I try to update or import inside the environment that has the "PowerAppTools_prefixhere" solution created in the past when I had no errors.

Are the steps that I follow wrong for importing/updating the solution?

Fun fact even if I don't see the code component in the component solution I'm still able to use it in any app in the environment.

When importing it finishes with message:
"blah...
blah..

...

Importing the temporary solution wrapper into the current org.

Solution Importing...

Solution Imported successfully.
Importing the temporary solution wrapper into the current org: done."

And after the success message I get an error:
Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: ...........
The diagnostic logs can be found at: c:\Users.....

All the guides I used are these:

Concluding, I am not able to update any existing component, and if I try to import a new one is not appearing in the "PowerAppTools_prefixhere" solution (but I can use it in apps)

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Pro_User_365 546 on at

Like (0)

Report
Copy link

Link copied!
Hi @ialexandridis ,
It seems like there might be an issue with the solution packaging process, specifically related to the solution name change to "PowerAppToolsTemp_prefixhere". Here are a few things to check and try:
Verify Solution Names: Make sure the solution name used during the pac pcf push command matches the solution name in your environment.
Check for Errors in Build: Ensure there are no errors in the component build process before importing.
Solution Update vs. New Solution: If updating an existing component, ensure the manifest version is correctly incremented. For new components, verify that they are being added to the correct solution.
Consult Logs: The error message you receive suggests a deeper issue. Check the diagnostic logs for more specific error details.
Review Documentation: Double-check the steps outlined in the Microsoft documentation you referenced to ensure no step is missed or changed recently.
If these steps don't resolve the issue, consider reaching out to Microsoft Support or the PowerApps community for more specific guidance, as they might have insights into recent changes or issues with the PowerApps environment.
Hope this helps you troubleshoot the issue!
Note: After receiving the answer, if you find it helpful, please consider accepting it. 😊 Regards, Ali Shahzad

Was this reply helpful? Yes No
ialexandridis 6 on at

Like (1)

Report
Copy link

Link copied!
Appreciate your response @Pro_User_365,
About
How I can verify the solution names? In the "pac pcf push --publisher-prefix prefixhere" command the only thing that I set is the prefix name. Is there a way to control the name of the solution that is automatically generated?
Build runs without any issue!
Manifest version is correctly incremented
Log files sometimes is tons of lines 1000+
The only difference from the documentation is the build process, instead of "msbuild /t:build" I use the shortcut in vscode Ctrl-Shift-B to run this command in screenshot

And I said that's something I've been doing for months without any issue! Until now

Was this reply helpful? Yes No
Pro_User_365 546 on at

Like (0)

Report
Copy link

Link copied!
To verify and control the solution name when pushing your PCF component with the pac pcf push command, you should check the Power Apps CLI documentation and the arguments available for the pac pcf push command. The automatically generated solution name usually follows a default pattern, but you may not have direct control over it without specifying certain arguments.
However, here are steps you could take to troubleshoot and resolve your issue:
Verify Solution Names: You can view the existing solutions in your environment using the Power Apps CLI with the command pac solution list. This will show you all the solutions and their details.
Solution Name in pac pcf push: Typically, the solution name is generated based on your publisher prefix and the name provided in the manifest. Make sure these are consistent with what you expect.
Review Logs: While logs can be extensive, they're crucial for diagnosing issues. Use text editor features like search to find errors or warnings that can give you clues.
Build Process: The difference in the build process may be significant. The shortcut in VSCode (Ctrl+Shift+B) might not execute the build in the same way as msbuild /t:build. Try using the full msbuild /t:build command to see if this resolves the issue.
Revert to Known Good Configuration: If a certain process has worked in the past, try to revert to that exact setup—whether that's specific versions of tools, commands used, or environment settings.
Contact Support: If the problem persists, consider reaching out to Microsoft Power Apps support or the community forums with specific details of your issue, including the error messages and log excerpts.
Remember to keep each version of your components and solutions well-documented, and consider implementing version control if you haven't already. This can help track changes and revert to previous states if something goes wrong.
Note: If you find this solution helpful, please consider accepting it. 😊

Was this reply helpful? Yes No