Missing Data Overview Report Templates
Missing Data Overview report templates contain a ReportDefinition page and a ReportSheet page, that together describe the Missing Data Overview reports you can produce. CygNet provides a sample report template file MissingDataOverviewTemplate.xlsx for reference. It is stored in the CygNet\Services\FMS\ReportTemplates\Samples folder on your host server.
The Missing Data Overview report publishes a synopsis of daily data collection status information for each selected Node within the time range, showing where there is incomplete or missing data. The report displays data in Contract time (C). Gas and (periodic metering, batch, and ticket) liquid devices are supported.
The ReportDefinition sheet includes the following parameters to describe the type of report to build.
The ReportSheet sheet includes the following sections and corresponding tokens to describe the specific format of the report to build. Valid tokens will be replaced by the values they represent. You may also include additional information you wish to see in the report.
Displaying Additional (Non-Token) Values
You can enter additional (non-token) elements such as logos, labels, or text into reports. Elements that are not valid token values will be displayed as entered.
Note: This means that tokens with typographical errors, therefore not "valid" tokens, will also be displayed as entered.
Example
[BeginDateTime] is a valid token. If you use [BeginDate] (not a valid token) instead of [BeginDateTime], the value will be displayed as "[BeginDate]" instead of displaying the date/time value desired, since [BeginDate] is not a valid token.
|
[BeginDate] |
Configuring the ReportDefinition
The ReportDefinition uses parameters to describe the type of report for the service to build. The following parameters determine the described characteristics of your report.
Missing Data Overview Report: ReportParameters
Report parameters, which appear between #ReportParameters# and #End#, can be defined by the following values.
| Parameter | Description | Value |
|---|---|---|
|
ReportName |
The value defined in this cell will be used for the report name, as it will appear in drop-down menus in FMS Explorer and CygNet Explorer. See Using the Reports Control and Scheduling FMS Command Tasks in the MSS for more information. |
Enter a value to be used for the report name. Example Missing Data Overview |
|
CommandName |
The value defined in this cell will be used by the service to determine which specific report command type to execute. See FMSClient Methods in the Scripting section for more information. |
Enter a value to specify the report command name. Example MDOR Note: Maximum of 7 characters; letters or numbers only, no spaces. |
Missing Data Overview Report: Worksheet Parameters
Missing Data Overview report worksheet parameters, which appear between #Worksheet# and #End#, can be defined by the following values.
| Parameter | Description | Value |
|---|---|---|
|
ReportType |
The value defined in this cell will be used to represent the standard FMS report type you are configuring. |
Enter a value to be used to indicate the type of the report. Example Missing Data |
|
NullToken |
The value defined in this cell will be used to represent null values in your report. |
Enter a value to be used to indicate a "null value" cell in the report. Example - |
|
The value defined in this cell will be used to represent the subtype of the Missing Data report you are configuring. |
Enter a value to indicate the subtype of the report. Options are Overview or Detailed. Default value is Overview. |
|
|
Missing |
The value defined in this cell will be used to represent time periods in your report for which all data is missing. |
Enter a value to be used in the data cell to indicate "all data missing" in the report. Example M See [Missing] style parameter for cell format information. |
|
Incomplete |
The value defined in this cell will be used to represent time periods in your report for which data is incomplete. |
Enter a value to be used in the data cell to indicate "some data missing" in the report. Example I See [Incomplete] style parameter for cell format information. |
|
Unavailable |
The value defined in this cell will be used to represent time periods in your report for which data is unavailable. |
Enter a value to be used in the data cell to indicate "unavailable data" in the report. Example U See [Unavailable] style parameter for cell format information. |
|
Future |
The value defined in this cell will be used to represent time periods in your report for which data cannot yet be complete, because all (future days) or part (today) of the time period is in the future. |
Enter a value to be used in the data cell to indicate "future time period" in the report. Example > See [Future] style parameter for cell format information. |
|
HideNoMissingMeters |
The value defined in this cell will be used to specify whether or not meters that do not have missing data will be skipped in the report. |
Enter a value to indicate whether or not to hide meters from the report when no data is missing. Options are Yes or No. Default value is Yes. |
|
The value defined in this cell will be used in your report to represent the value for the Group name or Group description fields when either of the following is true.
|
Enter a value to be used to indicate the Group name or Group description when the command was not run against a single group Node. Example [Invalid Group] |
|
|
NodeSortOrder |
The value defined in this cell will be used to specify the order in which to display Node results in the report. |
Enter one of the following options.
Default value is Name ascending. This parameter is optional. |
|
SubReportHeaderFrequency |
The value defined in this cell will be used to specify how many Node results to display per page in the report. |
Enter the number of results to show per page. Default value is 9. |
|
RptStDate |
Note: If you use this parameter in your report template, the RptStDate parameter will no longer appear for configuration in FMS Explorer or CygNet Explorer. See Missing Data Overview Report Definitions (FMS Explorer) or Reports: Missing Data Overview (CygNet Explorer) for more information. |
If used, enter a valid start date value for the report. RptStDate and RptEndDate must be the same configuration parameter type. Note: The report will only include records that exist entirely within the specified date range. See Selecting Date and Time for more information. This parameter is optional. |
|
RptEndDate |
Note: If you use this parameter in your report template, the RptEndDate parameter will no longer appear for configuration in FMS Explorer or CygNet Explorer. See Missing Data Overview Report Definitions (FMS Explorer) or Reports: Missing Data Overview (CygNet Explorer) for more information. |
If used, enter a valid end date value for the report. RptStDate and RptEndDate must be the same configuration parameter type. Note: The report will only include records that exist entirely within the specified date range. See Selecting Date and Time for more information. This parameter is optional. |
Configuring the ReportSheet
The ReportSheet uses tokens to describe the format of the report you want to run. The following tokens determine the report content, and will retrieve the corresponding values for display in your report.
Note: Enter report tokens carefully, as the tokens are case sensitive. Typographical errors (therefore not "valid" tokens) will be handled as "additional values" and displayed as entered; the non-token value will appear in your report instead of the actual value(s) the correctly entered token would have retrieved. See Displaying Additional (Non-Token) Values above for more information.
Missing Data Overview Report: Header Tokens
Missing Data Overview report definition headers, which appear above #EndReportHdr#, can be described by the following tokens and by entering additional values of your choice.
| Token | Description |
|---|---|
| [BeginDateTime] | The start date, in Contract day (C), of the time range for the record |
| [CmdGroupName] | The name of the group Node against which the command was run, if applicable See also NoCmdGroupToken parameter. |
| [CmdGroupDesc] | The description of the group Node against which the command was run, if applicable See also NoCmdGroupToken parameter. |
| [GeneratedDateTime] | The time the report was generated, in Local time (L) |
| [LastCompleteContractDay] | The date, in Contract day (C), of the last day containing complete data |
| [TotalDeviceCount] | The total number of devices in the report |
Missing Data Overview Report: SubReport Header Tokens
Missing Data Overview report subreport headers, which appear between #SubSection# SubReportHeader and #End#, can be described by the following tokens.
| Token | Description |
|---|---|
| [=] | When used as the first three characters, turns the cell into a formula |
| [RowNumber] | The current row number being displayed |
| [LastCompleteContractDay] | The date, in Contract time (C), of the last day containing complete data |
| [CurrentDeviceCount] | The index of the device being displayed |
| [TotalDeviceCount] | The total number of devices in the report |
| [NodeContractHour] | The contract hour of the Node |
| [NodeDaysOfData] | The number of days for which the data source of the Node will retain data |
| [NodeDesc] | The Node description |
| [NodeId] | The Node ID |
| [NodeInstallDateTime] | The install date/time for the Node, in Device time (D) |
| [NodeName] | The Node name |
| [NodePollingFacilityId] | The polling facility ID of the Node |
| [NodePollingFacilityTag] | The polling facility tag of the Node |
| [NodePollingSiteService] | The polling Site.Service of the Node |
| [NodeReportingFacilityId] | The reporting facility ID of the Node |
| [NodeReportingSiteService] | The reporting Site.Service of the Node |
| [NodeSecurityApp] | The security application of the Node |
| [NodeSortPriority] | The sort priority of the Node |
| [NodeTimezone] | The time zone configured for the Node |
| [NodeTimezoneUsingDst] | The daylight saving time status of the Node |
| [NodeType] | The Node type |
| [PollingFac_Attr0] - [PollingFac_Attr39] |
Polling facility indexed text attributes 0 through 39 (each a separate token) |
| [PollingFac_Category] |
Polling facility category |
| [PollingFac_Comment] |
Polling facility comment attribute |
| [PollingFac_Desc] |
Polling facility description |
| [PollingFac_Info0] |
Polling facility info attribute 0 Default attribute name is Facility Location |
| [PollingFac_Info1] |
Polling facility info attribute 1 Default attribute name is Facility Contact |
| [PollingFac_IsActive] |
Polling facility active flag |
| [PollingFac_Table0] - [PollingFac_Table59] |
Polling facility indexed table-driven attributes 0 through 59 (each a separate token) |
| [PollingFac_Type] |
Polling facility type |
| [PollingFac_YesNo0] - [PollingFac_YesNo19] |
Polling facility indexed Yes/No attributes 0 through 19 (each a separate token) |
| [RecordSpan] | The span for the record, e.g. hourly, daily |
Missing Data Overview Report: Style Tokens
All style token cells in the template must appear in this section. Do not delete any style token cells from the report template file, or the report will fail. It is acceptable to place blank cells between token cells.
The style of the Missing Data Overview report, which appears between #StyleTokens# and #End#, can be described by the following tokens.
Missing Data Overview Report: Data Table Header Tokens
Missing Data Overview report data table headers, which appear between #SubSection# DataTableHeader and #End#, can be described by the following tokens.
Note: In PDF format, reports containing tables that span multiple pages will repeat the data table header on each contiguous page.
| Token | Description |
|---|---|
| [=] | When used as the first three characters, turns the cell into a formula |
| [BeginDateTime] | The BeginDateTime token value used for the first day in the Date/Time row. See [BeginDateTime] style parameter for cell format information. |
| [RowNumber] | The current row number being displayed |
| [CurrentDeviceCount] | The index of the device being displayed |
| [TotalDeviceCount] | The total number of devices in the report |
| [NodeContractHour] | The contract hour of the Node |
| [NodeDaysOfData] | The number of days for which the data source of the Node will retain data |
| [NodeDesc] | The Node description |
| [NodeId] | The Node ID |
| [NodeInstallDateTime] | The install date/time for the Node, in Device time (D) |
| [NodeName] | The Node name |
| [NodePollingFacilityId] | The polling facility ID of the Node |
| [NodePollingFacilityTag] | The polling facility tag of the Node |
| [NodePollingSiteService] | The polling Site.Service of the Node |
| [NodeReportingFacilityId] | The reporting facility ID of the Node |
| [NodeReportingSiteService] | The reporting Site.Service of the Node |
| [NodeSecurityApp] | The security application of the Node |
| [NodeSortPriority] | The sort priority of the Node |
| [NodeTimezone] | The time zone configured for the Node |
| [NodeTimezoneUsingDst] | The daylight saving time status of the Node |
| [NodeType] | The Node type |
| [RecordSpan] | The span for the record, e.g. hourly, daily |
Missing Data Overview Report: Data Table Tokens
Missing Data Overview report data table parameters, which appear between #SubSection# DataTable (1 or 2) and #End#, can be described by the following tokens.
| Token | Description |
|---|---|
| [=] | When used as the first three characters, turns the cell into a formula |
| [FirstRow] | The row number of the first row in the data table |
| [RowNumber] | The current row number being displayed |
| [BeginDateTime] | The start date, in Contract day (C), of the time range for the record |
| [NodeDesc] | The Node description
Note: Appears only when the SubReportType Worksheet parameter value is "Overview" |
| [NodeName] | The Node name
Note: Appears only when the SubReportType Worksheet parameter value is "Overview" |
| [NodePollingFacilityId] | The polling facility ID of the Node |
| [NodePollingFacilityTag] | The polling facility tag of the Node |
| [NodePollingSiteService] | The polling Site.Service of the Node |
| [NodeReportingFacilityId] | The reporting facility ID of the Node |
| [NodeReportingSiteService] | The reporting Site.Service of the Node |
| [MissingDataStatus] | The status of each daily record span regarding missing data
Note: Appears only when the SubReportType Worksheet parameter value is "Overview" |
| [PollingFac_Attr0] - [PollingFac_Attr39] |
Polling facility indexed text attributes 0 through 39 (each a separate token) |
| [PollingFac_Category] |
Polling facility category |
| [PollingFac_Comment] |
Polling facility comment attribute |
| [PollingFac_Desc] |
Polling facility description |
| [PollingFac_Info0] |
Polling facility info attribute 0 Default attribute name is Facility Location |
| [PollingFac_Info1] |
Polling facility info attribute 1 Default attribute name is Facility Contact |
| [PollingFac_IsActive] |
Polling facility active flag |
| [PollingFac_Table0] - [PollingFac_Table59] |
Polling facility indexed table-driven attributes 0 through 59 (each a separate token) |
| [PollingFac_Type] |
Polling facility type |
| [PollingFac_YesNo0] - [PollingFac_YesNo19] |
Polling facility indexed Yes/No attributes 0 through 19 (each a separate token) |
Missing Data Overview Report: SubReport Footer Tokens
Missing Data Overview report subreport footers, which appear between #SubSection# SubReportFooter and #End#, can be described by the following tokens.
| Token | Description |
|---|---|
| [=] | When used as the first three characters, turns the cell into a formula |
| [FirstRow] | The row number of the first row in the data table |
| [LastRow] | The row number of the last row in the data table |
| [RowNumber] | The current row number being displayed |
| [CurrentDeviceCount] | The index of the device being displayed |
| [TotalDeviceCount] | The total number of devices in the report |
| [NodeContractHour] | The contract hour of the Node |
| [NodeDaysOfData] | The number of days for which the data source of the Node will retain data |
| [NodeDesc] | The Node description |
| [NodeId] | The Node ID |
| [NodeInstallDateTime] | The install date/time for the Node, in Device time (D) |
| [NodeName] | The Node name |
| [NodePollingFacilityId] | The polling facility ID of the Node |
| [NodePollingFacilityTag] | The polling facility tag of the Node |
| [NodePollingSiteService] | The polling Site.Service of the Node |
| [NodeReportingFacilityId] | The reporting facility ID of the Node |
| [NodeReportingSiteService] | The reporting Site.Service of the Node |
| [NodeSecurityApp] | The security application of the Node |
| [NodeSortPriority] | The sort priority of the Node |
| [NodeTimezone] | The time zone configured for the Node |
| [NodeTimezoneUsingDst] | The daylight saving time status of the Node |
| [NodeType] | The Node type |
| [PollingFac_Attr0] - [PollingFac_Attr39] |
Polling facility indexed text attributes 0 through 39 (each a separate token) |
| [PollingFac_Category] |
Polling facility category |
| [PollingFac_Comment] |
Polling facility comment attribute |
| [PollingFac_Desc] |
Polling facility description |
| [PollingFac_Info0] |
Polling facility info attribute 0 Default attribute name is Facility Location |
| [PollingFac_Info1] |
Polling facility info attribute 1 Default attribute name is Facility Contact |
| [PollingFac_IsActive] |
Polling facility active flag |
| [PollingFac_Table0] - [PollingFac_Table59] |
Polling facility indexed table-driven attributes 0 through 59 (each a separate token) |
| [PollingFac_Type] |
Polling facility type |
| [PollingFac_YesNo0] - [PollingFac_YesNo19] |
Polling facility indexed Yes/No attributes 0 through 19 (each a separate token) |
| [RecordSpan] | The span for the record, e.g. hourly, daily |
Missing Data Overview Report: Report Footer
Missing Data Overview report footers, which appear between #SubSection# ReportFooter and #End#, can be described by the values you enter. Type desired text into the cells, and format as desired.


