Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
In blog, I have explained what Delegation is and how it improves app performance. Blog also covers delegable vs non-delegable data functions and data sources. In this blog we will focus on Image type fields which are also non-delegable, means Image type fields cannot be delegated and use of them will retrieve full dataset on application layer and process them locally.
By default, when CDS data source is mapped to Gallery control with image, images do not load. Reason behind, CDS data source is delegable and would not retrieve non-delegable data (image) by default. To solve this problem and load images, you need to use at least one non-delegable data source or function in Items property of Gallery control. Use of non-delegable type will retrieve all data including images and images will be shown in Gallery.
Let’s see how this works with an example:
Filter(‘Company Products’, _statuscode_label = “Active”)
Note that use of non-delegable types will slow down your app. In this case Collection helps you to store data temporarily which expires when app is closed.
Business Applications communities