topic Re: Not able to use PreDefined Environment Variable in Qlik Compose

Not able to use PreDefined Environment Variable

aj96 — Fri, 14 Mar 2025 20:49:07 GMT

When I'm trying to use PreDefined variable I'm getting the following error

SYS-E-ERRMSG, User-defined variables are not set, some variables could not be replaced in the following string $$${database.Data Warehouse.datawarehouseSchema}.
SYS,GENERAL_EXCEPTION,User-defined variables are not set, some variables could not be replaced in the following string $$${database.Data Warehouse.datawarehouseSchema}

I'm using SQL Server db. Also I tried used custom variables with which I had no issues.

Re: Not able to use PreDefined Environment Variable

Steve_Nguyen — Wed, 13 Apr 2022 11:31:51 GMT

@aj96

more information would help others to understand the issue.

where are you using the variable ?

what are you trying to do?

Re: Not able to use PreDefined Environment Variable

aj96 — Wed, 13 Apr 2022 11:49:58 GMT

@Steve_Nguyen

I was trying to use in customETL. wanted to use the variable there in the query.

Re: Not able to use PreDefined Environment Variable

shashi_holla — Thu, 14 Apr 2022 16:26:06 GMT

Hi @aj96

Please confirm the Compose version you are on. Based on the 2021.08 Qlik Compose user guide, usage of predefined variables is supported sp03 onwards i.e. sub-version 250 or later.

https://help.qlik.com/en-US/compose/August2021/Content/ComposeDWDL/Main/DW/Projects/Variables_templates.htm

Thank you,

Re: Not able to use PreDefined Environment Variable

aj96 — Thu, 14 Apr 2022 17:15:56 GMT

@shashi_holla

sub version is 569

The custom variables are working, it's just the the PreDefined Datawarehouse variables are not working.

Re: Not able to use PreDefined Environment Variable

shashi_holla — Thu, 14 Apr 2022 17:56:11 GMT

@aj96

Looks like you are on latest patch version of 2021.08 and in the user guide link I shared in my last update, it mentions and we could be running into this constraint.

Exported CSV objects that are associated with predefined environment variables (for example, a mapping database and schema) cannot contain user-defined environment variables.

For instance, this is not allowed:

Name Landing Zone Database Schema

MyMapping $$${MyDatabase} $$${MySchema}

See also: Migrating objects as CSV files.

Name	Landing Zone Database	Schema
MyMapping	$$${MyDatabase}	$$${MySchema}

In any case if you could open a support case we can check it in detail and provide the right solution/answer.

Thank you,