Skip to Content
avatar image
Former Member

need to understand pros and cons of measures in Universe vs. Reports

I modified a WebI report that had two measures selected from the Universe:

- count(COURSES_ID)


As a result, there were two queries created, but the only difference was one had the COUNT and one had the SUM. this seemed to me to be overly complicated and added an extra layer of effort. Everything else in the query was the same.

So I ended up removing the measures from the report, then just did the calculation in the report, and so I ended up with a cleaner report, imo, with these

Count([Course Nbr])

Sum([Cred Hrs])

So was just wondering what are the considerations for each. We don't have much data so the number of rows returned isn't a consideration.

But I am nine months into this and trying to understand the pros and cons, how WebI thinks, etc.

Measures.png (32.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Mar 29, 2016 at 03:41 PM


    When you create the Aggregated Measure within the Universe the SQL Query uses the Database aggregation by creating a Group By clause. It bring MUCH less records before WebI starts creating the report.

    When you create the Aggregation at WebI level, you will get ALL the records from the Database NOT Aggregated.

    You always want to push the Aggregation to the Database, at the Universe level.

    You do have the option at the Universe Query Option to NOT create separate query per measure, see below



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Andreas J.A. Schneider


      excellent, thank you. Definitively the one statement makes more sense in this particular situation, but I realize there are pro's and con's to the Multiple Path option.