---
title: "Creating a Network Table Paragraph"
canonical: "https://docs.rubiconwater.com/space/RptNC/1979744586/Creating%20a%20Network%20Table%20Paragraph"
format: markdown
---
> Macro (toc)

Use this report component to create a table based on a network object type. Each row of the table displays details for an individual object such as object properties, details of related tags and object attributes. A variety of useful derived properties are available for use in your report. See [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options) for details.

A Network Table paragraph consists of a Data table (defined on the Data tab) which is used to extract data from the database, and a report table (defined on the Table tab) which is used to present the data. You can also add sub-tables which are displayed within network table cells (see [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Adding-a-Sub-Table-to-a-Network-Table](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Adding-a-Sub-Table-to-a-Network-Table)).

# Network Table parameters

These parameters are added to the report automatically for every Network Table paragraph:

- **Network Area/Group** - sets the parent area or group for the objects.
- **Effective Date** - restricts the values shown to those effective at the specified date.
  **Note**
  Note that the Effective Date parameter does not apply to all tag and attribute display options. In general it applies to values calculated over a specified time range, but see [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options) for details.

# Create a Network Table

**Step 1**

Click  **New Paragraph** to open the Add Paragraph dialog and choose *Network Table*. The New Network Table screen opens

**Step 2**

On the **General** tab, enter a name for the paragraph. This will identify the paragraph in the report structure pane.

**Step 3**

On the **Data** tab, select the **Object Type** for the table.

**Step 4**

On the **Data** tab, click **Add** to add a new data column. The Add Column screen opens.

**Step 5**

On the **Add Column** screen, enter the following details:

| **Property** | **Description** |
| --- | --- |
| Type | Choose the type of data to display. Choose:<br>- Object - to display properties of the current object such as Name.
- Tag - to display information about a tag that is related to the object
- Attribute - to display details of an attribute of the object |
| Filter | If you chose the Tag data type, use this to control how the tags are listed in the Criteria field. Choose:<br>By Name - to list the tags by name<br>By Type - to list the tags by Type |
| Criteria | For Tag and Attribute types, choose the specific tag or attribute. |
| Display | Choose what property you want to display for this type.<br>For example:<br>- Display a simple property such as the tag name
- Display a more complex property using a built-in function such as the average tag value over a specified period, or the average tag value a specified time ago.<br>See [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Display-Options) for a description of the available options |

**Step 6**

Add any sub-tables that you need. It is easiest to add sub-tables before you bind the data in the main network table. See [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Adding-a-Sub-Table-to-a-Network-Table](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1979744586/Creating+a+Network+Table+Paragraph#Adding-a-Sub-Table-to-a-Network-Table) 

**Step 7**

Click the **Bind Data** button. This binds the columns in your data table (including any sub-table columns) to columns in the report table.

**Step 8**

On the **Table** tab, make any changes you need to your report table. See <u>[Working with Report Tables and Columns](https://support.rubiconwater.com/help/dms/content/topics/modules/reporteditor/con_work_report_table.htm)</u> for more information.

**Step 9**

Click **OK** to save your changes.

---

# Display Options

These are the properties that you can display in Network Table columns. Note that some options always use the value at the current date while others use the value as at the effective date (specified in the Effective date parameter).

## Object Columns

| **Property** | **Description** |
| --- | --- |
| Object name | Name of the current object |
| Object ID | Unique identification ID for this object record |
| Object type | Object type of the current object |

## Tag Columns

> ℹ️ **Note**
> ℹ️ 
> ℹ️ If the option uses the effective date parameter, values are calculated using the effective date. If they do not use the effective date parameter, or if it is not set, they are calculated using the current date.
> ℹ️ 
> ℹ️ The Effective date column shows which options use the Effective date parameter and which do not.

If the option uses the effective date parameter, values are calculated using the effective date. If they do not use the effective date parameter, or if it is not set, they are calculated using the current date.

| **Property** | **Description** | **Effective date?** |
| --- | --- | --- |
| Tag value | Current value of the tag | No |
| Alarm state | Current alarm state of the tag | No |
| Update time | Date and time when the tag was last updated | No |
| Raw value | Raw tag value (without scaling, formatting or captioning) | No |
| Last logged value | Last value that was recorded in the tag event log as at the effective date. This is captioned if the tag uses captions, but without formatting. For a formatted value use *Last logged tag value*. | Yes |
| Last logged time | Last time when the tag value was last logged to the tag event log as at the effective date. | Yes |
| Tag ID | Unique identification ID for this tag record | No |
| Tag name | Name of the tag | No |
| Tag description | Description of the tag, used as a caption in the application interface | No |
| Tag units | Unit of measurement specified for this tag value | No |
| Minimum value | Minimum value specified for the tag. This is used in trending, and to restrict the values that can be entered manually or applied to a setpoint tag | No |
| Maximum value | Maximum value specified for the tag. This is used in trending, and to restrict the values that can be entered manually or applied to a setpoint tag | No |
| Alarm priority | Priority specified for the tag alarm | No |
| Alarm enabled | Whether alarms are enabled for the tag | No |
| Alarm high high | High high alarm threshold value | No |
| Alarm high | High alarm threshold value | No |
| Alarm low | Low alarm threshold value | No |
| Alarm low low | Low low alarm threshold value | No |
| Last alarm time | Date and time when an alarm was last triggered for this tag | No |
| Last alarm duration | Time elapsed from triggering of the last alarm and alarm resolution or acknowledgment | No |
| Last logged tag value | Last tag value (including any formatting or scaling) that was recorded in the event log as at the effective date.<br>For a captioned tag, this value will be the same as the *Last logged value* | Yes |
| Last logged tag value same time ? ago | Last value logged more than the specified time ago (or before the effective date if that is specified).<br>For example, display the last value logged more than four days ago, or more than four days before the effective date. | Yes |
| Mean tag value over last ? | Mean of all tag values over a specified time period up to the effective date. | Yes |
| Mean tag value same time last ? | Mean of daily tag values at the specified time before the effective date. The mean is calculated for a single day.<br>For example, if the specified time is two months and the effective date is a week ago, calculate the average over a day two months and one week ago. | Yes |
| Sum tag value over last ? | Sum of all tag values over the specified time period before the effective date | Yes |
| Sum tag value same time last ? | Sum of tag values at the specified time before the effective date. Calculated over a day. | Yes |
| Minimum tag value over last ? | Minimum of all tag values over the specified time period up to the effective date | Yes |
| Minimum tag value same time last ? | Minimum tag value the specified time before the effective date. Calculated over a day. | Yes |
| Maximum tag value over last ? | Maximum of all tag values over the specified period up to the effective date | Yes |
| Maximum tag value same time last ? | Maximum tag value the specified time before the effective date. Calculated for a single day. | Yes |
| Count of tag value records over last ? | Count of all tag values over the specified period before the effective date | Yes |
| Count of tag value records same time last ? | Count of tag values the specified time before the effective date. Calculated over a day. | Yes |
| Integrated average value over last ? | Integrated average value of this tag over the last period up to the effective date using a linear interpolation between recorded tag values. | Yes |
| Integrated average value same time last ? | Integrated average value of this tag on a day that was the specified time before the effective date. | Yes |
| Count of alarm records over last ? | Count of all tag events over the specified period up to the effective date. | Yes |
| Count of alarm records same time last ? | Count of tag events for the day that was the specified time before the effective date | Yes |
| Alarm duration (minutes) over last ? | Total duration of alarm states for this tag the specified period before the effective date | Yes |
| Alarm duration (minutes) same time last ? | Total duration of alarm states at the specified time before the effective date. Calculated over a day. | Yes |
| Maximum alarm duration (minutes) over last ? | Maximum duration of alarm states for this tag over the specified period before the effective date | Yes |
| Logging enabled? | Specifies whether the tag event history is logged. | No |

## Attribute Columns

> ℹ️ **Note**
> ℹ️ 
> ℹ️ If the option uses the effective date parameter, values are calculated using the effective date. If they do not use the effective date parameter, or if it is not set, they are calculated using the current date.
> ℹ️ 
> ℹ️ The Effective date column shows which options use the Effective date parameter and which do not.

| **Property** | **Description** | **Effective date?** |
| --- | --- | --- |
| Attribute value | Value of this attribute at the effective date | Yes |
| Date effective | Date and time when the attribute value at the effective date became effective | Yes |
| Attribute label | Descriptive label for the attribute as used in the application interface | No |
| Units of measure | Unit of measure for this attribute | No |
| Historic attribute value same time ? ago | Value of this attribute at the specified time before the effective date<br>For example, value of the attribute three months before the effective date. | Yes |
| Historic date effective same time ? ago | Date and time when the attribute value that applied at the specified time before the effective date became effective.<br>For example, if the effective date was one month ago, and the specified time ago (the "?" time) was three months, this option:<br>- Finds the value of the attribute four months ago
- Returns the date and time when that value became effective. | Yes |

# Adding a Sub-Table to a Network Table

A sub-table is another way of displaying the same information that you can display in a Network table. If you display information in a sub-table, a copy of the subtable is displayed in a single column for each row of the main table. The parent object of the main table row is the parent object of the sub-table.

1. On the Network Sub-Table Tab, click **Add** to create a sub-table. The Network Sub-Table Properties screen opens.
2. Create a data table and a display table in the same way as for the main table.
3. Click **OK** to save your changes.

When you bind the data in the main data table, a new column is created in the report table for each sub-table.

---