Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
WEBINAR June 25, 2025: Build on Apache Iceberg with Qlik Open Lakehouse - REGISTER TODAY

Qlik Cloud: changing a dataset name does not change the source's name

0% helpful (0/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Daniele_Purrone
Support
Support

Qlik Cloud: changing a dataset name does not change the source's name

Last Update:

Oct 17, 2023 2:56:41 AM

Updated By:

Sonja_Bauernfeind

Created date:

Oct 16, 2023 9:23:13 AM

When changing the name of a dataset, the source name still stays the same. This can be seen by uploading a  “firstname.qvd" and renaming it to “secondname.qvd”. 

The dataset's detail will show "firstname.qvd" as the source.

source name.png


As a consequence:

  1. you can have several datasets with the same name, but different sourcenames.
  2. the data load editor always refers to the source name (“firstname”), not the data set name. 

    select file.png


    Trying to load  “FROM [lib://DataFiles/secondname.qvd]” will produce a "(Connector error: File not found)" error.

 

Resolution

This is not a defect, it's how the product is designed.

A dataset represents a data resource with its properties such as name. The value of that is that you are able to use more user-friendly names of datasets without having to change the source names, which can be useful when the dataset is pointing to a database table for instance.

In the future, there is a plan to add the possibility of calling the name of the datasets in the script. 

 

Environment

Qlik Cloud 

 

Labels (2)
Comments
john_oll
Partner - Creator
Partner - Creator

WTF. Why "implement" this when it has no effect?

Daniele_Purrone
Support
Support

Hi @john_oll , this is to have a friendly name... which can be useful to easily identify datasets without modifying the original file name (which might break existing processes/reloads and more).
If you have any idea on how to improve this, make sure to suggest it to our product team.

john_oll
Partner - Creator
Partner - Creator

It would at least be helpful if both the "fake name" and file name are displayed, so you have a clue that it is just a fake label and you did not actually rename the file (AS THE NAME OF THE FEATURE IMPLIES).

DuncanBlaineVRL
Contributor
Contributor

Just discovered this feature the hard way.
I renamed a QVD to save it as a backup (via the Catalog view) so that an new version of the QVD would be saved when I ran an amended gen script. Instead it overwrote the original and caused a lot of confusion.  
A friendly name is a nice idea, but in my opinion, this feature needs better messaging.
For example, a column in the Catalog showing 'Source Name' and 'Friendly Name';
and in the Edit Dataset window there is room for a clear explanation and could display the Source Name as well as editable Friendly Name. Currently it just has an editable 'Name' field. 

Version history
Last update:
‎2023-10-17 02:56 AM
Updated by: