Limitations

With the release of Power Apps component framework, you can now create your own code components to improve the user experience in Model-driven and canvas apps. 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:

  1. Microsoft Dataverse dependent APIs, including WebAPI, are not available for canvas applications yet. For individual API availability, see Power Apps component framework API reference.

  2. 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 not yet supported. We are reviewing this and will be adding this capability in future release.

  3. Code components should not use the HTML web storage objects, like window.localStorage and window.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.

Power Apps component framework API reference
Power Apps component framework overview