Limitations
With Power Apps component framework, you can create your own code components to improve the user experience in Power Apps and Power Pages. Even though you can create your own components, there are some limitations that restrict developers implementing some features in the code components. Below are some of the limitations:
Microsoft Dataverse dependent APIs, including WebAPI, are not available for Power Apps canvas applications yet. For individual API availability, see Power Apps component framework API reference.
Code components should bundle all the code including external library content into the primary code bundle. To see an example of how the Power Apps command line interface can help with bundling your external library content into a component-specific bundle, see Angular flip component example.
Note
Support for shared libraries across components using library nodes in the component manifest is currently in public preview. More information: React controls & platform libraries (Preview).
Code components should not use the HTML web storage objects, like
window.localStorageandwindow.sessionStorage, to store data. Data stored locally on the user's browser or mobile client is not secure and not guaranteed to be available reliably.
Related topics
Power Apps component framework API reference
Power Apps component framework overview
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for