What is Report Culture Awareness, and how does it impact Mail & Deploy reports?
What is Report Culture Awareness, and how does it impact Mail & Deploy reports?
FIRST CREATED ON 30 Apr 2020 I AUTHOR Emma Camacho
A culture is a set of rules that specify how numbers and dates are formatted (Windows Regional Settings).
Generally speaking, the culture defines in what format numbers and
dates are being presented to users when they are displayed in the user
interface or included in a report.
However,
these culture settings only apply when converting the original datatype
(e.g. a date or a decimal) to a textual representation; therefore, not
all report types can be culturally aware.
Culture awareness is handled in different report types as shown below:
HTML Reports: All
data that is displayed in HTML reports are represented as text;
therefore HTML reports do support culture awareness. Whenever a value of
another data type (e.g. a date) is written to the HTML report, it is
converted to text first. This conversion process uses the culture of the
report. Microsoft Excel Reports: In
Microsoft Excel, culture awareness is handled by Excel automatically;
the values are written to the Excel Workbook in their original data type
(thus, no conversion that would require culture awareness is required)
and each cell can have a format string that defines how dates and
numbers shall be formatted. When a Microsoft Excel Workbook is opened on
a computer, the culture of the user (as set in the operating system)
will be used to determine how numbers and dates will be displayed to the
user. Therefore, Mail & Deploy does not apply culture-specific
settings to Microsoft Excel Reports and the option to set culture is not
enabled. Microsoft PowerPoint Reports: All
data in Microsoft PowerPoint Presentations is represented as text;
therefore PowerPoint reports do support culture awareness. Whenever a
value of another data type (e.g. a date) is written to the PowerPoint
report, it is converted to text first. This conversion process uses the
culture of the report.
Microsoft Word Reports: All
data in Microsoft Word Documents are represented as text; therefore
Word reports do support culture awareness. Whenever a value of another
datatype (e.g. a date) is written to the Word report, it is converted to
text first. This conversion process uses the culture of the report.
QlikView Document Embedded Reports: When
creating a report document from a QlikView Document Embedded Report,
the QlikView Desktop Client will do all the rendering and conversions
required for the generation of the output Adobe PDF document. Therefore,
Mail & Deploy does not apply culture-specific settings to QlikView
Document Embedded Reports and the option to set culture is not enabled.
However,
even in report types with enabled culture awareness, you have to be
careful as to when culture settings made in Mail & Deploy are
applied to that report.
Culture-specific formatting is only applied, if:
The report type supports culture awareness.
The value written to the report is in its original datatype.
Example:
You want to create a Microsoft Word report based on QlikView document
that contains a date field. If you want to write the value of that date
field into the report document, you can use a text element that contains
an expression that directly references the field of the QlikView
Document that contains the date value. If that is the case when
evaluating the content of the text element, a value of datatype date
will be returned by the expression and needs to be converted to a text
value in order to be inserted in the Microsoft Word document; therefore,
culture settings made in Mail & Deploy will be applied. If,
however, the expression you use as the content of the text element does
not contain a direct reference to the field but rather a datasource
expression which automatically applies a date format to the value of the
field that contains the date, then this expression will already return a
formatted textual representation of the date; therefore, culture
settings made in Mail & Deploy will not be applied, because of Mail
& Deploy treats this value as a text, not as a date.
In
reports with enabled culture awareness, the culture will also be
applied when converting values in expressions except for conversions
that are being done inside a datasource expression.
Looking for Additional Guidance?
If you require more detailed information or further assistance, please visit our comprehensive Online Documentation. Our resources are designed to help you navigate all features and functionalities effectively.
You have a date variable in Qlik (formatted as DDMMYYYY), but when used in Mail & Deploy, it gets converted into a number. For example, the file output appears as File_45014.xlsx instead of File_29032023.xlsx. Solution: To resolve this issue, you can ...
You want to create an Excel report using Mail & Deploy. Specifically, you have a table spanning columns A to K and need Column G to display the result of Column I × Column B, instead of using the result directly from the Qlik app. Solution: While the ...
FIRST CREATED ON 23 May 2023 I AUTHOR Emma Camacho Configuring the culture for a report ensures correct date formats, currency, and locale-specific settings. This article shows you how to set it up: (1) Set the Culture in the General Report Settings ...
FIRST CREATED ON 14 Jun 2023 I AUTHOR Emma Camacho Qlik Sense themes offer a powerful way to customize the appearance of your reports. By applying themes, you can easily align the look and feel of your reports with your brand or preferred style. ...
FIRST CREATED ON 31 Jan 2024 I AUTHOR Emma Camacho Synchronizing cell insertion in an Excel report within Mail & Deploy ensures that your data is accurately aligned and formatted. Here's an example to guide you through the process: If you need a ...