Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
Adfc_NZ
Contributor III
Contributor III

Ownership of a File not changing after reload

Hi,

So I have a strange issue I want to see if someone can shed some light as to what might be happening.

I have an app (in a Shared space) owned by user 'A'. That same user is the owner of the app's Reload Schedule.

That app generates a QVD file in another space (Managed).

That file is currently owned by user 'B'.

Now, I know I can use the Admin tools and change the ownership of the file, that's not the issue. 

The issue I have is: shouldn't the reloading of the app, which triggers the 'Store QVD', also change the ownership of the file?

FYI I tested using my Personal Space by creating a simple app with a Inline load and a Store, to store the resulting table in a QVD in a Managed space. Created a Schedule to reload the app. Both app and reload are then owned by me. I reloaded the app. Checked the file, was owned by me. Using Admin console, changed the ownership to another user. Reloaded the app again, file was back under my ownership?

What am I missing then, why isn't the "real case" changing the ownership of the file? Any ideas?

Thank you.

Labels (1)
  • SaaS

2 Replies
Eduardo_Monteiro
Partner - Creator III
Partner - Creator III

Hello @Adfc_NZ 

The file ownership is set at the moment it is created. 

What you are experiencing is the file being updated with new information, and this will not affect ownership.

 

I'm assuming you run the store statement for the first time by user B. Now the reloads are being performed by user A. 

Eduardo Monteiro - Senior Support Engineer @ IPC Global
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

Adfc_NZ
Contributor III
Contributor III
Author

Hi Eduardo,

Not trying to antagonise you 🙂 but when I tested in my personal space, it did change the file's ownership. But that doesn't happen in the "real case", so that's why I am confused.

Any idea why we'd have these 2 different behaviours, and which one is the expected one?