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

Announcements
Week 2: Presenting "Automate Sucess" and "Integration for Innovation" - WATCH NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
André
Contributor III
Contributor III

Why is the 'Open File' block deemed third party?

I am using the 'Open File' block to pull a file from an app's content library (via HTTP), and automations is deeming this a third-party block?

I've tried with the Raw API Request block using
apps/{APP_ID}/media/files/{FILENAME}.png
as the path, but it returns nothing. I'm assuming because per the API docs, it's expecting the --o tag, which I can't add in the block?

Is there a better way to do this?
Maybe a dev request to have 'Qlik Cloud Services' added to the connector options in the Open File block?

Labels (3)
1 Solution

Accepted Solutions
Shai_E
Support
Support

Hi @André 

You have the "Get Analytics App Media File" from the Qlik Cloud Services connector.

Which gets the content of that file, it looks to have the same endpoint you mentioned.

 

 

View solution in original post

4 Replies
Shai_E
Support
Support

Hi @André 

I think it makes sense that the Open File block is a third party block, why?
Because it makes use of several cloud storages, so i assume for example if you choose Dropbox as the connector for Open File it makes use of Dropbox API endpoints, ie third party API.

 

 

 

 
André
Contributor III
Contributor III
Author

I appreciate your thoughts and input Shai, but unfortunately they don’t quite resolve the issue I’m facing.

Shai_E
Support
Support

Hi @André 

You have the "Get Analytics App Media File" from the Qlik Cloud Services connector.

Which gets the content of that file, it looks to have the same endpoint you mentioned.

 

 
André
Contributor III
Contributor III
Author

Absolutely perfect, I didn't even realise these existed! Thank you! 😊