decrease application opening time

[Anonymous]

my application take more than 3 minutes open . even though the I have calculated the dimension and expression the script level

For i=1 to  NoOfRows('MasterData')

LET vRawDim$(i)= SubField(vRawDim, '|', $(i)) ;
LET vMasterDim$(i)= SubField(SubField(vMasterDim, '|', $(i)),'.',2);
LET vFlag$(i)= SubField(vFlagTemp, '|', $(i)) ;
NEXT

[Anil_Babu_Samineni]

For me it's taking as Maximum 10-15 seconds. Aren't you? Better if you increase specification over the file situated AMI

[Anonymous]

I am asking about main application with 50 MB data attached file is the sample application Is there is something I missed or there is any way to optimize ,right now I am using document analyser to analyse the unused fields

[Anil_Babu_Samineni]

Sounds well, You said, you are using Document Analyzer does this useful to you. I know DA has enough satisfies to troubleshoot. If not, May be Governance Dashboard for your case. This may helps you lot because we can track and initiate to indexing files. And If 50MB takes long time could be problem in Data model. And how about 3-Tier Architecture ??

These are the links i followed normally

Best practices for data modeling ‒ QlikView

10 Best Practices in QlikView Data Modeling

https://www.quickintelligence.co.uk/start-your-qlikview-project-the-right-way/

https://www.quickintelligence.co.uk/perfect-your-qlikview-data-model/

[balabhaskarqlik]

Follow some of the Processes.

Always have a 3 tier Architecture to build your QlikView Applications.

1 Fetch data from DB with no or some transformations

2 Transformations in script level

3 Optimized qvd loads for better performance

4 Partial reload

5 Perfect you Data Model.

[PrashantSangle]

If I understand properly you have already maintain complicated expression and dimension at script level

So In front end before closing app made some selections and save application.

Regards

[prieper]

Suggest to use a trigger with "On Open" functionality, which restricts your data in a useful way.

Saving with reduced data may sometimes fail, when you have access-restrictions on fields.

Else it may help to point (also via trigger) to a sheet, which does not have so complicated calculations. There the users may do selections and proceed then to the dashboard.

Peter