Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello
here in the company I work for we are using QDF with Qlik sense.
We had one home container in which applications' containers reside.
Now we are thinking of having a second Home cotainer in which we will create containers for new applications that are not relevant to the original home container.
Is this possible?
is it possible to allow some exceptional applications in the original home container to connect to containers in the new home container to consume some QVD files or reference QVS files
if all is feasible, please advise on how to accomplish this thoroughly
Hello ,
Yes, you can 'declare' home containers from another root container with DCGV function (DynamicContainerGlobalVariables)
for example :
// Declare 'Middleware' container pointing to'lib://QDF_ADMIN/99.Shared_Folders'
call DCGV('lib://QDF_ADMIN/99.Shared_Folders','', 'Middleware');
// Load persistent logger script from 'Middleware container
$(include=$(vG.MiddlewareCustomPath)\PersistentLogger.qvs);
Hi
Can you please supply some details? Are you on Prem or Saas?
By home container what do you mean?
If on Saas the views are customisable by the end user, so i am confident you would be able to achieve what you want.
We are using on-prem Qlik sense
Home container is the folder in which applications' containers reside
for example:
the QDF folder here is the home or root container
we need to create a new root container named QDF_FIN
Hello ,
Yes, you can 'declare' home containers from another root container with DCGV function (DynamicContainerGlobalVariables)
for example :
// Declare 'Middleware' container pointing to'lib://QDF_ADMIN/99.Shared_Folders'
call DCGV('lib://QDF_ADMIN/99.Shared_Folders','', 'Middleware');
// Load persistent logger script from 'Middleware container
$(include=$(vG.MiddlewareCustomPath)\PersistentLogger.qvs);