 |
An option would be to "File\Import\Reference Data" to attach an XLS as a local SQLite database. Or to be able to open an ODBC connection within the same attached manner. This way linking population would be possible as (Copy+)Paste in the population editor window, but simply using "select from .......". |
|
|
Once source data is connected, being able to query that data using SQL, and having these query definitions attached to OTFT's would make it populateble. We would need some linking or storage of SQL though. |
|
|
An indicator for OTFT's for Reference Type is helpful. This would require a definition on where to find the population, or reference, but at least the indicator is already there. That way it can be communicated. This is almost the same as the 'static population' indicator. Which means the population is not maintained by the artifact itself, but something outside the scope of this model. |
|
|
Once OTFT's are able to handle a Database Connection Name and a Reference Data SQL Statement, the Population Editor can use this to allow users to see the reference data externally (or internally if the Connection Name is set to the IG itself.) |
|
|
XLS reference data may be imported as Reference Data, once that is done, it is mirrored to a sqlite database and stored in the AppData folder. Using the Data Explorer Mapping, the population editor dialog can import rows from the reference data source (or any other connection). |
- Anonymous
