Today I had the opportunity to use the component import feature inside the Power App Maker. I found one critical defect and one opportunity for Microsoft to make this feature better.
Critical Defect:
Embedded Power App Flows are not components and should not be imported. Unfortunately, the process correctly imported the components from the source app but also all of its embedded flows. The app did not display an error when the importation was completed. It was only after I saved the app, closed it and reopened in the Maker, that the platform complained about corrupted flow metadata. Upon closer examination, the embedded flows from the source app had also been imported. THIS SHOULD NOT HAPPEN.
Enhancement Opportunity:
I should be able to select which components I want to import from another app. The current process brings them all in and then leaves it to me to remove what I don't want. This is an incomplete implementation as I should be able to choose which components I want to import from a popup list. This would also correct the issue with flows being considered components and imported.
272
Share
Report
All responses (
Answers (
