On Measure 4 Grand Total level, you have your choices of aggregation type, such as Average, based on the values above it in the same column. There is no way to perform a calculation based on other columns in the Grand Total level. For your second question, I'm not completely following. Your spreadsheet shows 2 case…

If you are using Classic Dashboards, expand on what others have said about setting a presentation variable in the dashboard prompt. This is the starting point of the idea. Create a standard prompt that the users will see, using it to filter your data. Create a second prompt control which will use that same column and set X…

Without knowing a lot of detail of your situation, you might take a look at MAX_EXPANDED_SUBQUERY_PREDICATES. There is a similar post about this same topic, but for OBIEE. Also, you can review:

I agree with @Gianni Ceresa and would add that it is good to experiment with the reports catalog manager provides. Try different options on a small catalog folder where you know the underlying content and check for your dependent objects appearing in the output. Some objects may not be listed in the report you run, so it…

As a tip for the future, it would be easier for us to review your code if it were in a text, not a photograph of a computer screen. I can only guess based on reviewing line by line (img-20240306-194015.jpg) you are trying to get the value 15 in column c1, which you were able to do by commenting out the tables W_XACT_TYPE_D…

One benefit to using the RPD is you can set the display column to have a different column to use for sorting. This feature is helpful if you have a date dimension that is a string/character, rather than an actual date data type. The custom sorting will be automatic when the field is used and you don't need to bring the…

Yes this essentially correct, if those MONTH values are literally 'JAN' , 'FEB', etc. A caveat, is '1' is a string, like '12', and you don't want a sort order of '1', '12', '2', '3', ... so you will want to use number values, not strings OR use '01', '02', .., '12' as chars. There is much more on this topic I could say,…

Jean-Pierre, Your example SQL looks like it is using a dimension table (dim_date), but your performance issue refers to scenarios when using a Fact table. It would be useful to see the SQL where the performance is bad. If the SQL provided is such an example, I would start off with running Explain Plan on the SQL statement.…

I would look at Manage Sessions and check the physical SQL generated. Use a simple report without other calcs going on, to make it easier to review the SQL. Check the aggregation - is it SUM? Is there anything else going on in the physical SQL which could be mapped to the model logic that might explain the unexpected…

Even in your more complex example, I feel the solution is in grouping values that you want to aggregate, if your intent is to include the values corresponding to those rows (via a sum, for example), but not display the labels. You would group them into a specified value. This grouping could be done in the UI via a…

It looks like what you want is to group 12/02 and 12/03 into a a single displayed label and sum up their values, which is then incorporated into the running sum. You would do this by creating a calculated date field with a case statement. The new date field's formula would be something like: case Date when 12/02 then 12/03…