Skip to main content

GetSysAttr - Script and chart function

The GetSysAttr() function is used to return information about the tenant and space in which an app is located. With the GetSysAttr() function, you can evaluate the tenant ID and name, space ID and name, and other details about the environment where the app resides. This function simplifies space and tenant identification of a Qlik Sense app that might be moved between different environments. The function makes it easy to identify the specific environment you are working in. This is particularly useful during the development, testing, acceptance and production (DTAP) stages of an app's life cycle.

This function can be used in the app's load script or chart expressions, either directly as an expression or in an expression stored as a variable. If you anticipate your app being moved between spaces or tenants during its life cycle, use the function in a chart expression to dynamically obtain space and tenant information without reloading the app. When doing so, store the function expression in a variable outside the load script, or use the function directly in the chart expression.

Use GetSysAttr() to determine the following information about your app:

  • The ID of the tenant where the app is located.

  • The name of the tenant where the app is located.

  • The URL of the tenant where the app is located.

  • The alias URL that has been defined for the tenant containing the app.

  • The region of the tenant that contains the app.

  • The ID of the space where the app is located.

  • The name of the space where the app is located.

  • The type of the space (shared or managed) where the app is located.

If you use this function in Qlik Sense Client-Managed, it returns empty data values. Therefore, you can use the function to develop load scripts in Qlik Sense Client-Managed without encountering errors, to later upload the apps to Qlik Cloud.

To access the full documentation for the Qlik Cloud function, see GetSysAttr - script and chart function.

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 – please let us know!