Case Insensitive Search for the Dashboard Prompt Filter

Hi,
Can anyone help me, how to make dashboard propmt filter to be case insensitive, as of now dashboard propmts are case sensitive by default. How can we achieve this? Any help on this will be appreciated. TIA

I wonder if it can be done. don't know if there's any work-around for it.
Generally, the data that is imported into the SOD system is case sensitive hence the field on which you base your prompt will also be case sensitive.

Similar Messages

Can I change the Caption (name) of the button Go for the dashboard prompt

Hi,
Can I change the Caption (name) of the button Go for the dashboard prompt
I need to change the name of the button to Set Prompt Values.
i did not see an option to do this
Thanks

Hello Yusuf,
First follow the forum Etiquette, see this http://forums.oracle.com/forums/ann.jspa?annID=939
You have to close the answered threads...
And regarding your question
Go to *{OracleBIDir}:\oraclebi\web\msgdb\l_en\messages*
Open globalfiltermessages.xml file.
Find this text
<WebMessage name="kmsgGFPGo"><TEXT>Go</TEXT></WebMessage>Now edit the Go which is there between the TEXT tags..
Ex: i am editing Go to Confirm
<WebMessage name="kmsgGFPGo"><TEXT>Confirm</TEXT></WebMessage>Save this file and just restart your presentation service.
Check your dashboard prompt now...
(Editing this post from here)
As per your requirement edit should be:
<WebMessage name="kmsgGFPGo"><TEXT>Set Prompt Values</TEXT></WebMessage>Edited by: Kishore Guggilla on Jul 18, 2009 2:45 AM

Case insensitive searching for criteria "All metadata"

If I'm specifically searching in (for example) keywords, then the search is case insensitive. However, if I'm searching "All metadata" then the search is case sensitive. I don't know if this is a bug or a feature (seems like a bug to me), but I'd really prefer it to remain case insensitive for this search criterion as well.
While I'm at it, I'd like to be able to search the IPTC headline.
Bart

I'll second that request on both counts! In fact, I'd like to see the ability to search based on any XMP field.
-Andrew

Can we have a Default Value for the dashboard prompt ?

Hi
I have a requirement as when we run the dashboard, dashboard prompt should be defaulted with a value for the first time.
Defaulting the values is done by SQL Results,but when i try to change the values for that prompt it is not showing any other values other than the defaulted prompt.
Ex: I have a dashboard prompt as Employee Name and i have defaulted the value for that with 'Scott' and ran the dashboard.
When i try to run it for different employee i am not able to get other values to be selected.
Do we have any mechanism as such we can have default value when we run the dashboard for the first time and then all the values when we run it for the second time?
Thanks

user12846884 wrote:
Defaulting the values is done by SQL Results,but when i try to change the values for that prompt it is not showing any other values other than the defaulted prompt.
ThanksYou do something wrong. What is the version of OBIEE? How do you create prompt?

Case insensitive searching in Interactive Page

Hi all,
I am currently working on the interactive report, and wondering is it possible to perform case insensitive search for the data in the textbox besides the magnifying class.
By the default, the system uses "=" for searching. I tried the searching option using "contains", and it would be able to search the content in uppercase and lower case scenario. Is it possible to make "contains" as the default?
Thanks,
Thomas.

By the default, the system uses "=" for searching.I get "Row text contains..." as the filter when entering text directly into the default search box. Perhaps you are working with a saved report?
There's a way to make all IR comparisons case insensitive. See this <a ref="http://apex.oracle.com/pls/otn/f?p=34839:18">example of case/accent insensitive search</a> on a standard report.
That code can't be put in a Before Regions process as described to work with IRs as page processes are not executed by the AJAX call that refreshes the report. However, IR refreshes do run the Virtual Private Database PL/SQL call defined in the application security attributes, so putting the NLS modification code there will work.
Go to Application > Shared Components > Edit Security Attribute | Virtual Private Database (VPD), and make the call from there. Due to the specific requirements of the code that has to be called from here when used for security purposes, this is probably best done by setting this up to make separate calls to packages defined outside APEX, one to handle any actual VPD and other security-related details, and others to orchestrate any other code that has to be run. (For example, in this case it may not be desired to alter the NLS environment on every page, so the program could take a parameter specifying the current page and apply the ALTER SESSION conditionally on this.)

Case Insensitive Search coupled with "LIKE" operator.

Greetings All, I am running Oracle 11gR1 RAC patchet 25 on Windows X64.
This db supports and application that requires case insensitive searches.
Because there are a few entry points into the db I created an "after login" trigger:
CREATE OR REPLACE TRIGGER MyAppAfterLogon_TRGR
AFTER LOGON
ON DATABASE
DECLARE
vDDL VARCHAR2(200) := 'alter session set nls_comp=''linguistic''';
vDDL2 VARCHAR2(200) := 'alter session set nls_sort=''binary_ci''';
BEGIN
IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN
EXECUTE IMMEDIATE vDDL;
EXECUTE IMMEDIATE vDDL2;
END IF;
END MyAppAfterLogon_TRGR;
This ensures that everyone connecting to the DB via any mechanism will automatically have case insensitive searches.
Now, to optimize the know queries I created the standard index to support normal matching queries:
select * from MyTable where Name = 'STEVE';
The index looks like:
CREATE INDEX "CONTACT_IDX3 ON MYTABLE (NLSSORT("NAME",'nls_sort=''BINARY_CI'''))
This all works fine, no issues.
The problem is when I write a query that uses the "LIKE" operator:
select * from MyTable where Name like 'STEV%';
I get back the record set I expect. However, my index is not used? I can't for the life of me get this query to use an index.
The table has about 600,000 rows and I have run gather schema stats.
Does anyone know of any issues with case insensitive searches and the "LIKE" clause?
Any and all help would be appreciated.
L

I think there is issue with your logon trigger :
"IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN"
it should be :
IF UPPER(USER) = 'MYAPPUSER' OR UPPER(USER) = 'MYAPPREPORTINGUSER' THEN
because user name stored in Upper case. Check and try.
HTH
Girish Sharma

Doing case insensitive search

Is there any performant way to do case insensitive searches within the database other than using upper on the column?
If I use upper(col name) the index on the column is bypassed and hence this effects performance.
Is there any other way to do this.
Thanks
Vandana

In 10g rel.2 :
alter session set nls_comp=linguistic;
Execute your query; it should work for text search case insensitive
You can also use regular expression function like regexp_like() with match_option set to i:
select ename
from emp
where regexp_like(ename, k, i);
Best Regards
Krystian Zieja / mob

Case-insensitive Search with Search Form

I am using a Search Form with a UIX Page. One of the issue that need to be resolved is to be able to do case-insensitive search for text information stored in some database columns. Please advise me how to implement case_insensitive search with JDeveloper's Search Form.
Thanks in advance,

Hi Qian,
This article (below) by Steve Muench explains how you can customize Query by example behaviour of ADF BCs and if you really want, how to create your own ViewCriteriaAdapter (but you don't have to go quite that far - luckily :) ).
http://radio.weblogs.com/0118231/2005/02/10.html#a492
Here is what I did. I implemented the following method in my base view object class (MyBaseViewObject). Note that this code is based on a piece of code that Steve posted on his blog (http://radio.weblogs.com/0118231/stories/2003/07/11/implementingAViewCriteriaAdapterToCustomizeQueryByExampleFunctionality.html); originally an example about creating your own ViewCriteriaAdapter.
Since applyViewCriteria(oracle.jbo.ViewCriteria) is used by the query-by-example mechanism you're able to "intercept" the ViewCriteria on "it's way in". After that the standard ViewCriteria does it's job as ususal and generated the where clause when required.
public void applyViewCriteria(ViewCriteria vc)
     if( null == vc || vc.size() == 0 ) super.applyViewCriteria(vc);
     ViewCriteriaRow criteriaRow = (ViewCriteriaRow)vc.first();
     StructureDef def = criteriaRow.getStructureDef();
     AttributeDef[] attrs = def.getAttributeDefs();
     System.out.println(getClass().getName() + ": applyViewCriteria()");
     boolean bFirst = true;
     do{
       if(vc.hasNext() && !bFirst) criteriaRow = (ViewCriteriaRow)vc.next();
       criteriaRow.setUpperColumns(true);
       for (int j = 0, attrCt = attrs.length; j < attrCt; j++)
         String criteriaAttrVal = ((String)criteriaRow.getAttribute(j));
         if (criteriaAttrVal != null && !criteriaAttrVal.equals("") && !JboTypeMap.isNumericType(attrs[j].getSQLType()))
          criteriaRow.setAttribute(j,criteriaAttrVal.toUpperCase());
       bFirst=false;
     }while(vc.hasNext());
     super.applyViewCriteria(vc);
NOTE that doing this makes all your views case insensitive (to vc search) you may want to implement more functionality in your base view object to set whether a view is in case insensitive mode or not.
ALSO that flag will not be passivated (if I remember correctly - someone correct me if I'm wrong) so you'll have to add that flag to the passivated data.
Cheers!
Sacha

Support for Case Insensitive Search and IN Clause in Open SQL

Hi,
I have some doubts regarding Open SQL:
- Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
- Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer |http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm]also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

No cross posting.
Read the "Rules of Engagement"
Regards
Juan

What is the best way to do a case insensitive search?

Hi Guys,
hopefully a quick one, anyone know what the best way to perform a case-insensitive search is? at the moment many of our stored procedures perform selects against un-indexed fields (e.g. product title) and to avoid casing problems we have an UPPER around the field name and the variable e.g.
AND (nvcproducttitle IS NULL OR
UPPER(p.NVCTITLE) LIKE '%' || UPPER(nvcproducttitle) || '%')
This seems to work just fine but on a large catalogue (10 million+) it can take 50-60 seconds to return.
Any pointers would be appreciated,
J

user7186902 wrote:
Hi Guys,
hopefully a quick one, anyone know what the best way to perform a case-insensitive search is? at the moment many of our stored procedures perform selects against un-indexed fields (e.g. product title) and to avoid casing problems we have an UPPER around the field name and the variable e.g.
AND (nvcproducttitle IS NULL OR
UPPER(p.NVCTITLE) LIKE '%' || UPPER(nvcproducttitle) || '%')
This seems to work just fine but on a large catalogue (10 million+) it can take 50-60 seconds to return.
Any pointers would be appreciated,
JYou could either ensure you have a function based index for your column e.g.
create or replace index fn_idx on prodtable (upper(nvctitle));
nb. syntax not checked
or you could use regular expressions. REGEXP_LIKE allows for case insensitive like searches.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/conditions007.htm#SQLRF00501

Dashboard prompt filter navigating to different tabular reports

Hi,
I was able to implement this halfway.
My Dashboard prompt has 4 filters, the fourth filter has three drop down values.
"Report with Sales Amount"
"Report with Purchase Amount"
"Report with both Purchase and Sales"
when the user selects the first choice, it should navigate to my "SALES-REPORT" which is section2 of the dashboard page.
when the user selects the second choice, it should navigate to my "PURCHASE-REPORT" which is section3 of the dashboard page.
when the user selects the third choice, it should navigate to my "COMBINED-REPORT" which is section4 of the dashboard page.
All three are three entirely different report, so far with previous advice, i have created the Dashboard prompt and the presentation variable, but unable to proceed further.
Thanks for your time and help.

I will show you how to do it with one. Repeat for the other two reports.
1) Build a small report with any two CHAR columns. For the first column, click on the fx, copy the column name and then delete it. Type this: CASE WHEN 1=0 THEN (paste the column name you copied here) ELSE 'Report with Sales Amount' END. The second column leave as is. The reason for the second column is because OBIEE requires every report to have at least one column. Since we "dummied out" the first column, if you don't have another column, OBIEE will error.
2) Put a filter on the first column and set it to the Presentation Variable you had for the fourth column prompt (the one the users can select "Report with Sales Amount" from).
3) On your dashboard, drag the "SALES-REPORT" report to a section.
4) On this section, click on the Section Properties button (NOT the report Properties button!) and select Guided Navigation.
5) Browse to the small report you created in step 1) and click on the "when the report returns rows" radio button.
So what this does is this: When the user selects "Report with Sales Amount" from the dashboard prompt, it will produce a row on your small report. And because of this, the Guided Navigation of the section will display this report. When the user selects anything else, the small report will return no rows and this section will not display.
Repeat the above for the other two reports making the proper modifications.

Case insensitive search working in dev but not in prod

Hello All,
I had set the CASE_SENSITIVE_CHARACTER_COMPARISON parameter as OFF in NQSConfig.ini file for enabling the case insensitive search in OBIEE.
This setup is letting me do the case insensitive search in Dev env but the same doesnt work in prod env. I tried pointing both prod and dev rpd to same prod db.
With same db also, case insensitive search doesnt work in prod env.
Any idea for which other configuration I can look for.
Thanks in advance.

Thanks Stijin. I had seen this post earlier. Case insensitive search works fine after setting the value for NLS_SORT and NLS_COMP in production RPD but the other report with distinct clause starts failing. Not sure about the reason.
Saw this comment from you in that post:
The only compromise solution we could find was to "cache" the column value we wanted to use in insensitive searches. These were mainly used in "show all choices" while setting prompts. Other than that there isn't much you can do in an Oracle database.
Can you please tell me how to implement the above.

How to get the value of multi-select in the Dashboard Prompt

I have a multi-select prompt in the Dashboard Prompt, what I want is, how do I know that user has choose one value,
for examle, for some reasons, if user didn't choose any value, then I will set one column in answer as "customer office" , if user choose one value, then the column in answer will be "customer name".
any comments, thanks.

Hi,
first define the presentation variable for the required column prompt. ex: PV
Then in report level set the filter for that column = @{PV}{customer office}. here u have to give default value as "customer office", so by default the report in dashboard will show customer office even though the user does not select any value from dashboard prompt.
Mark If Helpful/correct.
Thanks.

Possible to do case-insensitive searches?

G'day,
I was wondering if it's possible to do case-insensitive searches in oracle/HTMLDB?
I've tried what I thought would work
"select * from application where name like '%microsoft%'", this unfortunately doesn't return any records with a capital in it(eg "Microsoft").
If there is no way to do case-insensitive searches what is the best way around it?
Thanks
-Colin

Colin,
Yes it is possible to do case insensitive searches using SQL. Try, for example:
select * from application where upper(name) like '%ORACLE%'
The trick is to upper() both sides of the like operator.
Sergio

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

Case Insensitive Search for the Dashboard Prompt Filter

Similar Messages

Maybe you are looking for