View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002154 | CaseTalk Modeler | Repository | public | 2019-05-28 17:29 | 2024-03-13 09:37 |
Reporter | BCP Software | Assigned To | BCP Software | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Target Version | 13.5.x | ||||
Summary | 0002154: External reference data for otft population | ||||
Description | Being able to support external data would be helpful in validating the population without having to manually edit the population yourself. This linking could be a great way to import/export fixed data into the modeling environment. | ||||
Tags | No tags attached. | ||||
CaseTalk Edition | unknown | ||||
related to | 0001513 | assigned | BCP Software | Query external database for population checks |
related to | 0002281 | closed | BCP Software | Ability to navigate external data |
related to | 0002321 | assigned | BCP Software | Support INSPIRE code lists |
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.) | |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-05-28 17:29 | BCP Software | New Issue | |
2019-05-29 14:39 | BCP Software | Summary | Support external masterdata => Support external reference data |
2019-05-29 14:39 | BCP Software | Description Updated | |
2019-08-06 17:40 | BCP Software | Relationship added | related to 0001513 |
2019-08-06 17:41 | BCP Software | Note Added: 0001509 | |
2019-08-06 17:42 | BCP Software | Assigned To | => BCP Software |
2019-08-06 17:42 | BCP Software | Status | new => assigned |
2019-10-04 14:02 | BCP Software | Relationship added | related to 0002281 |
2019-12-11 21:18 | BCP Software | Relationship added | related to 0002321 |
2020-05-26 20:46 | BCP Software | Note Added: 0001649 | |
2020-12-03 12:05 | BCP Software | Note Added: 0001830 | |
2020-12-16 18:09 | BCP Software | Note Added: 0001833 | |
2020-12-16 18:10 | BCP Software | Target Version | Future => 11.0 |
2021-01-12 21:14 | BCP Software | Summary | Support external reference data => External reference data for otft population |
2021-01-12 21:16 | BCP Software | Fixed in Version | => 11.1 |
2021-01-12 21:16 | BCP Software | Fixed in Version | 11.1 => |
2021-01-12 21:16 | BCP Software | Target Version | 11.0 => 11.1 |
2021-02-11 15:00 | BCP Software | Target Version | 11.1 => 13.0.1 |
2021-10-21 10:40 | BCP Software | Note View State: 0001509: private | |
2021-10-21 10:40 | BCP Software | Note View State: 0001509: public | |
2023-10-25 11:40 | BCP Software | Target Version | 13.0.1 => 13.3 |
2024-03-13 09:37 | BCP Software | Target Version | 13.3 => 13.5.x |