Can chart totals be used to build other sheet objects

[kdmarkee]

I have a challenging xls file I am trying to duplicate using QlikView that is driven my tons of variables that feed into calculations, and then those calculated results are used to feed other calculations still, and so on and so on.  I've attached a very simplistic qvw of what I'm trying to accomplish and am hoping someone can offer some advice or solution, assuming it is possible what I want to do.  The qvw describes it in detail, but generally speaking I am needing a way to pull chart TOTALS (that have been built from a "popcorn trail" of input variables and expression column labels) from 2 separate straight charts that have no relationship to each other in the data model.  Then, with those totals, do some math on them, and include those pieces of info in a 3rd straight/bar chart.  I appreciate your help, thanks.

[marcus_sommer · Accepted solution]

No object could access the calculation-results from another object. This meant all necessary (pre) calculations needs to be done within a single object.

If ever possible to transfer a (complex) solution from a table-calculation like Excel to a database-oriented tool like Qlik (I consider the qlik datamodel like a database in the view of your task) in a nearly 1:1 way than it will be quite probably extremely expensive and very ugly because the tools are quite different and each one needs to be used in a special way to benefit from their strengths.

Therefore I think you need to develop another way of implementing it into Qlik. One might be to create a cartesian product between your tables and to pre-calculate the biggest parts within the script and your variables might be replacable by normal selections over integrated or associated fields or maybe loosen tables ...

- Marcus

[kdmarkee]

Thanks for the feedback.  My gut told me that to do what Excel can do in a tool like Qlik could prove to be tricky (maybe even impossible 1:1) because you are right, relationships need to exist in Qlik.  I'll have to go back to the business and see how we can modify the requirements so that it is more Qlik friendly.