topic Re: Why is the 'Open File' block deemed third party? in Qlik Automate

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

André — Thu, 24 Apr 2025 01:28:00 GMT

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?

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

Shai_E — Thu, 24 Apr 2025 10:02:28 GMT

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.

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

André — Fri, 25 Apr 2025 21:26:41 GMT

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

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

Shai_E — Mon, 28 Apr 2025 07:47:06 GMT

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.

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

André — Mon, 28 Apr 2025 20:21:33 GMT

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