The way the canvas components were added to a canvas app prior to release 3.0.0 is deprecated by Microsoft. Meaning that at some point in time it will not work anymore. That’s why the canvas components are now offered via a component library.
There is not an easy path to migrate from a release prior to 3.0.0 to release 3.0.0. I know that the hard way from migrating the canvas apps PACo Examples and PACoCo. Unfortunately, there is no other way than adding and configuring the canvas components from the component library and then removing the canvas components from a release prior to 3.0.0.
When Microsoft does not change the idea behind a component library, this should be an activity you never have to do again.
I advise the following migration procedure:
- Rename the canvas components in your canvas app.
- Import the canvas components you want to use from the component library.
- Configure the canvas components from the component library using the logic you already created.
- For some canvas components, the custom properties have changes. You can check the canvas components documentation on the PACo GitHub repository for the correct configuration: https://github.com/formsandflows/PACo/tree/main/Canvas%20components
- Remove the canvas components in your canvas apps once they have been replaced by a canvas component from the component library.