Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Chained Prompt in OBIEE 12c doesn't work

SoryApr 12 2017 — edited Apr 13 2017

I have three field in a dashboard prompt: Carrier, Region, End Period. I want only show the existing Region; I want chain Region to Carrier. I try to do that making Carrier a presentation variable and use in the selection of the values in region in the following way:

SELECT "REGIONS"."REGION"  

FROM "Special_Coverage"."CARRIER","Special_Coverage"."DETAIL SPECIAL COV FACTS","Special_Coverage"."REGIONS" 

WHERE  "Special_Coverage"."CARRIER"."NAME CARRIER"= (‘@{CAR}’) FETCH FIRST 65001 ROWS ONLY

But the query doesn’t take the value of the carrier and doesn’t make the filter

Comments

Greg E.-Oracle

Here's a few tips:

- First, Endeca doesn't do natural language processing.  It is very literal with the words that are entered and matched.

- By default, the MDEX limits the number of search terms to 10 by default.  Meaning if you entered 11 or more terms, terms #11 and so-forth would be ignored.

- You can increase this by setting the --search_max flag (typically configured in the <dgraph-defaults> section of your appConfig.xml

- Now, you can increase this to be quite large (say 200 terms).  Then, when a customer enters in their problem description, it won't ignore terms.

- Use the "Match Any" match mode.  Now, this might give you a lot of search results, but that goes to my next point.

- Use the NTerms match mode as your first relevancy ranking module.   This will order the results based on the number of terms

- Make sure you have a good set of "Stop Words", like "the a and it was is of", etc.

So now what will happen is that the customer will enter their problem, and you'll submit the whole thing to the mdex.  The MDEX will throw out the stop words, and then order the results based on the number of terms that matched.

Some other relevancy modules to think about:

- WFreq / Weighted Frequency.  This counts the frequency of words that are more important.

- Stay away from Phrase and Exact.  They'll almost certainly be too slow.

- Use a Static module based on the view count of an article, so that more popular articles will show up first.

You might also want to turn off these MDEX features:

--wb_noibrk    Disables word-break insertion analysis.

--wb_norbrk    Disables word-break removal analysis.

If you're going to submit big sets of search terms, those features will probably be too slow.

1 - 1
Locked Post
New comments cannot be posted to this locked post.