Data structures can be also described as entity-sets. While entities describe a single dimension (entity/fields), data structures allow definition of a hierarchical schema.
Data Service LoadData method
Data Service StoreData method
- Data API
- File Download API
Data structures can be defined in different ways. Either by referencing an already existing entity model or by reusing existing XSD schemas provided by other software vendors. However, defining data structures from the entity model is the easiest and allows the best results when used in sequential workflows.
This data structure is based on the entities defined in the entity model.
This data structure allows you to enter XML schema definition (XSD) manually. XSD Data Structure cannot be used as a parameter of a data service to load the data, because no mapping to the entities exists. But it can be used as a context in a sequential workflow that can be passed to external services if these require input or output parameters of such a schema.
Entity Mapping Data Structure can have the following child elements:
Maps an entity so it can appear in the data structure. When filled with data (from a service or by user), it will contain data rows of either all or only of the selected columns.
Defines parameters specified on the data structure level that can be used e.g. for dynamic filtering.
Defines a set of default values that will override the default values specified in an entity.
Defines a set of predefined entity filters that can be selected when loading data from a DataService.
Defines a set of rules that will automatically calculate values inside the data set.
Defines a list of fields by which the data will be sorted either when loaded from the database or in the front-end application.
|Rule Set Reference|
|XSD Data Structure|