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

[Daniele_Purrone]

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.

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. 
   
   
   

   
   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 

[john_oll]

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

[Daniele_Purrone]

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]

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).