Analytics Resources: Insights, Best Practices,

Case Studies and More

close
Written by Shwetank Sheel
on January 22, 2014

With the move from OBIEE 10 to OBIEE 11, the default behavior when editing a report changed. While earlier you would automatically be taken to the criteria view, with OBIEE 11 you are taken by default to the results view. This is can be a problem for 2 reasons:

  1. It adds an additional step to edit the report (most of the time you are editing the report to change the criteria or the filters).
  2. In cases where reports are large, the results view automatically triggers a query to get the results. You may not always want this and in heavy usage environments, you may not want to add this load to the system.

With 11.1.1.6.0, there is a way to change this in the front end. When logged in, click on the My Account tab in the top right corner and make your selection in the Analysis Editor dropdown.

(Thanks to Ajay Sreedharan for showing me this)

Default_Behaviour

The front end does not have any option to change this on a global basis. If you want to change this on a global basis, you will need to change this property in the dashboardeditor.js file found in /app/res/b_mozilla/dashboards folder.

The steps involved in doing this are:

  1. Open dashboardeditor.js file.
  2. Search for the function "DUIModifyReport".
  3. Inside the function you will find that
    ***"&Action=results&Path="****
  4. Change results to criteria. In other words, the changed code will look like
    ****"&Action=criteria&Path="*****
  5. Re-deploy the code and bounce the services.

Do note, this will affect for entire dashboard, and for ALL users.

Also, if you don't want to redeploy the code and bounce the servers, you can also make these changes in the dashboardeditor.js file in the <MIDDLEWARE_HOME>/user_projects/domains/BIfoundation/servers/bi_server1/tmp/_WL_user/analytics_11.1.1/<ONE_OF_THE_RANDOM_FOLDERS>/war/res/b_mozilla/dashboards and just restart the services. After restarting, do a clear cache and refresh on your browser.

As with any changes, I would recommend thorough testing after the JS change.

You may also like:

OBIEE 12c Cloud Analytics

Join us at the Modern Finance Experience

Join us on Wednesday 23-Mar at the Marina Bay Sands for the Modern Finance Experience event organized by Oracle. You wil...

OBIEE 12c

OBIEE 12c Baseline Validation Tool

In the real world, the migration between two OBIEE environments is really take time .The last time we did this for a cus...

OBIEE 12c

Steps to upgrade usage tracking when upgrading from OBIEE 11.1.7.1 to OBIEE 11.1.1.9

Recently usage tracking stopped working for one of my clients after upgrading to OBIEE 11.1.1.9 with the NQSERVER log sh...