You’re offline. This is a read only version of the page.
Hi, this would be my first post in this site.
I was planning to use components because I've heard that if you're planning to use something multiple times then you can use components instead. I have some questions though...
1) Is it possible for the component (when used) to have different data sources? So for example, on ScreenA I use component A which is connected to DataSourceA, then ScreenB using component A that is connected to DataSourceB?
2) If I use the component on different screens, then decide to update the component (be it design or whatever), would it break connection to their data source (DataSourceA for ScreenA and DataSourceB for Screen B)?
And probably an out of topic question... does running a flow through the OnSelect property of a button require something more than an Office 365 E3 or Microsoft Power Automate Free license?
I'll start experimenting then. Thanks a bunch!
I just took a simple example that utilizes different datasources.
Yes, what you mentioned is a great feature of component.
When needing to use the component in various contexts( on different screens, even on the same screen), it's better to consider various input properties for decorating header and other features you want to present such as font, color, message, sequence of actions, image —or a basic level of properties would be enough if you plan to directly modify the component, not by indirectly adjusting features by various input properties.
2)Existing data connection is not disconnected.
(* Although it occurs very rarely, if way of processing data within a component significantly changes, the existing data may become inaccessible during a session for various reasons)
I have three sharepoint lists with the same headers but contains different data (like for example, SP1 is for all Type A stuff, SP2 is for all Type B stuff, but both SP1 and SP2 have the same column headers).
They'll each be placed in different screens, but what I wanted to ultimately accomplish is that if I need to make design changes on one, it would also apply to the rest (like changing the fill color, font style, font color, etc.).
Another way to use different data source
1) OnVisible of screen A: Set(datasourceName, datasourcenameA);
*datasourcenameA is not a text but a real reference of the data source
OnVisible of screen B:
Set(datasourceName, datasourcenameB);
2)Items of gallery in Component: datasourceName. //gloabl var.
I've just tested using live connection in Component features released in 2021. I was not sure that different connection can be used on a Component depending on a situation because I have not used the feature yet.
I did not know until now whether it is possible to directly connect to the data source because I had not turned on the Access app scope before. Sorry
1)
Component supports data types for input/output properties such as Table(having data set meanings) and Record, which is used for displaying data within the Component, and can also be used to return output if needed. Unfortunately, Live data source as Input property of Component is not supported yet. So I used simple text such as "1","2" to identify a data source for demo.
Drag_and~ and AttendanceData is names of SPO list for demo. They both have same column names, 'ID', and 'Title'
------------------------------------------------------------------------------------------------------------
Definition about DataSourceName, custom property for distinguishing Datasource.
Connection object cannot be directly used as custom property yet.
Component used Datasource A as input property indicates "1"
One thing to consider is the column names of lists should be identical to each other in order to be used together in one component, thereby avoiding the need for lengthy code to manipulate the different names.
Component used Datasource A as input property indicates "1"
2) If I use the component on different screens, then decide to update the component (be it design or whatever), would it break connection to their data source (DataSourceA for ScreenA and DataSourceB for Screen B)? --> would you explain more?
Kirkby.
-----------------------------------------------------------
Below is my previous answer that I removed because it was not up to date due to not knowing the existence of the access App scope.
Screen allows to easily fetch live data (e.g., SPO List, SQL Tables) using connectors, but at present, components do not support this. The data source you added in your Component could not be recognized.
Component supports data types for input/output properties such as Table(having data set meanings) and Record, which is used for displaying data within the Component, and can also be used to return output if needed
However, Table and Record represent fixed value snapshots rather than live data (Note: Components can still fetch various kinds of live data internally; for example, using the Office365Users connector to create a UX for setting workflow sequences.)
As components are inherently tied to one screen, if an app has five screens and you want to use the component on each, you need to add the component separately to all five screens. You can initialize all five components with the same property or initialize them with the necessary data for each screen.
Components can be updated with a different dataset at any time within each screen. They can either comply with internally defined Input Property formats for updates or indirectly utilize global variables shared across all screens in the app.
Assuming that component A internally updates some internal data while operating, and this updated data is commonly referenced by other components (A', A''), the data inside A', A'' will also be updated when A updates. However, this scenario may not be common since components are typically initialized and controlled within each screen as per the screen's requirements.
Considering the description in (1), since components do not allow for Connection (Live Data) as an internal argument(Data source is not recognized in Component), there is no concept of data source disconnection. As mentioned earlier, Component uses data snapshots at present. They initialize based on these snapshots, operate using them, and when necessary, export the data back out in the user defined format.
Hi @Shiningriver,
I found out my explanation about Component Data source is not correct. so I've just removed my answer, I ask your understanding for this.
About additional M365 plan for using Power Platform:
In general, employees may have plans like F3, E3, E5, etc. If they do not use premium connectors (e.g., Dataverse, SQL, paid HTTP requests, paid 3rd party connector etc.) within Power Apps or Automate, F3, E3, E5 users do not need additional plans (licenses).
For apps utilizing premium connectors (this also applies when running Automate with premium connectors), the app will display premium marks and expose the required additional plan information for users.
#1
WarrenBelz
637
Most Valuable Professional
#2
stampcoin
570
Super User 2025 Season 2
#3
Power Apps 1919
473
Share
Report
All responses (
Answers (
