...
One of the unbeaten strengths of the SmartComponent Library is the implementation of Business Entities and the tooling provided for developing and testing thosethese.
In most situations static Business Entity classes designed and generated by the Business Entity Designer are the best choice – as they provide a high degree of flexibility and customizability to developers. However, customers have reported use-cases for dynamically rendered Business Entities, especially for simple tables with no requirement for custom business logic (e.g. validation or calculated fields).
...
The default implementation is provided through the DynamicBusinessEntityRepository service. This implementation is receiving receives the configuration from one or multiple JSON documents describing the model of the dynamic business entity. The file names for the JSON documents are received from the IConfigurationProvider service (e.g. .applicationsettings or .restapplicationsettings file) as a comma delimited list in the DynamicBusinessEntityDefinitions attribute:
...
In the top-level of the JSON Document, each single Dynamic Business Entity is described by a JSON document which is referenced by an a unique identifier. The following sample JSON contains a single model for an entity named “DynamicEmployeeBusinessEntity”:
...
The schema of a temp-table can also inherit files from multiple database tables and allows you to change the names of the temp-table fields. In this example the eCustomer temp-table inherits all fields from the Customer database table and includes a field named RepFullName based on the Salesrep.RepName field as well as a field based on the Region field of the Salesrep table.
...