Solutions
...
Litmus Production Record Datab...
Interacting with Litmus Produc...
Reading out Data Model definitions
8min
use cases reading out the data model definition can be used to verify what data models do exist and what items and levels are defined this is most useful, when creating a new data model or wanting to modify an existing data model user can do this either by using applications such as microsoft sql server management studio mssql cli this can also be used for building custom solutions based on applications which allow for an odbc connection such as excel c# net python litmus does provide such as custom solution which can be downloaded from our central portal method run s elect query with function prorec prorec gethierarchy as from clause note data models are a hierarchy used to organize and relate production record event data according to isa 88 rules input variables variable name datatype description example @nodename varchar(50) the name of a root node of a specific data model if no specific nodename is to be queried or to get a list of nodename's, the value can also be default which will assume the value % downtime default how to use to read out all or a specific data model definition, execute a select statement from the function prorec prorec gethierarchy providing all the required inputs below is an example using t sql in sql server management studio select from \[le productionrecord] \[dbo] \[ prorec prorec gethierarchy ] ( default ); result the function returns a table as result additional options it is possible to reduce the number of columns returned by the select statement below is an example using t sql in sql server management studio select nodename, item, valuetype, identifier from \[le productionrecord] \[dbo] \[prorec prorec gethierarchy] ( 'downtime'); this will reduce the number of columns returned to only the four selected it is possible to sort data based on users requirements returned by the select statement below is an example using t sql in sql server management studio select nodename, item, valuetype, identifier from \[le productionrecord] \[dbo] \[prorec prorec gethierarchy] ( 'downtime') order by item asc; the result will be a table, where all rows are sorted by their item name in ascending order