Canvas app code component error "Couldn't import components"
If you are developing code components (PCF) for canvas apps you'll be used to using the 'Get more components' panel. When adding the code-component to the canvas app, occasionally you will receive the somewhat unhelpful error:
Couldn't import components
There are no more details provided in the expanded down arrow area:
I'm putting this here for my future self (who always seems to forget about this issue) and anyone else who comes across this error.
The cause is usually because you have a property-set that has the same name as an in-build property or one of your own (e.g. Enabled/Selected)
The resolution is simply to prefix your property-set names with the name of the data-set:
<data-set name="Items" ... > <property-set name="ItemsSelected" .. /> <property-set name="ItemsEnabled" .. /> </data-set>
Hope this helps!
Published on:
Learn moreRelated posts
🔓 Understanding the “Access app scope” Feature in Canvas App Components (Power Apps)
đź’ˇ Introduction In Power Apps Canvas Apps, components play a crucial role in building reusable UI and logic blocks. However, traditionally, co...
Canvas App | Easy way to use SVG icons with PowerIcons
In my previous articles, I explained how to use SVG icons in Canvas Apps by manually modifying the SVG content to make it compatible with Canv...
How to Detect that a PCF is Running Inside a Canvas App / Custom Page
Usually my target is to develop a PCF working inside all types of apps: Canvas App (or Custom Pages), Model-Driven Apps and hopefully also ins...
Power Up Your Canvas Apps with No Code Interactive Maps: A Game-Changer for Sales and Field Teams!
If you’re a Sales Manager juggling territories, appointments, and customer data across multiple tools, it’s time to simplify things—with maps ...
Debug PCFs using a Browser Autoresponder Extension (MDA & Canvas Apps)
I’m sure the Autoresponder idea for Debugging PCFs (or WebResources) is not new to you. Debugging with an autoresponder solution is a li...