Navigation doubt

Hello SDN,
I am trying to create an authentication Web Dynpro DC. It would work as follows:
Using an start plug in the main window it should receive two navigation parameters: login, and password.
If authentication is ok, it should redirect to another used DC. If it is not, it should show an auth error message.
I had have a problem with process flow, because the event wdDOInit of the main view is excuted first than onPlugDefault of the main window, and It does not allow to call a view method (a navigation plug) from a window.
Do you have any ideas?
Thank you in advance.
Regards,
Gustavo Pabon.

Hi Gustavo,
In the embedding DC create a method which contains code for calling that component means the life cycle of embedded compoenent should be manual and use IWDComponentUsage class for creating and destroying compoennet . if u have a button in ur logon view assocaite i eith some action and the acton event handler(method) check the valid user if it is then call the method (component creation)or fire plug to error view create inbound plug in error view , two outbound plugs in logon view one for error view and second for Interface view of used component .
Thanks,
Yashpal
give appropriate points!

Similar Messages

Doubt about page navigation

hai sir this is surendra i am doing an academic project that is a web-site like orkut if a user want to see all his friends/groups then a single page is not enough to show all .So i need to use page navigation concept here.Please any one of you tell me "code" and how to use page navigation here.
Waiting for your reply.

you don't give enough information there.
How are you communicating with your database for example? JDBC? Hibernate?
Are you using any framework like Spring or Struts?

Doubt on Navigational attribute

Hi All,
Can we create variables above navigational attributes in bex reporting. Any pointers would be highly appreciated.
Thanks,
Ashok

Sure you can, there is no difference to the handling of regular characteristics. Just try it.
Regards, Klaus

Doubt in Navigational Attribute

Hi All
We have attribute and upon requirement we have changed that attribute to Navigational attribute? and for a period of a month this has been using in the reports.
Now requirement changes and customer says he does'nt need this navigational attribute and he wants to chnage this to display attribute.
Now if I change this navigational attribute to display attribute will there will be effect???
Regards
Balji

It appears from your question that you have not changed the property of the infoobject from attribute to navigational attribute( by unchecking the attribute only option in the General tab of infoobject) but has changed the properties while selecting the object n the cube from attribute only to navigational attribute. If you change this agin then the Infocube will become inactive as well all update rules will also become inactive. Following this the Multiproviders based on this cube will also become inactive. Alll you need to do this change the attribute properties and activate all objects cube , update rule and multiprovider.
Also there is one catch the data already loaded in the cube will have sid linkage for the navigational trribute and probably it needs to be reconstructed before the data is avilable for reporting correctly. I am not sure on this. You may do this in development and see if it has any effct on the data already loaded in the cube.
You don't need to worry about queries ..just remve it from the selection for characteristic drill down.

Problem with Absolute Navigation (External Window) and Light Framework Page

Hi All,
We are using Light Framework page for the portal devolopment. We have an application including two webdynpro iviews where absolute navigation is used to traverse from first iview to second iview (When user clicks a button on first iview). We are showing the second iview in external window (SHOW_EXTERNAL). When ever i clicks the button to traverse to second iview, i am getting an exception.
When we are showing it in same window (SHOW_INPLACE), it is working fine. But the iview is appeared in half of the page with scrollbars. It is working fine with default framework page (with both options SHOW_INPLACE and SHOW_EXTERNAL) and dispalyed in original size as mentioned in iview properties.
Could you please suggest us whether there is any work around for this.
Thanks,
Sudheer

Hi Kathiresan
I couldn't see the address bar of the window (In which second iview is getting displayed). But i can observe no parameters that i passed from first iview is visible in the view source of the second iview (When SHOW_EXTERNAL is used in absolute navigation). I could see all the parameters in the view source (when SHOW_INPLACE is used for absolute navigation). But i am using the same url for both the options (for SHOW_INPLACE and SHOW_EXTERNAL).
I doubt about the url being passed when SHOW_EXTERNAL option is used. But when we checked in debug, The correct url is being triggered (Atleast from first iview). Is there any way that could display the second window with address bar. What is making difference between SHOW_INPLACE and SHOW_EXTERNAL with absolute navigation and light framework page.
Could someone please suggest.
Thanks,
Sudheer.

Some doubts in BW3.5

<Moderator Message: Please read the rules of engagement. You should not post multiple questions to one thread, also use meaningful subjects. And don't offer points.>
HELLO Guys
I have some doubts regarding SAP BW3.5...cAN anyone please clarify.
1.this is regarding SID Concept.
iIn extended start schema,there will be one fact table connected to many dimendion tables.Fact table and Dim tables are connected by dimension IDs.then this Dim table will hold various characteristics.every characteristic will store the characteristic value and address(pointer) to SID table.This SID table will hold again addresses(pointers) to attributes,text and hierarchy tables(if we assume that characteristic have attribute,text,hierarchy) which in turn contain the values.When a query is executed,the OLAP processor searches first for characteristics in dim tables and then with help of dim IDs traces Transaction Data in Fact table relevant for this combination of characteristics and gives output.Did I understand the concept right?
how does OLAP Processor run if the query is on just text of a characteristic and it doesnot include this characteristic?
2.how does navigational attr decrease the performance?
3.cAN YOU ASSIGN
    a. many datasources to one infosource
    b.one datasource to many infosources
    c.many datasources to many infosources...
can you please give real time scenarios for this....
4.how do SID concept improve BW/BI.
thanks
Surekha Chand
Edited by: SChandx200 on Jul 2, 2009 7:35 AM
Edited by: SChandx200 on Jul 2, 2009 7:37 AM
Edited by: Siegfried Szameitat on Jul 2, 2009 1:09 PM

Hi,
You understanding is correct.
{code)
how does OLAP Processor run if the query is on just text of a characteristic and it doesnot include this characteristic?
{code}
This question of yours is not very clear. Re phrase and post it again.
2.how does navigational attr decrease the performance?
Ans:- Say for example in the customer master table customer phone no is the navigational attribute. Now when you select this navigation attriubte in your report then the processor will go and first check the value of Customer say C1 and then determine C1 phone number. Now this look up of cusotmer will happen for every customer . So if say there are huge number of records for which this look up of customer first has to happen then obviously the performance will be impacted.
Hope it is clear.

In the same page: One SyncBO, two tables, and navigation in both, can i?

Hi, i have a doubt, i´m doing an app, in one screen i want put the data in two different tables depend an attribute... Up here all correct,but the problem is navigation.
How can do an independent navigation of the two tables?
Thanks,

Ok, because I still not see the issue here - you can develop whatever you like, so why should I implement something that does effect a table when I do not want to effect that table..... Anyway, what would you like to do exactly with that button? Perhaps then I understand your problem.
Still:
You have one table. There you display the items with field value X. Ok, and when you press a button you want them to be -
removed from the client?
Well, to be honest. JSP is stupid. It does not know when you press the button, what values are displayed there. Only when it is a button of a form and the form was informed about the GUID of these items - then you can work with these GUIDs. I think in your case the easiest way it to say: If I press the first button, then please do this and that on all elements that contain an X in the field, and if I press the second button, do something else on all items without an X in the field. So the easiest way is to do the select statement again in the coding.
Hope this helps to solve the issue.
Regards,
Oliver

«A Nightmare called 6210 Navigator» - Part II / Ex...

In the post - «A Nightmare called Nokia 6210 Navigator» - I explained my disappointment with this new navigator model, specially for people, like me, who own and intensively used the «6110» before.
In all fairness to all of you - Nokia included - I found I should explain myself better.
I have both 'Navigator Phones' - 6110 (with firmware 6.01) & 6210 (with Firmware 3.08, updated first to 3.25 and now to 4.13, if I remember correctly) - have returned the first 6210 and will return again this second unit, mainly because of its lousy sound and 'bluetooth' crackles every time I got Map/Road directions... From which you hear the last words - only - most of the time and what makes this phone useless as a ('voiced') navigation tool.
Maybe the navigation function/program is not supposed to be the main phone feature any more, because Nokia is also using one bad/cheap loudspeaker in the 6210, while the 6110 had two good ones that worked fine against the engine/road/car noise...
My second 6210 surely confirms this is the case, as by now I know that my first (6210) returned unit was clearly not a defective one in terms of 'sound/bluetooth' capabilities - I returned it to the shop during my legal 30 day return period - because for what sound is concerned, this second unit confirms it: The phone is just like that - scrappy!
There are, however, other major problems to be concerned about...
The 'voice command dedicated button' was also removed - this function is now available through the upper right button - making it impossible to use (activating 'bluetooth', for instance) if you are inside any phone application (Maps 2.0, included)!
Has anybody tried a prototype before the phone release? Has anybody used a 6110 Navigator before? I guess not!
This is even more stupid/cumbersome, as for instance, the lower left button is free for this action (keep it pushed for more than 1 second) and would be a much more clever (and logical) solution...
It seems developers either don't waist much time balancing their solutions or haven't thought about it at all! (At least, this can be fixed by remapping the button in a further firmware update, although I doubt they care - or will, eventually, do it...)
IMO, the above described hardware shortcomings, alone, are enough to rule out this phone as a (Car/Driving) navigator unit, and no software or firmware update/release is going to (or can) alter this fact.
If you need to stay with Nokia, the (two years) 'old' «6110 Navigator», is undoubtedly a much better and user friendly 'Phone Navigation' unit - with or without Nokia's Maps application!
If you want to know a little more about other 6210's "Shortcomings & Problems', please do read further...
Maybe releasing a new model every year doesn't give them much time to think... Nevertheless it's there option and frankly it's not an excuse, at least, as far as I'm concerned!
Ergonomically there are other basic errors:
1. The phone front 'fascia' doesn't open/slide enough for you to have space to effectively use the upper keyboard row/buttons.
2. The lower keyboard row is placed to close to the unit's end, making it quite difficult to dial with your thumb while holding the phone in the palm of your hand.
...Sorry to say, but it's a bad/defective layout design! Again, I doubt a prototype was tested by human hands!
...And now - as it seems to be usual with the last Nokia products - The Bugs:
(Please feel free to add the ones you've found - It came a time I gave up using the phone any more!)
1. I couldn't connect the phone by 'bluetooth' with Nokia's own/dedicated «Pc Suite v.7.1.18.0»! (I'm using Win XP Prof SP3)
A bug, the lousy 'bluetooth' sound/connection, or a defective unit?
I discovered that it only happened with my first unit, which I now conclude - was defective. (I had given up after several hours lost trying to figure out what was wrong and discovering that the 'old' 6110 still worked perfectly, even with the new/last «Pc Suite» versions and settings!)
The second phone works now flawlessly with the «Pc Suite» program, I have to say!
2. Setting an alarm to a different day rather than the actual one, switches the alarm back to the actual day, as soon as you save it!
Another bug that 'Beta Users' seem to have forgotten. It's unbelievable how basic things like this can happen... Well, maybe they never used the alarm (or the phone), after all?
Corrected in firmware 4.13; so it seems... (However it took two firmware releases to correct it! Inexcusable, from my point of view!)
3. When navigating, if you receive or make a phone call the 'Navigation Screen' doesn't show back again after ending the call, although you continue receiving 'road voice indications'; to have your 'Map Display/Visual Road Indications' once again you need to 'hit' the 'Start
Application Button' once again - Delirious!!!
4. With 'bluetooth' on, if you give a 'Contacts Voice Command' you don't have sound/voice 'feed back / confirmation' for the 'dialled contact' (as you had in the 6110) - you have to look at the screen to aknowledge it - Quite unsafe if you're driving...
Last... And as usual... Some 'phone freezing', so we can rehearse (and improve) our 'Remove Battery' exercise...
Welcome to the club, thank you very much, I hope you enjoy!
There are several other 'malfunction' that I will not go into depth, as they are user/personal related, and quite frankly I'm so tired of this phone, that I don't feel like going on, and on, pointing out all those shortcomings - after all this should be Nokia's Team own home work!
The ones I pointed out are enough, at least for me, to say - bye, bye, «Nokia 6210 Navigator».
I may even continue to use my old '6110' - Why not? Not perfect, but a much better (navigator) phone - But I'm surely will looking quite closely into another brand for my next (navigator) phone!
Best wishes to all of you (Nokia, included),
telele
P.S. - As usual, you are entitled to contradict my findings... Update the bugs list... Or even praise the «6210 Navigator» phone.
All your comments are surely welcome!
I, on the other hand, will be returning this second unit.
Sorry, but I had enough - Period.
Message Edited by telele on 18-Jan-2009 06:54 PM
Message Edited by telele on 18-Jan-2009 06:55 PM

I have also 'upgraded' from a 6110 Navigator to a 6210 Navigator and found the newer model to be considerably harder to use.
In particular, your point #4 about not having a warning beep when issuing a voice command while in bluetooth/car mode is my number 1 gripe as it makes my cars bluetooth and phones voice dialling completely useless.
If you have found a solution to that particular issue please let me know.

Poor Performance with Webi on top of BW - Large Navigational Attributes

We have recently developed a reporting model based on having a BW cube of approx 20 million records. This has 2 very large line item dimensions (one 14 million records, on 6 million records) that both have navigational attributes stored against them.
We need the design to be like this because the attributes change monthly and we do not wish to do a complete drop and reload of cube data each month (this takes 10-12 hours).
When we build a Universe on top of the cube and try Webi reporting the performance is dreadful - many reports time out completely. This happens whether or not the large line item dimensions are selected in the query. The BW query is very simple just 2 key figures and approx 30 Navigational Attributes as default values. No filters are applied.
For example a query that just contains Calander Year and one key figure either times out after 10 minutes or fails.
Our source of the data is Oracle tables and the same query runs in 2 1/2 minutes and the query runs in RSRT in approx 5 minutes with no problems so it is definately a problem with BOBJ to MDX to BW.
We are on BW7.01 SP5 and XI3.1 SP2. SAP have recommend going to SP3 and using query stripping to help with this but I doubt if this will work.
We have tried building aggregates, splitting into yearly cubes etc but nothing seems to help.
My question is do the large navigational attributes mean Webi simply can't cope with this?
Thanks

Thanks for the suggestions.
Although this did not directly help I've now found a solution.
We had a calculated key figure in the query that doing a count of records on a huge navigational attribute. This was causing all queries to run very slowly (even if the key figure wasn't selected in Webi).
Removing it solved the problem. Will have to find another way to do the count key figure.
Thanks

Navigational Attribute Clarification

Hi all,
I have gone thru the forum for this concept.
Still i have little bit confusion on this.
Wat i understood is, Nav Attr behaves like a characterstic in Reporting, wat my doubt is instead of creating Nav Attr why don't we go for Creating that as a characterstic.
If we create a field as a navigational attribute from where it fetches the data during the reporting.
If i created a fiels as a characterstic from where it fetches the data during reporting.
Please
Regards,
Madhu

Hi,
A NAV is already a characteristic.
I believe that your question is more: why don't we store the characteristic directly in the InfoProvider instead of reporting on a NAV.
Suppose you sell articles (the basic char; CAMCORDER XYZ)
Suppose each article has an attribute "STATUS" = LIVE or DISCONTINUED.
Now you load your sales in a sales cube; you post the selling date, the article ID and it's status. When the article has been just listed (in JAN) to your shop it has the status LIVE, so you'll post something like
JAN__CAMCORDER XYZ__LIVE__$100
Now the status is set to discontinued by a buyer in FEB. Still you sell the remaining pieces:
FEB_CAMCORDER XYZ_DISC_$2000
Interesting to see that your cube can tell the turn over of this CAMCORDER depeding on its status over time.
Now the buyers might be interested to report only on LIVE articles.
Obviously filtering a query on STATUS = LIVE will still show $100 turn over in JAN, even if the article is now discontinued.
This is when the NAV enters into the into the game. If you enable the attribute STATUS as NAV of MATERIAL in your provider and filter you query ON MATERIAL__STATUS = LIVE, the CAMCORDER XYZ won't show up anymore.
just adding: during reporting, the X table of your basic char will give the SID of your NAV. Reporting with NAV add joins between tables, which can impact performance if not tuned properly.
hoping this clear you doubts...
Olivier.
Edited by: Olivier Cora on Apr 9, 2008 10:10 AM

Navigation Tag Library JSP Example?

Hi All,
I am trying to follow "Top-Level Navigation iView" example from "SAP NetWeaver Developer's Guide".
In help they have given JSPCode but have not mentioned in which directory I have to make JSP file and in "portalapp.xml" what type of entry I have to write in it. i.e. "<component>, <property>".
I need to know which entry I have to make in "Portalapp.xml" for JSP component and under which directory(PORTAL-INF) I have to made JSP file.
Please let me know where I can find step by step instruction for Navigation iView example.
I will award full points to useful answer.
Thanks in Advance
Ashish.

Hi Mr.Chowdary,
Thanks for your reply and step by step instruction. I followed steps as you describe. I have one question about "portalapp.xml"
Your answer is really helped me.
I go through "portalapp.xml" my question is regarding <components> element. As describe in <component-config> <property name="ClassName" value="com.sap.portal.navigation.LightTopLevelNavigation"/>
There is no "LightTopLevelNavigation.java" file. As per my under standing there should be a java file with name "LightTopLevelNavigation.java" extended from "AbstractPortalComponent" class and keep it under "src.core" or "src.api" folder.
To define a component you should have related java file. please correct me if I am wrong or explain me what is the significant of <component> element when you do not have any "JAVA" file with LightTopLevelNavigation.java
Please guide me as I am new to EP.
<components>
    <component name="LightTopLevelNavigation">
      <component-config>
        <property name="ClassName" value="com.sap.portal.navigation.LightTopLevelNavigation"/>
        <property name="SafetyLevel" value="no_safety"/>
      </component-config>
      <component-profile>
        <property name="NavigationTagLibrary" value="/SERVICE/com.sap.portal.navigation.navigationtaglibrary/taglib/TagLibrary.tld"/>
        <property name="EPCFLevel" value="0"/>
        <property name="com.sap.portal.iview.ShowTray" value="false"/>
        <property name="com.sap.portal.reserved.iview.IsolationMode" value="EMBEDDED"/>
        <property name="NumOfDisplayLevels" value="2">
          <property name="category" value="Navigation"/>
          <property name="plainDescription" value="Number of Display Levels"/>
          <property name="longDescription" value="Specifies the number of levels displayed in the light top-level navigation"/>
        </property>
      </component-profile>
    </component>
</components>
Thanks for your help and guidence. Full points will be awarded once my doubts are cleared.
Thanks.
Ashish

Nokia N97 Free Lifetime Navigation

Why there is no lifetime driving license in N97 just like 5800 Navigation Edition. Is someone is paying $600 for a phone then the user should get something for that value. Nokia should consider giving free license just like navigation edition.
what do u think?
Google Nexus 4.
Latest Android.
Loving it!

I thought it might be a publishing mistake at first but no, its true. Having been with nokia since the 101 in the early 90s right through to the n97 that i have now, I am left feeling betrayed.
I was able to forgive nokia for releasing the n97 without polishing the software first - (need i list the problems) but now, to have been cut out of the "free navigation" is disgusting.
Like others have posted. We pay a premium to have this phone so why do lesser phones get priority?
Are Nokia going to give us some answers to why this has happened? is it temporary? do they have something better just round the corner for us (i doubt it)?
If this is the way they want to play, I am quite prepared to shift sides and help the evil Google gain some marketplace. At least they share their innovations across the board!
Answer please Nokia!!!

JSF Navigation: Unexepcted value for action in h:form tag

Hi
I am running simple JSF application and when I click the button, it stays in the same page rather than the output page.
I found that the resulting Html code has form action and that action is referring to current page.
here is my JSF code...
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<f:loadBundle basename="gov.ca.dmv.dmvar.bundle.messages" var="msg"/>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>enter your name page</title>
</head>
<body>
   <f:view>
     <h1>
      <h:outputText value="#{msg.inputname_header}"/>
     </h1>
     <h:form id="helloForm">
      <h:outputText value="#{msg.prompt}"/>
      <h:inputText value="#{personBean.personName}" />
      <h:commandButton action="#{personBean.clickSearch}" value="#{msg.button_text}"></h:commandButton>
     </h:form>
   </f:view>
</body>
</html> Here is my html source
<html>
<head>
<title>enter your name page</title>
</head>
<body>
     <h1>
      Welcome to EASE
     </h1>
     <form id="helloForm" method="post" action="/RSample/index.jsf;jsessionid=5AD3913EE84D54EF78A6F46B2AFFFB79" enctype="application/x-www-form-urlencoded">
      Tell us your name:
      <input type="text" name="helloForm:_id2" />
      <input type="submit" name="helloForm:_id3" value="ENTER" />
     <input type="hidden" name="helloForm" value="helloForm" /></form>
</body>
</html> I am giving the action for a button and its not attaching the action for the button ..but its assiging to the form action with wrong value.
Anything I missed here?
--Varma

I am using JSF1.2
I found in html code ...
<form id="helloForm" method="post" action="/RSample/index.jsf;jsessionid=5AD3913EE84D54EF78A6F46B2AFFFB79" enctype="application/x-www-form-urlencoded">My index.jsp file is just forwarding to 'inputname.jsp'
In 'inputname.jsp' i have created a text box and a button.
<html>
<body>
<jsp:forward page="/pages/inputname.jsp"></jsp:forward>
</body>
</html>inputname.jsp
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<f:loadBundle basename="gov.ca.dmv.dmvar.bundle.messages" var="msg"/>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>enter your name page</title>
</head>
<body>
   <f:view>
     <h1>
      <h:outputText value="#{msg.inputname_header}"/>
     </h1>
     <h:form id="helloForm">
      <h:outputText value="#{msg.prompt}"/>
      <h:inputText value="#{personBean.personName}" />
      <h:commandButton id="button1" onclick="#{personBean.clickSearch}" value="#{msg.button_text}"></h:commandButton>
     </h:form>
   </f:view>
</body>
</html> PersonBean.java
package gov.ca.dmv.dmvar.common;
public class PersonBean {
        String personName;
        * @return Person Name
        public String getPersonName() {
           return personName;
        * @param Person Name
        public void setPersonName(String name) {
           personName = name;
        public String clickSearch(){
             return "greeting";
     }faces-config.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC
    "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
    "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
<navigation-rule>
   <from-view-id>/pages/inputname.jsf</from-view-id>
    <navigation-case>
     <from-outcome>greeting</from-outcome>
     <to-view-id>/pages/greeting.jsf</to-view-id>
   </navigation-case>
</navigation-rule>
<managed-bean>
    <managed-bean-name>personBean</managed-bean-name>
    <managed-bean-class>gov.ca.dmv.dmvar.common.PersonBean</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
</managed-bean>
</faces-config>There are no errors after submitting. My only doubt is I am binding the commondButton action to bean method. But in the html code the <form action is referring to index.jsp?

Error In Dashboard Prompt after navigation

Hi All,
Getting View Display Error while navigating using the Dashboard Page names..
Error Generating Drop Down Values
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27002] Near <ORDER>: Syntax error [nQSError: 26012] . (HY000)
SQL Issued: SELECT "Paint".Region FROM "Paint" WHERE ORDER BY 1
Please help me in resolving this..

Thats right...
Err..Ohk. Don't tell me that you are using Hierarchical columns and other attributes in same prompt (i.e. Single GO Button)
Like you have columns like Region-Country-State-City and say Category in same prompt where Region-Country-State-City is hierarchy in OBIEE RPD.
You will have to create 2 seperate prompts here to get it work.
Prompt 1: Region-Country-State-City (Constraint on each level)
Prompt 2: Category and other attributes
This will have 2 prompts so 2 GO button. No way you can achieve this in Single GO even if you change the XMLs and all.
This is OBIEE logic working behind pulling the common fact and also fetching hierarchical data based on level above i.e. constraints here...
Hope this clears your doubt. Or may be give the exact structure of your prompts.

Hi from few days onwards i found one abnormality in my iphone4s .That is if i observe my phone settings screen from right side of the device top navigation appearing rightside height is more than the left side. In reverse manner from the left side.

Hi from few days onwards i found one abnormality in my iphone4s .That is if i observe my phone settings screen from right side of the device top navigation bar appearing rightside height is more than the left side. In reverse manner from the left side. I dnt know whether it is default feature of iphone or not but i am really disappointed due to this. So please anyone help me in this issue and let me clear my doubt and make me happy. Thanks in advance.

I believe what you are seeing is an optical illusion when viewing the screen from the side. Try to align one of the one of the options in Settings, like General, with the navigation bar you'll see it does the same thing.
Hope that helps

Navigation doubt

Similar Messages

Maybe you are looking for