Description
DataSource Objects (DSO) are used in Build.One as the abstraction layer for providing data to another object (like a Grid or a form). At design time, you can add DSO to the screen and it doesn’t matter, from where the data is being fetched. The different possibilities for fetching the data for a DSO are:
- From an entity (could be a programmatically defined one or one directly connected to one (or many) database table)
- These will be also created, when using the
Quick Builder - Automated Generation of B1 Objects - From an mock-data set, like described in
Use Mock-up Datasource - From the Build.One Data-Hub to display data from 3rd party systems
Attributes
Attribute | Description | Example/Values |
defaultSort | Define here the field(s) and order (desc, asc), which you want to have as the default sorting | "Field1,Field2 desc" or "Field1 desc,Field2” |
entityName | Name of the contained entity in the DSO
Best Practice: Use a small e as prefix for the entityName of the contained entity | |
foreignFields | Use this to define the keys to join two DSO as comma-separated list | ForeignKeyDSO1,ForeignKeyDSO2 |
resourceName | ||
Subtype | ||
Different Events | Events are used on different places in time to execute custom code | |
ServerEventHandler | Here you can add your custom code EventHandler, which can execute code |
How to use it
- You can use a DSO in screen designer, simply drag&drop the needed DSO to the screen (not a specific panel)
- Use one of these connections for DSO to other objects:
PrimarySDOAs the root DSO of a screen in connection to the screen itself. There should be always one root DSODataFor connecting e.g. other DSO or GridsDisplayFor connecting e.g. Forms
Important information
The DataSource field names “_id” and “id” should not be used as their are immutable and used internally to identify records.
Use Cases
Back to 
Documentation
Back to Home Page