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.
Related
I wanted to created a dashboard prompt which would automatically fill in with the first available value. This is possible when the selection choices are e.g. all column values.
What I need is to select my values via sql result but still want to fill in the first available value, but that option is blanked out when choosing sql results.
Is there a way to achieve this, maybe via adapting the xml?
Thanks!
What you have highlighted is ONLY ever active when you have interdependent prompts with constraints. I.e. "Limit values by" set to TRUE
I am currently using Oracle sql developer v4.0.3.16. When I do auto-complete of table columns, they show up in ascending order. I've got table with over 200 columns. Auto-completion window shows only 40 positions. When i choose last position '...' - window is being refreshed with all column names, but still in ascending order.
How can i change the way of presenting result in prompt, to show all column names in order as is returned by 'DESCRIBE table' command?
You can't influence the order, we do alphabetical only. Main reason is because a general user isn't going to have your data model memorized.
To get the best bang for your buck with this feature, you're going to want to type the first 1 to however many characters of your column or table or procedure name.
We don't show 200 columns by default, because that's not very helpful at all.
But give us the first letter, and now things become much more interesting.
Starting in a version very close to what you have, the automatic insight feature doesn't even make a suggestion unless you have 10 or fewer 'hits' - although this is configurable.
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.
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.