Page History

Image Removed

Translating Tags and Tables

For reports that have different translation options, the first requirement is to create Dictionaries in Displays / Localization.

To switch between languages, use the property:

@Client.Localization = "Spanish";  // 

Use 

Spanish dictionary

@Client.Localization = "

";         // Use default

Translatable Elements

• Tag descriptions
• Table headers
• Static text with locale keys
• Custom messages

Translation Callback

For dynamic translation:

csharp

public void OnReportCustomTableCell(string reportName, 
    string columnName, DataRow row, TableCell tableCell)
{
    if (row["ItemName"].ToString() == "{object}")
    {
        string translated = @Client.Locale(row[columnName].ToString());
        Run cellText = (tableCell.Blocks.FirstBlock as Paragraph)
            .Inlines.FirstInline as Run;
        cellText.Text = translated;
    }
}

Headers and Footers

Creating Headers

1. Create separate report form
2. Design header content:

========================================
     Company Name
     {Info.Date} - {Info.Time}
     Production Report
========================================

Creating Footers

1. Create footer form
2. Add page numbering:

Page {Page.Number} of {Page.Total}
Generated by: {Client.UserName}

Linking to Main Report

1. Open main report properties
2. Set Header property to header form
3. Set Footer property to footer form

Special Features

Alarm Audit Trail

Add alarm history to reports:

{Alarm.Group.AuditTrail}

With custom messages:

csharp

For Tables and Tags, the property above should be enough. However, the callback function must be used to translate an Alarm Audit Trail with added Custom Messages and Comments. 

To enable the translation of custom messages, you must add a string element to the itemName input parameter, as seen below:

string itemName = "{object}"

A final AddCustomMessage with localization capabilities should look like this:

@Alarm.AuditTrail.AddCustomMessage(
    "User:

 {" 

+ 

@Client.UserName 

+ 

"} 

logged",
    null,

 null, null, "{object}", null, null
);

Append Mode
Accumulate data in existing file:
Set Append column to 1
New data adds to file
Preserves historical records
Dynamic Cell Colors
Apply conditional formatting via callback:
csharp
The code added to the callback function is presented below:
code
public void OnReportCustomTableCell(string reportName, 
    string columnName, 
System.Data.
DataRow row, 
System.
Windows.Documents.
TableCell tableCell)
{
if
 
(row["ItemName"].ToString()
 
==
 
"{object}")
{
string[]  Message_Split_Parts  =  
 double value = Convert.ToDouble(row[columnName]
.ToString().Split(’{’,  ’}’
);
 
string
 
Translated_Message
 
= "";

for
 if (
int
value 
i
> 
=
90)
 
0;
 
i
 
<=
 
Message_Split_Parts.Length
 
-
 
1;
 
i++) {

// Translate the custom 
 tableCell.Background = Brushes.Red;
    else if (value > 80)
        tableCell.Background = Brushes.Yellow;
}
Export Formats
Format
Extension
Features
Use Case
PDF
.pdf
Full formatting, images
Professional reports
XPS
.xps
Windows native, exact layout
Internal distribution
HTML
.html
Web-ready, hyperlinks
Online viewing
ASCII
.txt
Plain text, no formatting
Data export
Unicode
.txt
International characters
Multi-language
Best Practices
Test preview - Verify before saving
Use templates - Reusable headers/footers
Validate queries - Check data availability
Handle nulls - Default values for missing data
Size images - Optimize for output format
Test translations - Verify all languages
Archive reports - Implement retention
Troubleshooting
Missing data:
Verify tag names and paths
Check query execution
Confirm data timing
Formatting issues:
Match font availability
Check export format limits
Review page margins
Translation problems:
Confirm dictionary loaded
Check locale keys
Verify callback function
Performance:
Limit query results
Optimize images
Reduce complex formatting

In this section...

The DataGrid is added to the Report following the default logic for tables. The DataGrid language will depend on the dictionary that was enabled when the report was saved.

Headers and Footers

To add a Header and/or Footer to a Report, you need to create one independent report for each. Then, set the reports as the Header and Footer in the Main Report. 

The Header and Footer data (can be text, image, or page numbering) will be replicated throughout the main document.

Appends

By default, when a new report is generated, it replaces the old one if the SaveFile path and ReportName are the same.

However, it is possible to append the most recent data into an existing report, which allows the old and new data to be displayed in the same ReportFile.

To do so, you need to enable the Append column on Reports / Forms, and insert the number ”1” in it.

Examples Using Report

Tags and Symbols

Below is an example of the creation of a report with all elements mentioned above. It is a sample report with a Trend, Tags, and Tables.  

The Table was created in a static format for it to be populated by different Tags (and their current values at the moment the report was saved) as well as the timestamp of their last value.

There is also a Trend element (added as a symbol) that displays the configured Pens (Tag.Temperature and Tag.Pressure) when the Report was saved.

Image Removed

Finally, the created PDF file can be seen below.

Image Removed

You can also check Dynamic Cell Colors in Reports for a code example on how to achieve that effect.

In this section: