Hi, New role created should be given access to the required report/dashboard as "OPEN". With Open access , no user will be able to create/modify any report but only read/consume it.

Yeah, but I have seen folks developing degenerate Dims on top of the same fact but with different Dim - Fact alias and try to treat it as Degenerate Dim. This leads to self join and hampers performance

Try the below approaches: 1. Avoid complex derived measures/attributes in BMM layer of BI RPD, rather try to use physical mappings for logical calculations. 2. De-generate Dimensions should be developed on top of the same fact alias with which join is established. 3. Avoid complex/cartesian joins as it affects performance.…

If an LTS is assigned priority as 0, this fact should definitely be hitting in the BI server query.. 0 means highest priority and if your joins with this 0 priority LTS are correctly linked with content levels set, this should definitely be working.

Welcome Please mark the answer as correct 

Check out: https://docs.oracle.com/cd/E23943_01/bi.1111/e10544/conditions.htm#BIEUG1205

Step 1: Create A new Condition on top of your analysis. The parameters defining your condition should be like XYZ Prompt values "is not null". Give a row count for the condition and save the condition. Step 2: Go back to your Dashboard for which you have the requirement -If user won't select any value from the Dashboard…

On pulling any Dim and Fact, is the same LTS being hit? can u elaborate on your observations?

Try This: Got o Prompts -> Edit Analysis -> Select the Prompt, go to Edit -> Expand options and select "Require User Input". Click OK and SAVE the prompt. Run it and check

Hi, 0 as the Priority indicates high priority, Depending on the requirement the priority needs to be set for respective LTS. Then check for the available dimensions which are being pulled in the report, depending on that the LTS is hit in the BI query.

Try Exporting your dashboard through "Export Entire Dashboard". this should work. Thanks, Kamna

Its a permission issue

In that case, check the columns which are used for creation of the Pie chart. There is an issue with the column name, or might be the case that column was renamed and alias got deleted. Another possible reason might be that column permission is breaking somewhere due to which the BIAdministrator is able to view the Pie…

Check this option mentioned below: Go to Administration -> Manage Privileges -> Access to Graph view-> Add the BIConsumer role. Access should be "Granted". Try your luck!