cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Wukong
Frequent Visitor

Change a Publisher of PCF solution

Hello everyone,

In my company, we have 3 different environments (Dev, preprod, prod) and 1 for organization "psl-dev". I was importing a solution which contains PCF solution from Dev to Preprod and got an Error that the "Publisher prefix new for this control psl.confirmdialogcontrol does not match the prefix "crd7e" for the solution with Id xxx".

The Publisher of the main solution is indeed DefautDevPublisher with crd7e prefix And I chose the Org one with "new" prefix when initializing my PCF. Which is weird is that, in my generated repo, there are 3 publishers.

Wukong_0-1632993723222.png

So I wonder if I can "switch" those publisher to the crd7e one. Do you think it's possible ?

I look at the CLI doc : https://docs.microsoft.com/en-us/powerapps/developer/data-platform/powerapps-cli  and the cmd "pac pcf version" looks like a way to achieve this. But I am not really comfortable with the CLI yet.

If anyone  has a suggestion, glad to hear it. Thank you.

 

1 ACCEPTED SOLUTION

Accepted Solutions
cchannon
Super User
Super User

The only way to change the publisher is to rebuild the control with a different --publisher-prefix value then delete the copy of the control currently installed in your environment and import the newly built copy.

 

That said, generally I think most would call it bad practice to use these default prefixes, and instead I would recommend you make a new publisher with a prefix that you can remember and always make your customizations with that prefix. It sounds like you're already a bit too deep into your customization work to change all that, but I suggest you start with a solution publisher and prefix the next time.

View solution in original post

2 REPLIES 2
cchannon
Super User
Super User

The only way to change the publisher is to rebuild the control with a different --publisher-prefix value then delete the copy of the control currently installed in your environment and import the newly built copy.

 

That said, generally I think most would call it bad practice to use these default prefixes, and instead I would recommend you make a new publisher with a prefix that you can remember and always make your customizations with that prefix. It sounds like you're already a bit too deep into your customization work to change all that, but I suggest you start with a solution publisher and prefix the next time.

View solution in original post

Wukong
Frequent Visitor

Thank you @cchannon,

I expected this. So I will do so. 

Regarding Publishers and prefixes, I may consider change the existings or create a new one as you suggest, but I must first consider the impact because There are shared entities between solutions so potential side effects...

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Users online (1,733)