Endeca Dimension Values Dynamically

Hi All,
We need to provide the dimension value as a data source column (one of the results column) , we are able to provide the dimension value as a Hard Coded Value (Like Wine Type application).
Ex: CRM
But how to point the data source column or property as a dimension value.
For Ex: CRM should be replaced with an actual column (So that we need not hard code all the dimension values)
<DIMENSION_NODE>
<DVAL TYPE="EXACT">
<DVAL_ID ID="2"/>
<SYN CLASSIFY="FALSE" DISPLAY="TRUE" SEARCH="FALSE">PRODUCT</SYN>
</DVAL>
<DIMENSION_NODE>
<DVAL TYPE="EXACT">
<DVAL_ID ID="4"/>
<SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">CRM</SYN>
</DVAL>
</DIMENSION_NODE>

Hi,
We have marked the dimension match mode as 'Auto generate'.
This is our scenario:
SELECT PRODUCT , CATEGORY, SUBCATEGORY FROM PRODUCTCATEGORY TABLE
We have a product dimension and we mapped all these three data source columns to the product dimension.
CRM is a product value -->MARKETING is a category value --> COMMUNITY is a sub category value
How to provide these values from data source instead of hard coding.
We have to provide a hierarchy like PRODUCT > CATEGORY > SUBCATEGORY
<DVAL TYPE="EXACT">
<DVAL_ID ID="2"/>
<SYN CLASSIFY="FALSE" DISPLAY="TRUE" SEARCH="FALSE">PRODUCT</SYN>
</DVAL>
<DIMENSION_NODE>
<DVAL TYPE="EXACT">
<DVAL_ID ID="4"/>
<SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">CRM</SYN>
</DVAL>
<DIMENSION_NODE>
<DVAL TYPE="EXACT">
<DVAL_ID ID="5"/>
<SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">MARKETING</SYN>
</DVAL>
<DIMENSION_NODE>
<DVAL TYPE="EXACT">
<DVAL_ID ID="10"/>
<SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">COMMUNITY</SYN>
</DVAL>
</DIMENSION_NODE>
</DIMENSION_NODE>
Edited by: 986689 on Apr 25, 2013 10:47 PM

Similar Messages

Best Practices - Dynamic Ranking, Dimension Values to Return, etc.

The pinned post says non-technical questions belong on the Business Forum. I can't find an Endeca-specific business forum. If there is one, please tell me where to find it.
My question is about dynamic ranking and the initial display of only the top N dimension values with a "More..." option to see the rest of them.
What's the current wisdom on this from a usability point of view? Use it, don't use it? If using it, show how many values initially?
Or, if not using it, you instead set up a hierarchy of dimensions so that the user never has to look at 50 choices for something?
This is not a technical question. What is the current wisdom? What are the best practices?
Thanks!

Dynamic ranking is a good choice only if all choices cannot be further grouped. In my practice most of the content can be normalized and restricted to a very limited set of options. Dynamic ranking with "more" is an easy way out and seems like a lazy take on content management.

Can I create "Dimension value range" dynamically from data?

Hi,
Can I create "Dimension value range" dynamically from data?
Regards

You need to have a Database Link between two servers. Then you could do execute that statement without any problem. Try to create a database link with the help of
CREATE DATABASE LINK command. Refer Document for further details

Dynamic setting of the dimension values.

Summary:
How can I programmatically control the dimension values displayed in ‘Selected’ window of ‘Edit worksheet’ wizard. of Oracle BI Discoverer plus for OLAP 10.12.48
My objective is to dynamically set the dimension values for a particular dimension based on some criteria.
Requirement:
1.The user should be able to select one of the pre-defined options.
2.Based on the option selected by the user, the necessary business logics need to be applied and then resets the dimension values. The ‘Selected’ window of ‘Edit Worksheet’ should be refreshed.
3.Based on the option the short description & long description should be changed
Existing Application Implementation:
We already implemented this logic in oracle express 6.3.4 as follows.
1.Radio buttons are provided to select the display option
2.Whenever the option is changed, a program is executed in the Express objects. This program evaluates the option, applies the necessary business logics and displays the dimension values based on the option chosen. View is then refreshed to reflect the new dimension values. Note that this process does not affect the total “available dimension” values. The total number of “available dimension” values remains the same. It just manipulates the values in the ‘Selection’ object.
3.The formula of the short description and long description is modified. This formula checks the option and based on it changes the description
Issues I faced to Implement this logic in Oracle BI Discoverer plus for OLAP 10.1.2.48
1. No provision to add radio buttons, hence were trying to implement the functionality with a dimension.
2. No options available for applying business rule and setting the desired dimension values.
3. No ‘event’ available to refresh the views
How can I achieve this in Oracle 10g discoverer plus for olap 10.1.2.48
Thanks,
Natarajan

I think this is not possible.
When you give this settings while creating the SMARTForm, SMARTForm will generate a FM based on that settings. And it is not possible to change those settings at runtime.
We have some constriants like this for dynamic paradigm in SMARTForm. Like, we can provide shading or Box color for the cell.
Regards,
Naimesh Patel

Dimension values display order and record details

Hi All,
I have explicitly ordered my dimension values to be in a logical order instead of alphabetical. Ex: Small, Medium, Large. This works great in the navigation tree but when I view a specific record and it has those 3 dimvals they are listed in alphabetical order.
Is there a when doing a record query to ask Endeca to respect the same display order as in the nav query?
Thanks,
Luc

We are used to add two dummy records in each dimension.
We add the following data:
We use '-1' (surr-key) for Invalids and '-2' for Unknown.
Easy way to populate these dimensions is to add a script together with all objects when you release new functionality. Beware you use the same descriptions.
Even better is to think of a more general solution (more easy to maintain) and store these values in a support table. In such a table you will be able to add more columns to get more details per row. Use this reference table when you load youre dimension. Also you will find the opportunity to add more error handling cases. Especially when you add the dimension in this support table.
Regards
Moscowic

Invalid navigation state. Multiple dimension values from model

We are getting following error on the endeca server in production environment and we are not able to reproduce it in the lower environment, can some body expains what this error means and how this occurs
WARN 03/17/13 20:59:39.418 UTC (1363553979418) DGRAPH {dgraph} Error processing HTTP exchange 797486: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
WARN 03/17/13 21:00:27.575 UTC (1363554027575) DGRAPH {dgraph} Error processing HTTP exchange 798401: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
WARN 03/17/13 21:01:31.394 UTC (1363554091394) DGRAPH {dgraph} Error processing HTTP exchange 800340: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
WARN 03/17/13 21:01:43.216 UTC (1363554103216) DGRAPH {dgraph} Error processing HTTP exchange 800577: Invalid input : Invalid navigation state. Multiple dimension values from model (18,"Product Aisle") in query nav state.
WARN 03/17/13 21:02:39.912 UTC (1363554159912) DGRAPH {dgraph} Error processing HTTP exchange 801775: Invalid input : Invalid navigation state. Multiple dimension values from model (4,"Form") in query nav state.

Hello Tijomon,
Looking at the warning it seems the query being build is not good. Some possibilities are:
~ you have multi select enabled in the front end on a single select dimension
~ the index was moved from one environment to other and some of the dimension values do not match (due to the state being different)
HTH,
Pankaj.

Partial Update - Unknown Dimension Value ID

Hello Old Endeca Friends,
I am getting a lot of these sorts of errors when I perform a partial update:
ERROR 04/25/13 16:56:21.115 UTC (1366908981115) DGRAPH {dgraph,update} Record change references unknown dimension value id 4294484500 [recspec=`UPI:100224148']
I am using MDEX 6.4 and PS 6.1.3. The dimension value ids in question seem to be in the autogen_dimensions.xml, but the dgraph doesn't seem to recognize to know about them. Why?
Any further insight would be appreciated. "Just run a baseline" is not a good answer, I need to do partials every hour throughout the day.

Thanks for the input, everyone.
It looks like my issue was that my state file had a set of updated dimensions but my dgraph did not.
I had a baseline extract with properties X, Y and Z (let's say) and I was adding in new dimensions A and B. I moved my state files from my test environment to my production environment with entries on dimensions A and B. I started getting partial data for dimensions A and B and processing it. However, my dgraph knew nothing about A and B. So, although forge created the dim vals fine and the state files were modified appropriately, my dim val updates and adds on my dgraph failed because my dgraph had never processed a baseline extract with dimensions A and B.
Once I ran a baseline with dimensions A and B, partial updates went fine and have now processed dozens without issue.
Unfortunately, I only get baseline data once a week, so it took me a bit of time to realize what was going on.

Error in Partials for new dimension values

Hello everyone,
I was trying out partial update for the first time on our index. ADDS, UPDATES, DELETES everything works out fine. The only error we are seeing is when an ADD or UPDATE has a new dimension value in it, the following error shows up:
*DGRAPH {dgraph,update} Record change references unknown dimension value id 4294428511 [recspec=`P_RECORD_SPEC:GS1001B101508E']*
This is what I observe:
~ data/state/autogen_dimensions.xml has the entries for this dimension after partial forge is completed
~ the forge output files SomeName--sgmt0.records.xml has the entries for this dimension
My thinking is the new dimensions collected in autogen-dimensions.xml during the partial are not available to the dgraph when the update is run. Am I missing any steps? Can you please point me the right direction. Please let me know if you need additional information on my setup.
[Product: Endeca Information Access Platform version 6.1.4.530518 (analytics enabled)]
Regards.
Pankaj.

Can you share your XML record manipulator where you tag each record with the update action? This would be a place where you would see:
<EXPRNODE NAME="ACTION" VALUE="ADD_OR_REPLACE"/>
The missing piece might be: <EXPRNODE NAME="DIM_ACTION" VALUE="ADD"/>
The latest documentation has a good, dedicated partial update guide.
[MDEX 6.3.0 Partial Update Guide|http://docs.oracle.com/cd/E35825_01/MDEX.630/pdf/PartialUpdatesGuide.pdf]

Dimension Values With Zero Results

Hi All,
We are integrating Endeca Search with a J2EE application . We need to display all the dimension values on the left hand side.
The dimension values are displaying based on results.
How to show all dimension values even if no results will be returned.

Create 2 queries one for getting results and for getting dimensions.
Check for number of records for first query .say (for N=1234 numofrecords returned are 0 )
So create a second query with N=0 and fetch only the dimension not the records. In this way you will have dimension values if 0 results are returned

In Drop Down by Index how can i pass default value Dynamically

Hi Friends,
In Drop Down by Index how can i pass default value Dynamically.Please help me.
Thanks in advance.
Regards,
Kumar.

hi,
if you want the value to be defaulted only the first time you execute the program then write the code which suman has mentioned in the views method
wddoinit.
Regards
Sajid

How to limit dimensions values of querybuilder

Hi,
I want to learn how to limit dimension value in query builder. i want, the user who run the querybuilder can not see a dimension value which i do not want to display.
For example,
The time dimension has "2000" and "2001" values as default which is defined in database. Normally when i run the querybuilder for create new presentation or calculation, In the dimensions panel of the querybuilder display all values of each of dimension. The user can select values which she/he want from that list.
But i want to limit values which the user can see in the dimensions panel of the querybuilder. for this time dimension example, i want to hide "2001" value from the user. How can i do it. if there is any sample code, please share.
Thank you very much for your helps.
ilknur

Thanks Thomas, excellent suggestions as always.
If anybody wants more information regarding Thomas' suggestions please refer to
Oracle9i OLAP Developer's Guide to the OLAP DML for the AW Permit command.
In sumamry: To create permission programs, you define two programs with the names permit_read and permit_write. In these programs, you can specify PERMIT commands that grant or restrict access to individual workspace objects. In addition, you write these programs as user-defined functions that return a Boolean value, and the return value indicates to Oracle OLAP whether or not the user has the right to attach the workspace.
For relational security there is an excellent tutorial on the database pages of OTN, follow this link:
http://otn.oracle.com/obe/start/index.html
then follow the links for Oracle9i Database Release 9.2.0.2 - Security - Creating Label-based Access Control. This module describes how to use Oracle Label Security to setup security based on label policies
These security layers should be transparent to the OLAP metadata layer, therefore, once you have implemented your chosen security method your BI Beans application will only need to connect with the appropriate user to inherit the security layer. For more information see the Security section of the BI Beans Help:
http://otn.oracle.com/bibeans/903/help/
BI Beans product Management Team
Oracle Corporation

Pass values dynamically to the WHERE clause in SFAPI

Hi there
We have a requirement to pass values dynamically (in the run-time of the interface) to the WHERE condition to our SFAPI query.
Eg -
SELECT person, personal_information, address_information, phone_information, email_information, employment_information, job_information, compensation_information, paycompensation_recurring, paycompensation_non_recurring, job_relation, accompanying_dependent,         global_assignment_information, direct_deposit, national_id_card, person_relation
          FROM CompoundEmployee
          WHERE last_modified_on >= to_date('LAST_RUN_DATE') AND
                       last_modified_on <= to_date('CURRENT_RUN_TIME')
LAST_RUN_DATE is stored in a custom entity for which we execute another OData query. The custom entity is updated with the CURRENT_RUN_TIME once the interface has been executed successfully. So the next time the interface is run it picks up the LAST_RUN_DATE from the custom OData entity.
SAP PO has the functionality to run a dynamic query for OData adapters. Refer to Note 2051137 - PI Successfactors adapter : Dynamic odata query and single synchronous sfapi query
Eg - select fields from position (this is what you state in OData query path in the comms channel; this is static); and you have an advanced tab in comms channel where you mention dynamicquery and set it to true (this points to a XSD which has the keyword TOP, SKIP & FILTER in it).
This gets the filter values passed from the BPM from another query (from a OData cust_table).
So the whole query is - select fields from position filter field a = x field b = y etc. Field a field b are fields in position that are you passing values x and y in run time of the interface.
SAP PO also has the advanced tab feature for SFAPI for dynamic query.
Question is -
how to use it?
has anyone implemented this before?
What does XSD will look like?
How do we pass values to the fields to the Where clause for SFAPI.
Any ideas are welcome!
Regards
Arijit Das

After you have added a new where clause on the detail VO, try re-executing VO's query by DetailVO.executeQuery()
If it doesn't work try re-executing the MasterVO's query after you have added the where clause on the detail

Few dimension values used in FACT tables.

Hello all,
We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
Thanks and Regards,
Upendra

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

How to pass tag name and value dynamically in the output of PCo notification?

Hi,
I have a requirement to develop such a scenario where there can be multiple no of tags in PCo (Say 10) but there will be single notification to push the tag name when the value got changed and the changed value to MII. for any value change for any of the tag, the notification will be trigger. So As per my knowledge I have to pass the tag name and value dynamically in the "output" tab of the notification. But need your support to find out how to pass them dynamically.
Thanks in advance.
Regards,
Suman

Hi Suman/Jeedesh,
As per Pco notification, it will trigger whenever any of the tag value changes in Agent instance subscription items.
For above issue, My suggestion
1. Create DB table name TAGLIST with 200 tags as rows in columns (Tagname, TagValue)
2. Based on notification trigger, create a transaction and update values w.r.t TagNames in above table
3. Next time, when notification trigger with fresh value for any of the tag, cross check with existing TagName with Value and update in DB table.
4. And in the mean time, send those Tag details vie mail trigger or as per requirement
Instead of creating 200 notification, above is a just alternate way suggestion to achieve dynamic tag value change notification.
Hope it might solve your problem
Regards,
Praveen Reddy

How do i show descriptions instead of dimension values at presentations ?

We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
Flavio

There a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Endeca Dimension Values Dynamically

Similar Messages

Maybe you are looking for