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

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
henriheino
Partner - Contributor
Partner - Contributor

QDF wont work in subfolders correctly

Hi,

I have created new QDF envirnment to use in Qlikview, but for some reason my QV app won't find other containers if it is located in subfolder. For example my QDF might look like this 4.test/1. Testi and 4.Test/2.Testi and if I call 2.Testi in container 1.Testi using CALL LoadContainerGlobalVariables it gives base path missing. If I create new container right in Root (5.Test) I can call other containers and it works just fine. I have tried creating new QDF and same happens in there. Also container maps in all folders are correct and updating if I do something. Below is image of my QDF if that helps explaining what I mean.

qdf.PNG

 

Br,

Henri

 

Labels (1)
3 Replies
Vegar
MVP
MVP

It should not be hard to reference to a sub folder container using the qdf. Make sure that it is defined correctly in your QDF Deploy Tool.

Vegar_0-1601360362831.png

Then in the script make sure to initiate the QDF and call the LCGV using the Container Prefix. Take a look at the simple script below.

//Simple initiation of QDF
$(Include=..\initlink.qvs);

//Get the global variables of 4.Test\2.Testi. The prefix is set to 'Testi2'
Call LCGV('Testi2')

 

With this script above put  inside an application in the 4.Test\1.Testi container I am able to get this output.

Vegar_1-1601360578992.png

 

I hope this answer can be of help.

henriheino
Partner - Contributor
Partner - Contributor
Author

Hi,

My Deploy Tool looks exactly same as yours and I am using same script in app but still get "QDF Warning, vG.Testi2BasePath missing'" Also app in 4.Test/1.Testi foldet won't find shared paths but app in 5.Test folder finds them.

qdf2.PNG

 

 

qdf3.PNG

Br,

Henri

Magnus_Berg
Employee
Employee

Looks like it should work? Could you start from scratch using deploy tool and only adding" 4.Test\1.Testi" with the prefix "testi2" and see if this works, also validate the physical container exists in the location 4.Test\1.Testi . It might be some bug regards of all the container names that are almost similar? So great to test if it works without these. thx