store total values from a table chart into variables

[alec1982]

hi all,

I want to store the total values..(Sum Sales) showing on a table chart into variables, doable?

Best,

Alec

[petter]

Depends on what you mean by "storing". A variable can directly reference fields and a variable can contain an expression that could calculate the Sum Sales for you. But a variable can't directly reference an expression contained (hard coded) in an expression in a chart.

If you put the expression into a variable (expression-variable) and then use this variable directly in you expression in a chart then the calculation of the "expression-variable" could be done identically in both the chart and outside the chart. Just bear in mind that outside a chart and inside a chart is not totally similar because the dimensions of a chart filters/combines which elements that would take part in the calculation. That can be reproduced outside the chart anyway but not without additions to the "expression-variable".

[alec1982]

hi Petter,

I agree with you. What I am trying to do here is I am building the following scenario:

User goes in and makes few selections.. the total row on the table chart changes based on the user selections.

I need to store the resulted values in variables so I can use them next time the document reload.. (Building Montecarlo simulation)..

Best,

Alec

[petter]

Storing data back is not the most streamlined thing in QlikView. Actually it is not user-friendly at all. So there are several third-party solutions for that purpose and also QlikView extensions to do write-back. Have a look at QlikMarket.

I guess you want to have this deployed on a QlikView server so the users will go via AccessPoint to run the application?

You could roll you own approach. It is possible to make VBScript Macros that write to a CSV or XLS file server-side. Then this information could be read back on the next reload. Other approaches could also be used. QlikView Extensions that do write-back to a SQL database which you could include reading back in your load script.

Another approach could be to use Input Fields that are stored per user and persist on the server - not in a database table but in files that the server manage.

Variables could actually be persisted with bookmarks and these could be shared between users if you like.

[#5]

Hi alec

did you get result for storing the table row into variables.