Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

LongMonthNames

The format defined replaces the long month names convention in the regional settings.

Syntax:  

LongMonthNames

When modifying the variable, the ; needs to be used to separate the individual values.

The following example of the LongMonthNames function defines month names in full:

Set LongMonthNames='January;February;March;April;May;June;July;August;September;October;November;December';

The LongMonthNames function is often used in combination with the following functions:

Related functions
Function Interaction
Date - script and chart function Script function to return DayNamesas field values.
LongDayNames Long form values of DayNames.

Regional settings

Unless otherwise specified, the examples in this topic use the following date format: MM/DD/YYYY. The date format is specified in the SET DateFormat statement in your data load script. The default date formatting may be different in your system, due to your regional settings and other factors. You can change the formats in the examples below to suit your requirements. Or you can change the formats in your load script to match these examples. For more information, see Modifying regional settings for apps and scripts.

Default regional settings in apps are based on the user profile. These regional format settings are not related to the language displayed in the Qlik Cloud user interface. Qlik Cloud will be displayed in the same language as the browser you are using.

If you are an app creator, you can set the default region for apps you create. For more information, see Setting your preferred regional settings for creating apps and scripts in Qlik Cloud Analytics.

Example 1 - System variables default

Example 2 - Change system variable

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!