8 Replies Latest reply: Apr 4, 2012 8:22 AM by Jason Michaelides

# summing/totals after crosstable import

little example

• ###### summing/totals after crosstable import

If your "Total Time" is a solid number ( so not a calculation) you should show it as a dimension and not as an expression. This way it will show 100 for every row.

• ###### summing/totals after crosstable import

And get rit of your Downtime  Types if you want to see them add up (23 for machine A)

• ###### summing/totals after crosstable import

thanks Dennis,

I cannot get rid of the different types.

It's also hard to put the totals as a number, since I need to do calculations on it :

 Machine Total Time Dowtime Uptime % A 100 23 77 77 B 100 37 63 63 C 100 26 74 74

etc

Maybe I have to load the table in 2 times, one time not as crosstable, and without the downtime types, and then a next time only the downtime types as crosstable, and create a common unique key to link them up?

But this looks like ambiguous programming? I think there must be easier solutions than this.

• ###### summing/totals after crosstable import

I mean get rit of the Downtime Types as a dimension in your charts.

Then you will get 23 right?

Try this create a Strait Table:

Dimension :      Machine

Expressions:           AVG(TotalTime)

SUM(DownTime)

Column(1) - Column(2)

Column(3)/ Column(1) *100

Let me know if this is what you are looking for

Dennis.

• ###### Re: summing/totals after crosstable import

Dennis just beat me to it!  See attached

• ###### summing/totals after crosstable import

You could use Avg([Total Time]) instead of Sum([Total Time])

• ###### summing/totals after crosstable import

thanks Jason,

but how do I end up (Total Time) - Downtime, to calculate Uptime?

Uptime = avg(total time) - sum(downtime) doesn't work correctly...

• ###### summing/totals after crosstable import

Hi,

Why don't you just make another table of Machine and TotalTime.

So 2 tables can be

table1:

Machine,

TotalTime

table2:

Machine,

DowntimeTypes

DownTime

This should work for most of the scenarios.

But yes, If you have huge data Size then you may also think rather then making two tables using flags and set analysis on the same cross table only.

..

Ashutosh