Yes, it is possible. If you are reloading in QlikView Server you need to ensure that the Concurrent Reloads option is set to greater than one to allow this. You also need to be careful to ensure that you don’t have two QVW files reloading at the same time which read and write the same files.

Hi Andy,

Thanks for your comment. The menu does not slide out (that would require macros and not be pleasant to build), rather it simply appears over the top of other objects. To achieve this a number of objects are layered on top of each other with the show/hide condition set. This is relatively simply, but you do need to ensure you set explicit layer values on everything, so that objects appear in the right order.

Hope that helps.

This is a great dashboard. I’m really interested in how your slide out Ajax selection menu works. Could you explain how it was implemented?

Hi Nair,

Being a ‘proper’ developer, in any language is a definite plus point – as you need to take care to get your semi-colons and brackets in all the right places. Getting started is relatively quick and simple, but really mastering the product takes time. Getting some kind of training in will certainly help speed up the process.

I have done a couple of previous blog posts that you may find interesting:
What Makes A QlikView Developer
How Do I Learn QlikView

Good luck picking up the product, it can do amazing things in the right hands.

thanks for sharing your experience, Steve! good job again! I know it is not easy to build a dashboard like this in QV and this there it helps to be an expert like yourself! :)

Hi Boris, Thanks for your comment, glad you like the UI.

I would not like to say how long the UI took to build, but it certainly took more time than on some other projects delivering as much data. As it is a dashboard that is being taken out and pitched as an OEM offering it had to be top notch. Simple things like alignment of buttons added a little to the effort, and overlapping object were sometimes a pain – but worth it. Generally though I am a big advocate of making your QlikView dashboard look like a QlikView dashboard, as going with the natural UI does make things simpler and quicker.

The Supporting Data link just fires the user off to another sheet with a number of straight tables showing row level information. There is a vertical scroll on this tab, as each table is shown one above another. It’s not likely to be used by many users (in fact I think the link has a show condition on it) but is useful during development.

I inherited the data model and it was very much based around a link table. This made some things a bit problematic. After taking the project on I concatenated more into the main fact table (as is generally my preference) but there is still a link table for some entities.