Data Features
This module covers some important features and concepts related to App Data, Data Sources and Global Data Model.
App Data
Client Filters
Add one or more filters to a Database Connected Data Source, that can be enabled or disabled runtime.
Article:
Client filters (article and video)
Data Source Object Properties & Object State
Data Source Object Properties are built-in properties available for each object the data source. You should be familiar with these properties, as well as the Object State properties of Runtime Only Data Sources.
Article:
Data source object properties (incl. Object State)
Data Connectors
Data Connectors are special types of Data Sources. They may not contain data (i.e. you cannot read data into them), but you may do Create, Update or Delete directly towards the database through Data Connector Data Sources.
Article:
Calendar Data Sources
Calendar Data Sources are special types of Data Sources that will populate a list of hours, days, weeks, months etc. between two dates when the App loads. This is very handy for calendar-related UI and logic.
Article:
URL Path
A built-in Data Source exists in all Apps: URL Path. Learn what it is, and how to use it.
Article:
Showroom example:
View Container (usage of URL Path.Sub view)
Global Data Model
Boolean Labels
Useful for giving a meaningful name to Object Class Properties of boolean data type.
Article and video:
Many-to-many relationships
Many-to-many relationships define the relationship between two Object Classes, where either Object Class may have multiple relations to each other.
Many-to-many relationships can be represented in two ways in Appfarm Create: Either using a multi-reference property (an Object Class Property with cardinality Many), or using a separate Object Class. Read more in the article below.
Article:
Sequential and random identifiers
Object Classes come with two build-in Object Class Properties that may be enabled per Object Class. When enabled, the objects are assigned a random identifier and/or sequential identifier upon creation.
Article:
Concurrency Control / Strict object versioning
By default, when 2 different users update the same object, the last write wins. Object Classes have a built-in feature to avoid this, to have a "first come, first served" approach (first write wins) to updates on the same record.
Article:
Last updated