How Do I View Data in a Logical Unit?

1. Go to the Project Tree, click Logical Units and verify that the LU has a green icon, indicating that it is deployed to the debug server. If the LU has a white icon, deploy it to the debug server before running the Data Viewer on it. Do either:

   • Right-click the LU > Deploy To debug.
   • Click the Deploy icon, located at the top of Fabric's Debug Panel.

2. Click on next to the selected LU to open the Data Viewer window.

3. Set the Sync Mode in the top left pane; the default Sync Mode is ON.

4. In the Instance ID field (top central pane) - enter an Instance ID (IID).

5. Click Play to generate a new Data Viewer file. Fabric runs the GET LUI command on the debug server of the selected Instance ID. Each sync of an LUI creates a new *.db SQLite file for the LU instance. The LU Instance is displayed in the Instances Tree.

   Note that if you set the Sync Mode to OFF and the Instance ID does not exist in the debug server, the following error message is displayed:

   Instance '[LU Name]:[Instance ID]' was not found and sync is disabled.

6. Double-click the Instance ID to open the Instances Tree drop-down list.

7. Click the Instance DB file to display its tables under the Instance DB Tree.

8. Double-click a table to display its data and then right-click the table to open a context menu with the following options:

   a. Show Data, displays the table’s data.

   b. Show Schema, displays the table’s structure.

   c. Show Indexes, displays the table’s indexes, if defined.

Click for more information about Logical Units.

What Are the Data Viewer Components?

The Logical Unit Data Viewer contains the following areas and components:

• Sync Mode and Instance ID
• Instances Tree
• Instance DB Tree
• Scripting Area
• Results Pane and Toolbar

Sync Mode and Instance ID

This area has the following components:

Import DB File

When clicked, it allows you to browse to an external Data Viewer file and load it.

Sync Mode

Set the Sync Mode for the GET LUI command, initiated by the execution of the Data Viewer. The options are On, Off and Force. The default mode is On.

Instance ID

To complete this field, do either:

• Enter a specific Instance ID value.

• Select a previously stored Instance ID from the drop-down list.

• Write a project (java) function to generate the Instance ID. Note that this function must return a string as an output. Once you have created such function, use the function name in the Instance ID field (that is, do not enter the code that contains the function).

  For example:

  Create an Instance ID by using the function: fnCreateInstID. This function takes an input value and adds 10:

  if (i_id!=null && !i_id.isEmpty()){
     return Integer.sum(Integer.valueOf(i_id),10)+"";
   }
  return "0";

More complex functions can be written, of course, such as generating a random Instance ID or an Instance ID that complies with other criteria (such as certain values).

Play

When the icon is clicked, the data file of the Instance ID is retrieved and saved for debugging.

Instances Tree

The Instance Tree area (top left) displays a tree of available data files in the following order:

• LU
• Instance
• Dated file name

Instance DB Tree

The Instance DB Tree area (bottom left) displays the Table Tree, which includes:

• k2_delta_errors - holds information on errors, including when each error occurred.

• k2_main_info - holds basic information about the LU, like the LU Name and its Instance ID.

• k2_objects_info - holds information for each of the objects in the selected instance.

• k2_transactions_info - holds basic information about each transaction (ID and timestamp).

• Reference tables under k2_Ref - these are displayed only as part of the Instance DB Tree, when the reference object is enabled in the LU Schema's properties.

To display the values of a table in the Tree, right-click the table and select either:

• Show Data, to display the table or view it in the Results pane.
• Show Schema, to display the table structure in the Results pane.
• Show Indexes, to display the table indexes in the Results pane.

Results Pane and Toolbar

(Bottom right) Displays the data or schema requested with the row count.

Scripting Area

The SQL Scripting Area (upper-right pane) is used for writing and running SQL statements on a selected LUDB.

The following options are supported:

How Do I Run an SQL Statement in the Data Viewer?

Run and execute the SQL statement from the Scripting Area on the selected DB file:

1. Enter the SQL statement using SQLite syntax into the Scripting Area.
2. Select the DB file to be used to run the statement from the drop-down list.
3. Do the following:\ a. Click Run or Run on New Tab under the Scripting Area.\ b. Press F5 or Ctrl + Enter. Separate multiple queries with ‘;’.
4. View results in the Results pane.

How Do I Export a Logical Unit Data File?

1. Go to the Instances Tree and right-click the DB File.
2. Click Export Selected DB Files and select the Location and File Name of the exported file (LUDB format).
3. Save your changes.

Additional (Right-Click) DB File Options

• Open DB - opens the Instance DB Tree of the selected DB files.
• Delete Selected DB Files - deletes the selected Instance DB files from the project folder: Fabric\[project name]\Implementation\LogicalUnits\[LU name]\VirtualDB_Data.

Notes

The latest Data Viewer file can be used in the following components:

• New functions / Web Services - the latest Data Viewer is displayed in the Database's drop-down list, whereby the LU table can be invoked on the code. Click for more information on How to Create a New Project Function.
• LU Schema - create a new table, based on SQL Options, to open the DB query where you can select the latest Data Viewer file. Click for more information about Adding a Table to a Schema.
• Population object / DB query - to display the latest Data Viewer file in the Database's drop-down list. Click for more information about Creating a New Table Population.
• Debugging population objects. Click for more information about Debugging a Table Population.