Skip to main content Skip to complementary content

minute - script and chart function

This function returns an integer representing the minute when the fraction of the expression is interpreted as a time according to the standard number interpretation.

Syntax:  

minute(expression)

Return data type: integer

When to use it

The minute() function is useful when you would like to compare aggregations by minute. For example, you could use the function if you would like to see activity count distribution by minute.

These dimensions can be created either in the load script by using the function to create a field in a Master Calendar table. Alternatively, they can be used directly in a chart as a calculated dimension.

Function examples
Example Result

minute ( '09:14:36' )

Returns 14.

minute ( '0.5555' )

Returns 19 ( Because 0.5555 = 13:19:55 ).

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 – Variable (script)

Example 2 – Chart object (chart)

Example 3 – Scenario

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!