hi all - If created dozens of requests the uses drilling. Now I'm getting strange behavior in a certain scenario...
I have a request that is a pivot view and contains UNIONs. One of the columns, employee name, is set up as 'Navigate' for the Value Interaction property. The request drilled to has employee name set up as 'Is Prompted' in the criteria.
If the main request is displayed as a table view, the drilling works fine - the drilled to request opens with the intended employee that was clicked on in the main request. However, if the main request is a pivot view (which is the view I want) instead of a table view, the drilling does not work as intented - the drilled to request opens with all the employee names. I just want to drill on the clicked upon employee, not all the employees.
I'm using OBIEE 10.1.3.4.
Any suggestions as to why this would work as a table view but not as a pivot view?
Try one thing.
Build a separate page and place the report in that. And then give interaction to the page.
Now check if its passing the values. This will pass the values.
Award points if this helped.
Thanks for the suggestion MuRam, however, it still behaves the same.
Once again if I drill to the other page via a table view, it works, if I drill on a pivot view, it does not. I'm just wondering if there's something buggy with obiee where's there's UNION's and a pivot views. I've never had an issue with drilling like this before with pivot views. the only thing different this time, compared to many requests I've created with drilling and pivot views, are UNIONs being used.
What you need to do is-
create a separate report with only a single column (employee in your case) with employee as is prompted.
In the drill report refer this column of the report (ie from data based on another analysis.)
OR even try-
Placing the main report over the drill report section and hide the section(ie in the custome CSS-display:none). This once helped us.
Award points if this helped to help others with similar issues.
Good suggestions, marked it as helpful, however, it doesn't solve the problem. The reason I'm thinking this is a bug when you have a pivot view and UNIONs is...
1. I can add a table view to the request, UNIONs still intact, and drilling works for the table view, but not the pivot view
2. For the pivot view, I can remove all UNIONs, and the drilling works.
The best solution is to define hyperlink for the detail report in the report column itself. Change the expression of column to HTML hyperlink. (Make sure value interaction is disabled) Use Go URL syntax to navigate to detail report and pass parameter, something like below:
<pre>'<a href=”saw.dll?Go&Path=/Shared/ReportName&Action=Navigate&P0=1&P1=eq&P2=Emp.Name&P3=’ || Emp.Name || ‘">’ || Emp.Name || ‘</a>’</pre>
This link has more details:
Hope this helps
That did the trick to get around this buggy behavior. Thanks for the help! - point were awarded.
Thanks all to take the time and offer suggestions, much appreciated.
Edited by: djflo on May 30, 2012 7:03 AM