Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am able to create Data Files in Qlik Cloud using the Platform Ops connector, for example using the "Create Data File in Space" block. Ideally, I would want to use the Cloud Services connector as it does not require an OAuth connection. However, I only see blocks for listing & deleting data files in this connector - no blocks to create as are available in the Platform Ops connector.
Does anyone know if writing is not possible using the Cloud Services connector or if the right block has just not been added yet?
Historically the connectors were designed for different use cases, but we've recently made an agreement to bring them more into alignment.
I'll make a note of this particular gap, we'll take it into consideration.
Hi @tolange,
What about those blocks? The problem is, they only support 100mb:
I'm not sure about your scenario but you could also set dynamically Load Scripts on Qlik Sense Applications to create Data Files.
Regards,
Mark Costa
Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hi Mark, thanks! The temp content service is useful for interacting with externally stored files and quickly get them into Qlik.
My use case is a little different. I want to for example query some Qlik endpoints, compile a list of reloads or users for example, or get some straight table from an app - and then store this into a file right inside Qlik Cloud. With the platform ops blocks I can do so by creating a base64 string of my desired file and then create it using the "Create Data File in Space" block. Such a block is not available in the Cloud Services block as far as I see.
Now, via the temp content service, the file would first need to exist and be open - so I would need to create it on the fly. So either "Open File" would let me add a base64 string instead of an existing file (just opening a file already stored in Qlik would also be beneficial) or the "Upload File To Temporary Content" would allow for base64 strings instead of existing opened files as input.
You are right in that I may do similar operations via load script but I would like to explore what's possible via automations as for example API calls are much easier to handle in them compared to load scripts.
Best regards,
Tom
I don't see another way besides the Qlik Platform Operations. Is creating an OAuth client a big inconvenient?
The funny thing is, why we have connector on Qlik Platform Operations and not on Qlik Cloud Services?
Regards,
Mark Costa
Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Platform Operations blocks are fine for platform management purposes, i.e. for users with elevated access, but for "normal" developers and creating best practice guides for them, I would rather go with Cloud Services blocks as those do not require any additional configuration and are scoped to the individual user by default.
Regarding why the functionality to write data files does not seem to be there in the Cloud Services - that's exactly what I was also wondering.
Historically the connectors were designed for different use cases, but we've recently made an agreement to bring them more into alignment.
I'll make a note of this particular gap, we'll take it into consideration.