Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
Don't do the case statement with your ago() ... just base it on the logical column that already evaluates the case ... also since you are using logical columns on logical columns, @Christian Berg's comment of " Probably something like derived calc (post-agg) versus physical mapping calc (pre-agg)" is starting to take form…
-
Store the user_ID, warehouse_ID in a DB table and model it on the physical join ... then based on the user the join will limit the data coming back. Based on the users groups in AD you can modify the refresh of the security table(s) to write the combination rows you need. Doing this in the database will perform better than…
-
This is why developing off "development objects" isn't ideal ... hard to fit the windows and the roof when the foundation is shifting ...
-
Invalid path ([object NodeList]) - must start with a slash - OBIEE 24/7 | Oracle Business Intelligence Chrome doesn't always behave ... after all it's a browser like the rest!
-
Yes you can ... steer away from trying to mimic functionality from tool to tool .. you can use the text object on a dashboard and put the HTML for the link in there ...
-
Since a company is IN an industry, why not have a logical hierarchy? Then it's a matter of a level-based measure to show the total for the industry and you can add the value of showing not only raw measures, but % contribution or comparison values as well. You could also just add the volume field twice on the report and…
-
The SampleApp (v506) has the examples you are looking for ... it has dynamic and fixed ... if you don't have the VM, I can fire mine up after work today and post the details (RPD) from these ..
-
Correct ... my mistake ... wasn't reading it right ... needs the time hierarchy level not SQL_TSI ... @Christian Berg - I ain't perfect! lol ... good catch!
-
Are your individual prompts set to Page level scope?
-
Your problem desciption is missing any and all references to a SQL TSI_### interval ... BI server knows it needs to go back 1 step, but on WHICH LEVEL?
-
You have to remove the default action (drill) on the columns that are interfering...
-
if you want all the columns to go to the other report then you have to set them all to behave the same way ... my advice is have ONE column that is used to drive the action - you can have multiple actions: Country -> State Report -> City Report -> Postal Report -> Additional Country Details
-
you start with Country and want to click and navigate to another analysis that has country details or perhaps state details, and you don't want to just keep drilling in that one report? ... then open the column properties of Country and change the default interaction to Navigate to BI Content (can do it on header/value…
-
In your screen shot (on the left of EM), click the Diagnostics tab and have a look at the log files and messages ... your answer is there.
-
drop a column on you report and change the formula to: (SUM(InsideSales) / SUM(Sales))*100 taken from: OBIEE - Aggregation rules in Logical SQL with the GROUP BY and BY clause [Gerardnico]
-
Also ... take a look here for tips on how to model where/when not every dimension joins to every fact (and vise versa)... What To Do When OBIEE Fact Tables Do Not Join to All Dimension Tables?
-
You have done what is described in this blog? http://gerardnico.com/wiki/dat/obiee/dimension_measure
-
If you need counts by/over time, then you'll need to build a fact table that records the counts that way ... so it's an intersection of store key and time key ... facts can only be correlated across conformed dimensions. For now .. make sure you have the content levels set correctly ... you might need to set the rest on…
-
The certification matrix (http://www.oracle.com/technetwork/middleware/bi/bi-11gr1certmatrix-ps6-1928219.xls) says ... ALL11.1.1.7.0+Microsoft Windows x64 (64-bit)2012 (Does NOT include 2012 R2)
-
create a new logical table as a fact with the dimensional table as the source ... join it to your dimension (set it's content level to the base of the dimensional hierarchy) and aggregate the PK (count distinct) and name it Store Count ... now you can relate the sales facts with the count facts through the conformed…