I have a dashboard containing 2 analysis reports. The reports are nearly identical (one is being used as a reference to a system we are trying to retire), and so they use the same prompt columns.
The problem I am running into is if I leave any of the prompts columns blank, the dashboard prompt still expects a value, causing the report to return nothing.
Dealer Number is equal to Prompt_Dealer -Left default blank in the analysis
and Enterprise is equal to {} -Added {} to the default analysis value
and Dealer Name is equal to "" -Added "" to the default analysis value
I've also tried using null, but with no luck.
Is there a way to ignore the column prompt if I don't enter a value on the dashboard page?
By setting the individual analysis filters to OR, instead of AND, and making sure that they are logically grouped, the dashboard prompts will be ignored when left blank.
Related
I have a report that requires 3 parameters, all 3 has q query to pre populate them using a dataset for each, so the under their properties the available values is selected with the query. Default were also set to use the same query. This work fine.
My problem is when the user of the report wanted to enter the values themselves rather than going into the list populated by the query. Users know the value that they wanted to enter so it's faster for them to enter rather than select. SSRS report seems not to give you the ability to enter if you have set the available values and default values for some reason. Is their a way to go around this please?
Many thanks.
There is one straight forward way to use comma separated multi value parameter rather than list where user enters input.
Below link explains in detail, but I am quite sure you do not want to stick to below solution.
https://www.mssqltips.com/sqlservertip/3479/how-to-use-a-multi-valued-comma-delimited-input-parameter-for-an-ssrs-report/
Another thing you could do is keep your multi value parameter as list as it is and create a text input parameter.
Now if user want to simply choose from list fair enough you will have to handle second parameter as null because user chose from list.
Then on your dataset check and apply filter as 2nd parameter value as not null.
Same goes if user does text input then multi value parameter as not null.
I am using OBIEE 12c and have an analysis that contains a table with two table prompts.
What I am getting is that when I choose values for prompts I see the corresponding result, but when I then change the value of one of them, the other one is not keeping its old value. Is it normal way behavior? I want the prompt to keep the old value when the other prompt is changed. Is it possible?
No that's not normal behaviour. Just tried it on 12.2.1.2 and 12.2.1.4 with Firefox and Chrome. For all four combinations the in-line table prompts when you change the second prompt, the first one stays on its selected value. When you change the first prompt then the second one also changes.
This is normal and expected behaviour since you never know if the currently selected value of prompt two actually exists for the - now new - value of prompts one.
I have a report with 2 columns, both columns measure Sales. I would like 1 column to filter on a supplier while the second column would be overall sales so that I can compare the sales of the supplier to the total sales. This report would be used on a dashboard, however I cannot figure out how to get the total sales column to ignore the prompt for the supplier. Is there any clauses I can use to ignore the dashboard prompt for this one column?
Method:
The prompt sets the variable
Report A calls on the variable to tell it what to include
Report B calls on the variable to tell it what to exclude
How-to
Setup Prompt for “INCLUDE” variable.
Notice the "Set a variable" is set to Presentation Variable:
Report A
Report Filter: Setup Report Variable to accept “Include”:
Report B
**Save a copy of the report and say “is not equal to”
To compare the “All Other except for” report
Below is a simple example on a dashboard.
With no filter set, notice that the "exclude" side is showing all results:
A user must then select an item from the prompt (setting the "Include" variable)
Once the user presses apply you notice that the left side is including the selections and the right side is including everything EXCEPT for whats on the left side:
We have a column that has NULL Record entry, so we cant opt for unchecking NULLABLE field in RPD. Scenario is, we are selecting a particular department ID in prompt and for which the column has a value (Say India) but still shows NULL in the prompt. When we take the Prompt Query fired by OBIEE and run it in SQL, it retrieves only India and NULL doesnt come into picture. Is there any other option to Remove the NULL value in prompt in OBIEE? Any reason why OBIEE shows NULL values?
See this previous post for some guidance. Not all the options will work for you since your situation is different, but it could act as a good starting point.
How to Remove Null Values from prompts in OBIEE
To summarize that link, if you have a limited number of possible values, you could chose specific column Values under Options in the edit prompt dialog box.
Also, checking the box to require user input will sometimes resolve this null value problem, however this is not always the case nor is it always possible depending on your situation.
Finally, try to go to Edit Dashboard Prompt, in Choice List Values drop-down list select SQL Results, then write the SQL statements as column name is not equals to “Unspecfied” (In this way we can remove Null’s also).
Once again, that link is for another question so not all these options are applicable here, but I have found it to be a good starting point.
How to remove invalid Null values that are not present in database but showing in prompts in OBIEE. For some of the columns Null Values is valid but for other it is not. So i want to display null value in prompt only if it is valid.
you will have to got to rpd and modify the column in physical layer; mark it Not Nullable (uncheck the Nullable check-box)
Seven years later... is this still useful?
Anyway, I've found out that there is a better solution if you want to avoid using a Choice List wih the "SQL Result" option and stick to the "All Column Values" option (because this one allows you to use the "Limit Values by" option, which I need).
There is a parameter in the instanceconfig.xml file that defines this behavior: "ShowNullValueWhenColumnIsNullable" (wrongly documented in some versions as "ShowNullValueInPromptsWhenDatabaseColumnIsNullable", as per this Support Doc)
You can see its usage in the Fusion Middleware System Administrator's Guide (search of one of the two property names above).
If you have a limited number of possible values, you could chose Specific column Values under Options in the edit prompt dialog box.
Also, checking the box to require user input will sometimes resolve this null value problem, however this is not always the case nor is it always possible depending on your situation.
Additionally, go to Edit Dashboard Prompt, in Choice List Values drop-down list select SQL Results, then write the SQL statements as columnname is not equals to “Unspecfied” (In this way we can remove Null’s also).
Finally, you could go to the Physical Column properties in Physical Layer and Disable the Nullable option by unchecking the box.
I prefer to work in my filter in the where statement (is not null or not like '').
Another situation you might notice is an extra blank row in the filter. This can be removed by setting the preferences is required in the prompt filter.
Good luck.