Personalized Community is here!
Quickly customize your community to find the content you seek.
Microsoft Customer Co-creation
Help impact how the tools and services you rely on are developed. Microsoft Customer Co-creation connects you directly with our engineers so you can provide feedback before a single line of code is written. Interested? Learn more at Microsoft Customer Co-creation
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All 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