help

[#1]

Hi All,

Will anyone share your experience of facing challenges while working with Qlikview development so far

Which is most difficult to achieve as per user requirements.

Regards,

Bob.

[oscar_ortiz]

Bob,

The question is a bit vague.  Can you get a bit more specific as to what you're looking for?

Thanks

Oscar

[#3]

I wanted to know most difficult challenges did you face so far to achieve by using qlikview according to the end user requirements.

To design the dashboard,all the time 100% not possible to achieve user requirements.Some times it may difficult.

did you face before those kind of situations.???

[#4]

Hi Babi,

When designing a dashboard try your best to keep it as broad as possible. If one was to start working on ALL the requirements of the business users, one'll get fatigue and tiresome and stress out. My best suggestion to you is to keep the dashboard as broad and general as possible. Provide as many list boxes and text objects as possible.

You can also check out the Qlik demos for further clarification. Qlik Demos: See QlikView in Action | Demo.Qlik.Com

Hope it helps,

AQ

[oscar_ortiz]

So as far as user requirements go if you have the data to support the user requirement then it should not be an issue with completing their requirement.

One of the issues is when the end user is trying to replace an existing report and they are stuck on having to see it exactly the way the old report was displaying, normally some sort of table based report.  Well, then you are not taking advantage of QlikView's strength in visualizations.

Another issue is when the requirements want to show too much information on a single sheet.  The sheet becomes too busy and may cause issues if too many active objects are being displayed at one time.

Hopefully, this is a good starting point for you.  Again if you have more specific questions please feel free to ask.

Thanks

Oscar

[Peter_Cammaert]

One of the most difficult challenges in building QV enterprise solutions for large data sets is that you can be sure that the data never matches what the customer thinks/says it contains. Surprises galore...