I followed the steps outlined here. However, my component is not showing up in the custom control list.
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/import-custom-controls
This is my project. It runs fine in the control harness.
https://github.com/rexkenley/d365MultipleLinesHTML
Thanks.
Solved! Go to Solution.
After a few more tests and naming variations, I can't reproduce the issue anymore. The best I could tell was that there was a residual unmanaged version of the control that I accidentally deployed (and could have sworn deleted) that is contributing to the issue.
So the take away is to make sure you clear out all unwanted code artifacts.
But as a side benefit I did find out I can customize the deploy package name to be the same as the main project name (even though the pac command forbids it). Just go to deploy\Other\Solution.xml and modify the <UniqueName> node and
Have you imported the Solution.zip file to your environment? If you have multiple CDS environments, are you certain you are in the correct environment?
We have only 1 environment.
I decided to start from scratch but was unsuccessful. Here are the steps I took
I have attached the screen shots.
Hi @rexkenley ,
Have you taken a try to deploy your code Component to your CDS directly using pac command?
Do you mean that you could add not custom control to a Entity?
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. On your side, you could also consider take a try to deploy your code Component to your CDS directly using pac command as below:
pac auth create --url <https://xyz.crm.dynamics.com>
Note: The <https://xyz.crm.dynamics.com> represents the D365 instance URL related to your PowerApps Environment.
After that, push your code component to your CDS using the following pcf command:
pac pcf push --publisher-prefix <your publisher prefix>
Based on the screenshot that you mentioned, I found that you have imported your code component as custom control in your PowerApps Environment successfully. If you do not see the code component under the "Add Control" panel, please check if the Code Component has been displayed in a different name.
Please note that the displayname of the Custom Code Component is defined within the Manifest.Input.xml file for your code component as below:
The user @MinhPham96 has faced similar issue with you, please check my response within the following thread:
Please consider add your custom control within a specific Entity form mentioned as above, then check if the issue is solved.
Best regards,
The name is correct
I read the @MinhPham96 thread and this could be the cause of the problem.
"Also please make sure the Entity you are expanding is in same Solution as your imported Custom Conponent package."
My managed solution only has the control, it doesn't have the Entity. I have attached my code in a zip file, can you please see if it works for you?
You need to run
You will then get the managed solution file. Thanks for taking a look at this.
Now this is VERY strange. I repeated the same process except this time I use Test for the name and "deploy" for the deployment solution name and it works.
I have attached a screenshot.
Is there a limit to the length of the name?
After a few more tests and naming variations, I can't reproduce the issue anymore. The best I could tell was that there was a residual unmanaged version of the control that I accidentally deployed (and could have sworn deleted) that is contributing to the issue.
So the take away is to make sure you clear out all unwanted code artifacts.
But as a side benefit I did find out I can customize the deploy package name to be the same as the main project name (even though the pac command forbids it). Just go to deploy\Other\Solution.xml and modify the <UniqueName> node and
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
190 | |
53 | |
51 | |
36 | |
33 |
User | Count |
---|---|
268 | |
95 | |
80 | |
68 | |
67 |