Description
Build.one allows the developers to connect their applications build with the platform to OpenEdge databases. For that connection B1 needs different objects to be able to display, maintain and edit the data.
DataSource
A DataSource (or SwatDataSources as it is called the object type in Build.One) is an Object-type that connects to the databases and then provides the data to the UI elements in the screen. Two DataSources can also be connected to provide a set of filtered data, providing from two different tables.
This same functionality can be done with the SwatBusinessEntities objects, but these objects are going to be deprecated and SwatDataSources should be used instead
For more information you can see the detailed article DataSource
ForeignFields
attribute. Check for more information.Dynamic and Static DataSources
Currently in Build.One there are two types of DataSources, Dynamic DataSource (Also known as Dynamic Business Entities) and Static DataSource (Also known as Static Business Entities). Both types of DataSources allows the same data import funcionalities, however the configuration of the import is done different in each type. Dynamic Business Entities can configure the schema of the database trough the Entity object (described in the next section) while the Static ones need to be configured through custom code.
Entity
An Entity (or SwatEntity or as it is called the object type in Build.One) is the object representation of a table in the database. This objects can have Fields objects inside which determine which the columns of the table that are going to be imported. When the whole structure is configured, these fields will represent the columns of a Grid / Table or the Inputs of the maintenance/creation Forms
Entities can also be understood as the Schema of your data, as it is the object that defines the columns of the database.
Once the Entity is configured, it can be imported in the DataSource so it enables the schema configuration in the DataSource. This can be done with the attribute EntityName
in the DataSource and adding the Entity as the value.
Back to Documentation
Back to Home Page