Microsoft Power Apps, through the Power Platform, provides tools for customizers to make the most granular adjustments to a system. Furthermore, a canvas app can be used to augment a particular model-driven app or even a portal. Within a canvas app, data is displayed primarily through fields on galleries and forms. This is important because galleries and forms, while two very different components of a canvas, can be used with one another in different areas of the canvas.
Galleries are commonly used to navigate to a form. Once you navigate to a form from a gallery, the data you see is coming from the Item property on that form. Usually, this property is set to something similar to GalleryX.Selected, as the form needs to know where and how to pull the data. But what if your form is referenced in another area of your canvas, perhaps from GalleryZ? In this case, assuming the Items property was not adjusted, if you accessed the form from GalleryZ, no data would populate because the form is expecting to see data from GalleryX.Selected. So we need a way to dynamically adjust the Items property on the form to account for this.
Power Apps solutions
One way to accomplish this would be to write Power Fx (ƒ×) code in the Navigate property on the gallery and Item property on the form. This method creates less bulk in the app overall, but if the form is ever adjusted to view data from a different source or moved within the app, properties on both the gallery and the form itself are most likely going to need to be updated manually.
[]
