Showing posts with label GO URL. Show all posts
Showing posts with label GO URL. Show all posts

Monday, October 12, 2009

Using more then one GO URL request navigation with HTML drop down list

There was a question on OTN forum http://forums.oracle.com/forums/thread.jspa?threadID=968563&tstart=0 and it's very good base for me to write this post on how to place multiple GO URL navigation to a different subject areas in one column using drop down list.

In one of my previous posts
http://108obiee.blogspot.com/2009/09/go-url-request-navigation-between.html I describe how to use/make GO URL request navigation between different subject areas.

I this example we'll use GO URLs from previous post and put them in only one column and give the user ability which one GO URL navigation from the drop drown list to choose.

As a reference for writing this post I use this link
http://www.tek-tips.com/faqs.cfm?fid=2960 and thanks to that site for placing the code in. The code is combination of javascript and html select and option tag which makes drop down list and put links inside them. So when the user chooses value from the drop down list he navigates on the target report.

This first thing is to make Answers report, I used my Normal model subject area:



Write expression with HTML select and option tag to make drop down list and inside put your GO URLs:





We call javascript function inside column expression in Answers in the select tag and onChange so now we need to declare it somewhere.

This can be done in the dashboard text object in the text properties:





Now place report along with the text object inside the dashboard:



Test

Initial start:



The first report navigation from the drop down list:



Result:



The second report navigation from the drop down list:



Result:

Friday, September 11, 2009

GO URL request navigation between different subject areas

I this post I'll show how to navigate with GO URL between different subject areas (presentation areas, one presentation area is equal to one BMM area).

Example one:

Navigation is between Normal model subject area and Normal model subject area two, which has only renamed logical tables and columns, the physical source is the same for both areas.

BMM subject areas:



Presentation area:



The source report that uses Normal model subject area:



The target report that uses Normal model subject area two:



Column GO URL to Report 26 on the source report:



P2 (target report column) -> PROD.PR_CAT.
P3 (source report column) -> PRODUCTS.PROD_CATEGORY.

Test

I put the source report on the dashboard page.

We will navigate from the third row (Peripherals and Accessories) from the GO URL to Report 26 column:



Before navigation, NQQuery.log for this report:



When navigate to the target report we get:



NQQuery.log for this (target) report:



We see that navigation works fine in this example, when we have navigation between different subject areas that use the same physical tables, the filter is applied on the second report column (logical PROD.PR_CAT, physical PRODUCT.PROD_CATEGORY).

Example two:

Navigation is between Normal model subject area and Normal model subject area three, which has new the physical source, table CATEGORIES with column PROD_CATEGORY, our target column for navigation.

BMM subject areas:



Presentation area:



The source report is the same as in the previous example that uses Normal model subject area.

The target report that uses Normal model subject area three:



Column GO URL to Report 26 subject area three on the source report:



P2 (target report column) -> CATEGORIES.PROD_CATEGORY.
P3 (source report column) -> PRODUCTS.PROD_CATEGORY.

Test

We will navigate from the third row (Peripherals and Accessories), from the GO URL to Report 26 subject area three column:



When navigate to the target report we get:



NQQuery.log for this (target) report:



We see that navigation works fine in this example, when we have navigation between different subject areas that use different physical tables, the filter is applied on the second report column (logical CATEGORIES.PROD_CATEGORY, physical CATEGORIES.PROD_CATEGORY).

Sunday, August 9, 2009

GO URL request navigation and unicode replacement

This post is translated from Croatian, from one of my previous posts. There are many sources of information and questions on OTN forum on how to use GO URL in OBIEE like this one http://forums.oracle.com/forums/thread.jspa?messageID=3595832 and the basic documentation about this can be found in the presentation services administration guide http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31766.pdf. I will not explain here what is the basic syntax. I'll explain how to replace some characters with unicode codes.

There is a two different type of navigation to a new request. One is option value interaction = navigate, on the column properties:




The second, advanced option is to using GO URL.

If we have characters in the column names in the presentation area that are not standard in the ASCII (they are non-ASCII strings) (see http://www.asciitable.com/) for them we used corresponding UNICODE conversion http://rishida.net/scripts/uniview/conversion, for example Croatian character š is non-ASCII string and has to be replaced with UNICODE.

In our case we are using one report to another combination and parsing current row column value from the source report to the target report filter.

We can use Oracle database functions for ASCII and UNICODE codes:

select dump('š', 1016) from dual--hexadecimal: c5a1
select ASCIISTR('š') from dual--unicode: \0161
select to_number('c5a1', 'XXXX') from dual--hexadecimal to decimal: 50593
select chr(50593) from dual--decimal to ascii: š


The source report:



The target report:



GO URL on the source report:



This is required to set before:



P2 is the target request column and P3 is the source request column.

P2 (target) -> Proizvod."%u0160ifra%20proizvoda
P3 (source) -> REPLACE(Proizvod."Šifra proizvoda", ' ', '%20')


*Note that Š is replaced with %u0160 unicode and space with %20 only in the target column. This is related only to a presentation column name. For the source column name we leaved Š and spaces (Proizvod."Šifra proizvoda") and replace space in data inside it (with %20).

Inside P3 (source) it's necessary to replace space with %20, because if there is a space in the data (for example PR 0107) without replacing it with corresponding UNICOD or hexadecimal codes we woudle get only first string (PR) and the second (0107) is cutted.

For example, for spaces we use:

select dump(' ', 1016) from dual--hexadecimal: 20

or


http://rishida.net/scripts/uniview/conversion

If we notice that some of characters are not properly transferred we need to replace them all as well, for example > character should be replaced with REPLACE(Proizvod."Šifra proizvoda", '>', '%3E'), because:

select dump('>', 1016) from dual--hexadecimal: 3e

P3 (source) can be any presentation column, constant, session or repository variable. In our example it is presentation column Proizvod.Šifra proizvoda.

Now if we use for example static repository variable P3 -> VALUEOF("v_sifra") as a source parameter from the source report instead of presentation column we would have GO URL like this:

Monday, June 29, 2009

Same page navigation drills using drill in place, iframes and embedded content in section

In this lession I'll cover same page navigation drills between two reports (not two dashboard pages), and I'll show how to implement this by using different methods and what are disadvantages and advantages of each of them. We want to stay in the focus of the first report (same page navigation) when we call the second report, for all cases.

We'll use reports:





On the PROD_CATEGORY (Navigate) column (Report23) we set value interaction to navigate to Report 24:



On the PROD_CATEGORY (Dimension drill) column (Report23) we set dimension level drill down:



GO URL to Report 24 column on Report23:



Current iframe column:



GO URL to Report 23 column on Report24:



Here we try to turn back dashboard prompt presentation variable from the first focus (when we choose it for the Report23) for returning back from Report24 to Report23 because we don't want to reset previous filter (but this don't work for navigation between two reports on the same page, it works only for navigation between two dashboard pages)

Report navigation inside iframe

We build iframe for Report23 and show it as narrative view in the dashboard.



Column is described above (Current iframe). With this, we have ensured ourself that everything is staying in the same focus (same page).

We test it:



If we navigate from all three columns we stayed in the same page (same focus. same window) and that is right. But here is the problem if we go to Report24 (from the first or the third column) and try to return back with GO URL to Report 23 column on Report24 we cannot set the previous filter in Report23 with presentation variable that we choosed. Report24 cannot see it. So if we go to that link, we get all records:



Drill in place inside a section

This only works for dimension level attributes drills and it has the same dashboard page focus. Otherwise it opens new window and loses focus.



Embedded content in section

Everything works fine, focus is always in the same dashboard page when we navigate using all methods except we cannot use dashboard prompts, neither presentation variables in reports that are inside embedded content. We didn't use drill in place option in the section.



GO URL in embedded content properties:

http://localhost:9704/analytics/saw.dll?GO&nquser=Administrator&path=/shared/Development/Report%2023&Action=Navigate