Skip to main content

Notifications

Power Apps - Power Apps Pro Dev & ISV
Answered

Change a Publisher of PCF solution

(0) ShareShare
ReportReport
Posted on by

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.

 

  • Forrest Zhang Profile Picture
    Forrest Zhang 12 on at
    Re: Change a Publisher of PCF solution

    Yes, you can customize the prefix each time you deploy the PCF. 

    See below article for details.

    https://www.hellosmart.ca/2024/07/how-to-resolve-publisher-prefix.html

  • Wukong Profile Picture
    Wukong on at
    Re: Change a Publisher of PCF solution

    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...

  • Verified answer
    cchannon Profile Picture
    cchannon 4,702 on at
    Re: Change a Publisher of PCF solution

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,422

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,711

Leaderboard