Many a times it is required to open the OBIEE application again and again with the same user and password for some testing or development purpose. In that case you can use the Go Url parameters in the URL and save it in your favourites so that you can avoid repetitive entry of login credential.
Here is the example:
For accessing Answers:
For accessing Dashboards:
If you want to show static data in any rpd column then you can create a view in rpd as follows which can display static data for the given column.
And create a column ColumnName in the column tab.
Create a join with fact table and you can see the static data as follows.
Very simple but might be useful.
There are 2 ways to disable iBots.
1. Open the iBot from More products> Delivers and uncheck Set Schedule checkbox. This method can be used to disable one iBot at a time.
2. If you want to disable all the iBots at once then write a sql script to update NEXT_RUNTIME_TS column of S_NQ_JOB table as null.
UPDATE S_NQ_JOB SET NEXT_RUNTIME_TS = null ;
Commit;
This table holds all the iBots which are created and NEXT_RUNTIME_TS column holds the time when the iBot is supposed to run nexttime.
I will tell you the background for this blog. Some times you make the Dev, Test or any other db in sync with Prod. So this copies all the iBots which are created in Prod to other environments and users will get iBot results from other environment also. So inorder to disable this you can use the above step.
Making values in prompt column in sync with the report column.
Scenario: You have a dashboard with Prompt on Opty Status column.
And the report has columns like Opty Status, # of Opty.
Issue: Opty Status in prompt shows values more than the values which are shown in report.
Reason: For the Prompt column, single table comes into picture i.e W_OPTY_D whereas for Report, Fact table will also come into picture and which might drop few status based on the data populated in Fact.
Solution: Add a dummy column from fact in the where clause of Prompt sql which will force the query to bring Fact table also into the picture and hence the result would be in sync with the report column.
eg: SELECT “Opportunity”.”Opportunity Status” FROM “SubjectArea” where “- Fact – Opportunity”.”Row_Wid” >0
This is very simple tip but might be useful for beginners.
Many times we write case statement in columns and Prompts to populate a hard coded values.
Example:
Case when 1=0 Then Employee.Name else “Value1′ end
Here the first condition would be always false, so it will display the hardcoded value.
So basically we can use any dummy column in Then clause.
Now, what I would suggest is before giving any column name in Then clause, make sure it does not contain any outer joined table in the repository.
Generally while developing, we don’t see this but I am suggesting you based on my experience.
In my project I had similar case, where one of the prompt was using a dummy column which had 5 outer joined tables in the repository and just for fetching 2 hard coded values in the prompt it was taking around 20 minutes.
Once I changed the dummy column, the performance improved drastically.
|
31,273
|
Unique Visitors |
