Renaming QVD and Parquet files from semantic layer across environments

Feature Request: Improved Environment Handling and File Naming in Semantic Endpoints in TimeXtender (Classic)

In our current setup using Qlik Sense endpoints to generate QVD and/or Parquet files for Semantic Endpoints in TimeXtender (Classic), we have two environments (DEV and PROD), each designated to write files to different folders. Our directory structure looks like this:

QVDs
│
├── DEV
│   └── <QVD Files>
│
├── PROD
    └── <QVD Files>

Under each environment's folder (DEV and PROD), the QVD files should have the same name to facilitate switching between folders in Qlik Sense without requiring changes to QVD names in the script.

Problem

Currently, we use the Postfix Option (_DEV and _PROD) for each environment. This setup forces Qlik Sense scripts to connect using:

LIB CONNECT TO 'MDW';

instead of:

LIB CONNECT TO 'MDW_DEV';

and

LIB CONNECT TO 'MDW_PROD';

This ensures that data is loaded from the respective database environments (DEV and PROD).

An unintended consequence of this setup is that every QVD file is saved with the environment postfix:

<QVD_Folder>\<QVD Name>_DEV.qvd
<QVD_Folder>\<QVD Name>_PROD.qvd

To make the scripts work, we must manually find and replace _DEV.qvd with .qvd and _PROD.qvd with .qvd, so the files are named equally across both environments.

Feature Request

1. Environment-Specific Connections: We request the addition of an option to change only the connection name in the Qlik app script without altering the file name postfix of the QVDs. This would allow:

LIB CONNECT TO 'MDW_DEV';

while keeping the QVD filenames consistent.

2. Parquet File Generation: We also request an option to enable automatic Parquet file generation. Currently, we manually change:

_DEV.qvd];

to:

.parquet] (parquet);

This feature would simplify our workflow by directly supporting Parquet file generation.

Benefits

Implementing these features would:

• Eliminate manual file renaming processes
• Streamline the deployment of Qlik Sense across different environments
• Facilitate efficient data management with automatic Parquet file support

We believe these features will greatly enhance usability and maintainability in TimeXtender.

Thank you for considering our request.