Share
Report
4Correcting my earlier post which turned out to be user error on my part. Notes for the next person:
Not sure if this is new since the Access app scope feature was introduced, but you can use collections and globals within a component...they are just now locally scoped (unless you enable the new feature and want to reach into your app). You still see warnings because the checker doesn't know you aren't trying to work with an app-scoped collection. Tabular data can be sent in as input params and then dealt with within the component. If you want to manipulate it, I would assume you can output a modified table (have not tried that).
Where I was missing a step is I had logic to create/populate some things using OnReset and you have to manually Reset(<component name>) to fire that during development (vs. having an ability to run the On Start code for an app). That would be a nice tweak since that dev-time need to see how your component initializes is still valuable.
From the latest docs the supersedes a bunch of prior threads saying collections and components don't mix:
-------excerpt--------
When Access app scope is turned on, the following are accessible from within a component:
- Global variables
- Collections
- Controls and components on screens, such as a TextInput control
- Tabular data sources, such as Dataverse tables
When this setting is turned Off, none of the above are available to the component. Set and Collect functions are still available but the resulting variables and collections are scoped to the component instance and not shared with the app.
All responses (
Answers (
