Comment on page
Set data source attributes
This action node can control the number of objects read in to an app at runtime. It is useful for data sources that could potentially contain many objects or data sources that are not frequently used. It is often used in conjunction with the following attributes set directly on the data source:
- Initially skip object count
- Initially limit object count
- Initially subscribe to updates
- Initially disabled
This attribute can be used to control if objects are read into a data source or not. This can be used to implement lazy loading of data, enabling the data source only when a user performs a particular action. For example, if you have a data source
Company Logand you only need this data when the user clicks a
View Historybutton, you can have the data source initially disabled and enable it if the user clicks the button.
Limit can be used to control the number of objects in a data source. For example, if you want to want to implement infinity scrolling for a client user you can use initially limit object count and update the limit value to show more objects when a user scrolls in a container.
Skip is used to control which objects are read into a data source. For example, if you want to implement pagination for a client user to browse the contents of a data source you can use skip in conjunction with limit. As the user switches between pages you can update the skip value based on the page the user is on. You can let them specify the number of objects to show per page by updating the limit value.
This attribute can be used to automatically refresh the contents of a data source based on changes made by other users. This can have a performance impact, so it should only be used when necessary.
Visible when a Data Source is selected.