Power Platform Build Tools error after removing custom control

(0) Share

Report

Posted on by Community Power Pla...

I have a DevOps pipeline that exports a solution and reimports it into the same environment. The solution is unmanaged.

I recently removed a custom control because it was no longer being used. I deleted it from the environment, and there were no dependencies.

My import pipeline now fails at the import solution step with the error message: The CustomControl ID does not exist for the specified name

Any suggestions on where to find the cause or fix the issue? I can't tell in the log where the error is occurring to check the files, I've searched all the files for a reference to the control name, but nothing comes up.

Categories:

Power Apps component framework

Power Platform Build Tools

All responses (1)

Answers (1)

Verified answer

cchannon 4,702 Super User 2025 Season 1 on at

Like (2)

Report
Re: Power Platform Build Tools error after removing custom control

I think this one has nothing at all to do with your pipeline. It happens some times (I'm not really sure when or why) that when you remove a PCF from a form it doesn't totally come off the form.

What happens is that when you add the PCF, it gets registered in the form XML in two places; a "Custom Control Description" at the top of the form XML and inline on the actual control you are replacing. Unfortunately, sometimes when you remove the control it only gets removed from the inline part of the XML and the "Control Description" piece stays behind. I'm not totally sure this is your issue, but I've seen it enough times to jump to this as a guess.

Unfortunately, when this happens you're a bit SOL as far as the UI goes. You can re-add the control and remove it again as many times as you want, but it never seems to fix the XML. I've only found two ways to deal with it:
delete the form and recreate it (not a workable solution if this is a managed form with downstream dependencies) or
Create a new unmanaged solution with nothing in it but this one form. Export it and crack open the Customizations XML. Find the custom control reference and cut it out with surgical precision.
Of course, as a general rule hand-editing customizations.xml is a very bad idea, but in this case, I do recommend it.