Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Power Apps Cookbook

You're reading from   Microsoft Power Apps Cookbook Become a pro Power Apps maker by applying practical use cases to solve ever-evolving business challenges

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781800569553
Length 376 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Eickhel Mendoza Eickhel Mendoza
Author Profile Icon Eickhel Mendoza
Eickhel Mendoza
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Chapter 1: Building pixel-perfect solutions with Canvas Power Apps 2. Chapter 2: Building from data with model-driven apps FREE CHAPTER 3. Chapter 3: Choosing the right data source for your applications 4. Chapter 4: Automating processes with Power Automate 5. Chapter 5: Extending the Platform 6. Chapter 6: Improving User Experience 7. Chapter 7: Power Apps Everywhere 8. Chapter 8: Empowering your applications with no code Artificial Intelligence 9. Chapter 9: Discovering the Power Platform admin center 10. Chapter 10: Tips, Tricks, and Troubleshooting 11. Chapter 11: Advanced Techniques with Power Apps Component Framework 12. Other Books You May Enjoy

Handling image resources in components

In Chapter 5, Extending the Platform, we learned about the Power Apps components feature – small building blocks that encapsulate a set of controls to be reused across an application.

These components isolate themselves from the applications so they can get used anywhere, no matter their purpose. This behavior means that a component can't access variables or resources from an application unless passed through custom properties.

It also means that resources included in components won't be available from the applications loading those components.

Let's use the following example: You create a component to display an About dialog for all your solutions. This dialog includes the logo of your company. When you build it, everything works correctly, but the logo doesn't show when you use it, as a component, in your solutions.

This happens because the component only packs its definition and doesn't include resources...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime