OBI Dashboard report differs from analysis based report

3713479

A Dashboard based report using the following filters is returning zero rows whereas the same report run as an analysis returns the expected results.

Customer # is present in report A

Customer # is NOT present in report B

The output should show most of the customers  from report A since report B represents a small subset of report A.

The Dashboard is using default date ranges whereas the analysis based report has the date ranges "hard coded" in a filter.

Any insights from the user community are appreciated.

Thank you !

Gianni Ceresa

In an analysis (not report, analysis) a filter if it isn't protected will be replaced by the values selected in a dashboard prompt if any.

Therefore your analysis is probably running with a very different filter. Add the "filter" view in the analysis and you will have a hint, look at the generated query and you will be 100% fixed on what is executed.

PS: have a look at , would be great if you could close old thread if they are solved (marking as required to help others with the same need easily identify helpful pieces).

3713479

Gianni

Thanks for your input...in this case, the analysis based reports and the Dashboard based reports are in separate catalogs.

Also, I created the analysis based reports earlier in the project and am trying to replicate the same functionality from the Dashboard.

My plan is to ask the Administrator to provide the query log for the step that is returning zero rows.

Also, I am thinking that there is some issue with the scope of the date prompts, either the page level scope is not being enforced or the dates are being bypassed.

Gianni Ceresa

Let's take a step back:
Are you talking about OBIEE Answers objects? Analysis, dashboard prompts and dashboards?

Or are you talking about BI Publisher reports?

[Deleted User]

I'm with Gianni on this one. Take a step back and look at what you are doing, how you are doing it and the why you are doing it in the way you are doing it.

OBI and BI Publisher are two completely distinct products even though BIP comes bundled together with OBIEE. BIP is used for pixel-perfect reporting, not fully dynamic dashboarding and ad-hoc analytics.

3713479

Gianni & Christian

Thanks for your input.

I am not using BI Publisher.

I am  converting reports, each of which were created as an analysis,  to run from the dashboard with prompts for date ranges so that the dates are not hard coded within the analysis filters.

I am at a loss to explain why the dashboard functionality is returning zero rows. 

I noticed that the dashboard reports return the expected results when there is a single report filter.

When two report filters are present, the report is failing.

[Deleted User]

3713479 wrote:I am not using BI Publisher. I am converting reports, each of which were created as an analysis, 

That statement doesn't make any sense. A "report" is an object created by BI Publisher. An "analysis" is an object created by OBIEE Answers. Not quite sure what "converting reports which were created as analysis" would mean.

Gianni Ceresa

Ok, so the wording was a bit confusing and made us think you were doing something different.

If you want to keep control on what you analysis does when it's inserted in a dashboard, you need to control the possible behaviour of filters.

It's clear that a filter set as "is prompted" will take the values of the prompts, but you don't seem to have that, right? Because when looking at the analysis as standalone this filter is ignored, it is only applied when in the dashboard and a prompt is setting a value there.

This is a first thing to check.

Second step you can protect all the other filters, and start unprotecting them one by one till you run into the issue. This is a "poor" way to debug if you don't have direct access to the logs.

With access to the logs, both the logical SQL and the physical SQL you will be directly fixed on why you don't have results, and you will adapt your analysis as required.

There isn't much more which can be posted: you are the one having that RPD, that analysis, that dashboard and that server. Nobody else here has the same.

3713479

To clarify, each report is an analysis object created from OBIEE answers that I am attempting to migrate to the dashboard framework to avoid hard coding of date parameters.

As suggested,  I will ask the  DBA for both physical and logical SQL logs to assist in isolating the issue.

Thanks for your responses.

[Deleted User]

I will leave Gianni to this, but one last try:

3713479 wrote:To clarify, each report is an analysis object created from OBIEE answers

A "report" is not an analysis and an "analysis" is not a report, even if both display data. A chicken is not a horse and a horse is not a chicken, even if both are animals.

Please try to learn the correct terminologies and use the appropriately. You are creating problems by not being specific where there should be no problem at all.

3713479 wrote: I am attempting to migrate to the dashboard framework to avoid hard coding of date parameters.

You do not "migrate" anything to the dashboard. You just *use" analyses inside a dashboard. They are modular, re-usable objects. Like LEGO bricks.

3713479

Gianni

Your post regarding the logs has been helpful.

For five dashboard pages, I have defined all the date parameter prompts with "page level" scope.

When  dashboard page # 5 is launched, the analysis on that page is invoking predecessor analyses on other dashboard pages,  The problem is that an analysis on page # 1 is using the date prompts from page # 5 instead of the prompts defined for page # 1.

Therefore, my conclusion is that the page level scope attribute is not being enforced.

Any