Data is populated, via a selection, from the repository (back end database) into a Data Source and can then be read, changed/manipulated, deleted, new records created, etc. prior to Evoke writing it back to the physical database when the Data Source is saved.
Name - Each Data Source must have a name to identify it within Pages.
Entity Type - Each Data Source must have an Entity Type that defines the structure of the Data Source to match a specific Entity.
Collection - Data Sources can be singular (a single instance of the Entity structure or a single record) or a Collection (multiple instances of the Entity structure or a group of records)
Auto Saved - the Auto Saved option defines if a Data Source is connected to the automatic save/cancel buttons in the App. If this is ticked then when the Data Source is changed the tick (commit/save to physical database) and cross (reject/discard changes) options automatically are displayed.
Initialize - the initialize option sets the datasource to be a "blank version" or "proper instance" of the object, making it able to hold data, have data assigned to it, etc. As opposed to a "structure only" version or "Empty instance" that cannot hold or manipulate any data. An "Empty instance" is overwritten with a "proper instance" when a selection or read is used to populate the datasource.
Data Paging - providing the ability to deliver data to desktop and mobile devices in one roundtrip or as a series of pages.
Use the DataSource Build button to populate the name of a DataSource and the path to any Related Data whenever this is required when working on your app design.
There are two main purposes of Refined Data Sources, 1) to provide the data populated in the Root Data Source in a different view i.e. Sorted (by setting the Initial Sort Properties to a space separated list of Property names to sort the data by or for reverse order add a minus sign before the property name) or Filtered using the build button and 2) to provide the App user with the option of sorting, searching and filtering data displayed in the App. The options can be turned on, when a refined datasource is used, in the Template General settings section.
If you do not wish to or need to include Evoke search/sort/filter options on a datasource/datagrid in your app then you will not need to create a refined datasource and can leave that section blank.
Use the DataSource Build button to populate the name of a Refined DataSource and the path to any Related Data whenever this is required when working on your app design.
Use the DataSource Build button to populate the name of a Global DataSource whenever this is required when working on your app design.