{"id":16016,"date":"2021-08-18T09:51:46","date_gmt":"2021-08-18T16:51:46","guid":{"rendered":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-apps\/canvas-components-can-now-access-app-scope-directly\/"},"modified":"2025-06-11T07:52:56","modified_gmt":"2025-06-11T14:52:56","slug":"canvas-components-can-now-access-app-scope-directly","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-apps\/canvas-components-can-now-access-app-scope-directly\/","title":{"rendered":"Canvas components can now access app scope directly"},"content":{"rendered":"

Canvas components<\/a> have become an important part of canvas app reuse and scalability.\u00a0 They enable the sharing of app logic and UI across screens and apps.\u00a0 They even enable a form of app co-authoring by partitioning an app into pieces that multiple makers can work on at the same time.\u00a0 You can find some amazing downloadable canvas components at\u00a0canvas components sample gallery<\/a>.<\/p>\n

And we aren’t done with them yet.\u00a0 In today’s installment, we are enabling a canvas component to directly access variables, collections, controls, and tabular data sources from its host app.\u00a0 No longer do you need to pass everything in and out through component properties.<\/p>\n

Until now, canvas components have been properly encapsulated and could not access information and resources from the app.\u00a0 Everything needed to be passed in to the component through input properties.\u00a0 We did this to make it easier to share components across apps by using a component library.\u00a0 Strict encapsulation ensures maximum sharing.<\/p>\n

But sometimes you want to define a component just for this app.\u00a0 You want to reuse a UI widget or create a user defined function as an output property.\u00a0 No need to worry about sharing.\u00a0 And to make it easier to write and maintain, let it share in the app’s scope.<\/p>\n

We have introduced a new component setting that does exactly this Access app scope<\/strong>:<\/p>\n

\"\"
\nNote:<\/strong>\u00a0This setting works properly for new apps but not existing ones.\u00a0 Existing apps will be supported with a bug fix in Studio version 3.21083.\u00a0 As a workaround, you can turn off the “Collection access in component scope”\u00a0 “Retired” feature under “Upcoming features” in the app’s Settings, save the app, and then reopen.<\/p>\n

With this setting turned On<\/strong>, your component can now access:<\/p>\n