Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Accepted Solutions
Great question.
In SaaS everything would be done via a Connection. So your first step would be to create a Connection to the Azure file location where your files are stored, or will be stored. Notice the name I gave my pretend Azure storage connection.
Now when I want to write a QVD out I need to use the that connectors name in my statement.
Store MyTable into [lib://MyAzureStorageLocation/MyTable.qvd] (qvd);
That statement assumes that "MyAzureStorageLocation" Connection, is in the same Space that I'm running my code. But it doesn't have to be. Perhaps I have a Space called StorageConnections that retains all of the connectors to my various storage systems. Then in my code I need to adjust the syntax slightly to indicate that space.
Store MyTable into [lib://StorageConnections:MyAzureStorageLocation/MyTable.qvd] (qvd);
Loading would require the same concepts.
MyTable:
Load *
from [lib://StorageConnections:MyAzureStorageLocation/MyTable.qvd] (qvd);
Hopefully, this helps you get cranking writing and reading QVD's in our SaaS environment. SPACES is the big thing to think about. Remember without the preceding name and :, Qlik Sense will look for connections in the current space. Just like the Connections themselves are only shown from the Space the application is in unless you click the down arrow above the list of connections to choose the space to see the connections for.
Great question.
In SaaS everything would be done via a Connection. So your first step would be to create a Connection to the Azure file location where your files are stored, or will be stored. Notice the name I gave my pretend Azure storage connection.
Now when I want to write a QVD out I need to use the that connectors name in my statement.
Store MyTable into [lib://MyAzureStorageLocation/MyTable.qvd] (qvd);
That statement assumes that "MyAzureStorageLocation" Connection, is in the same Space that I'm running my code. But it doesn't have to be. Perhaps I have a Space called StorageConnections that retains all of the connectors to my various storage systems. Then in my code I need to adjust the syntax slightly to indicate that space.
Store MyTable into [lib://StorageConnections:MyAzureStorageLocation/MyTable.qvd] (qvd);
Loading would require the same concepts.
MyTable:
Load *
from [lib://StorageConnections:MyAzureStorageLocation/MyTable.qvd] (qvd);
Hopefully, this helps you get cranking writing and reading QVD's in our SaaS environment. SPACES is the big thing to think about. Remember without the preceding name and :, Qlik Sense will look for connections in the current space. Just like the Connections themselves are only shown from the Space the application is in unless you click the down arrow above the list of connections to choose the space to see the connections for.
