Book Image

Learn Microsoft Power Apps - Second Edition

By : Matthew Weston, Elisa Bárcena Martín
4 (2)
Book Image

Learn Microsoft Power Apps - Second Edition

4 (2)
By: Matthew Weston, Elisa Bárcena Martín

Overview of this book

Microsoft Power Apps provides a modern approach to building low-code business applications for mobiles, tablets, browsers, and Microsoft Teams. The second edition of Learn Microsoft Power Apps will guide you in creating well designed and secure apps that transform old processes and workflows. Learn Microsoft Power Apps starts with an introduction to Power Apps to help you feel comfortable with the creation experience. Using screenshots from the latest UI, you will be guided through how to create an app, building your confidence to start developing further. This book will help you design, set up, and configure your first application by writing simple formulas. You'll learn about the different types of apps you can build in Power Apps and which one applies best to your requirements. In addition to this, you’ll learn how to identify the right data storage system for you, with new chapters covering how to integrate apps with SharePoint or Dataverse. As you advance, you’ll be able to use various controls, connectors, and data sources to create a powerful, interactive app. For example, this book will help you understand how Power Apps can use Microsoft Power Automate, Power BI, and Azure functionalities to improve your applications. Finally, you will be introduced to the emerging Power Apps Copilot tool, which uses artificial intelligence to accelerate the app building process. By the end of this Power Apps book, you’ll be ready to confidently develop lightweight business applications with minimal code.
Table of Contents (27 chapters)
24
Other Books You May Enjoy
25
Index
Appendix

Using the component library

Component libraries are now the recommended way of reusing components across multiple apps. They are centralized, which means that the dependencies created when using the components are all pointing back to a repository that is likely to have a much longer life expectancy than an app. Apps generally go through a life cycle where eventually they will be retired and removed, so if Microsoft had chosen to work on an app-to-app basis, then that would have introduced a huge amount of risk.

To mitigate this risk, and to give a truly centralized approach to the creation and sharing of components, the component library was developed. At the time of writing, this feature is still in public preview; however, it works quite effectively.

The biggest advantages that you get from using the component library is that you can make it extremely easy for others who are creating apps in the same environment to discover and use those common components, publish updates, and send...