Selective fields redisplaying on immediate='true'

Hi,
I use commandLink-s with immediate='true' for adding rows to a dataTable which contains inputText-s. The immediate is for not blocking on validators when adding a row. But a strange thing is that when some data is being entered and the link pressed the data is redisplayed or lost depending on where the data is - (alway in same 'form') if the data is in a dataTable it disappears, if it is in a panelGrid it stays!!
Any idea why such behaviour, and how to make the freshly entered data to be redisplayed in the dataTable too?
Thanks

Hi,
Is the solution approach detailed in the document Activate Field triggers for syndication valid for MDM 7.1?
Yes, you can use same solution approach detailed in the document Activate Field triggers for syndication valid for MDM 7.1
The document says "The solution approach can be considered as workaround; in the future a syndication functionality based on certain fields might come as part of the MDM standard delivery."..Would like to know if any new functionality has been delivered by SAP in MDM 7.1,
No, still this features are not covered in MDM 7.1
Thanks,
Jignesh Patel

Similar Messages

ActionListener for commandButton not being called after Immediate='true"

I have a form with multiple Boolean buttons. The inputText under these fields need to be validated. I am using
<af:selectBooleanRadio
group="OMSHostType" id="radio1"
text="#{ad4jRscBundle.SAMEHOST} "
autoSubmit="true" immediate="true"
valueChangeListener="#{viewScope.emas_view_ad4jMngrDeploy_Ad4jMngrDeployHomeView.setSameHost}"
shortDesc="#{ad4jRscBundle.SAMEHOSTHELPTEXT}"
selected="#{viewScope.emas_pagemodel_ad4jMngrDeploy_Ad4jMngrDeployHomePageModel.sameHost}"/>
I am using an explicit valueChangeListener to update the radio button values. I have multiple such radio buttons and each field have some exclusively mandatory attributes.
My CommandButton Deploy has stopped calling the actionListener after i made the above changes.It calls the listener if I set immediate="true" in the commandButton also but that bypasses the validation phase, a result which is not desired.
<af:commandButton id="submitCommandButton1"
text="#{ad4jRscBundle.DEPLOY}"
partialSubmit="true"
immediate="true"
action="goto_deployProgress"
actionListener="#{viewScope.emas_view_ad4jMngrDeploy_Ad4jMngrDeployHomeView.submit_Ad4jMngrJob}"
/>
Any idea why immediate attribute is capable of changing the commandButton's properties?

Hi,
without setting immediate=true, the command button action listener executes in teh InvokeApplication phase. Setting it to true invikes it in the earier ApplyRequestValue phase. Buttons that have immediate=true set skip all model updates and validation and instead directly render the response. My suggestion is to set immedatiate=false on the selectBooleanRadio - or is there are reason why you want to have this executing early in teh lifecycle?
Frank

Problem with immediate=true, maybe a Bug

I'm using a dataTable for selecting an user. The selected userBean will be put to the session context with id "selectedUser". The next page allows to edit users values. This edit page contains a cancel button with immedtiate=true param to abort editing and go back to the list. The edit page contains some input fields like:
<h:inputText id="firstName" value="#{selectedUser.firstName}" />
<h:inputText id="lastName" value="#{selectedUser.lastName}" />
These fields are showing correct values for the selected user. But after selecting another user from the list the edit page is showing the values of the previous selected user! By selecting the second user again and again after a while the edit page shows the correct values.
Well, I've added a JSP expression to the edit page to show me if the selected user is the right one "Edit User (${selectedUser})". The value of this expression always shows the correct selected user.
If I modify the command button from:
<h:commandButton action="users" value="Cancel" immediate="true" />
to:
<h:commandButton type="reset" onclick="window.location.href='/faces/users'" value="Cancel" />
the problem does not appear!!!
For me it looks like a bug. Any ideas?
Thx,
Wolfgang

Sorry for the imcomplete testcase, here it comes again:
--- Users.java ---------------------------------------------
package jsf.test;
import java.util.ArrayList;
import javax.faces.context.FacesContext;
public class Users
private ArrayList users;
public Users()
super();
users = new ArrayList();
users.add(new User("User_A", "firstName_A", "lastName_A"));
users.add(new User("User_B", "firstName_B", "lastName_B"));
users.add(new User("User_C", "firstName_C", "lastName_C"));
public ArrayList getUsers()
return users;
public String edit()
FacesContext context = FacesContext.getCurrentInstance();
User user = (User)context.getExternalContext().getRequestMap().get("user");
System.out.println("selectedUser: " + user);
context.getExternalContext().getSessionMap().put("selectedUser", user);
return "navToUser";
--- User.java ---------------------------------------------
package jsf.test;
public class User
private String loginName;
private String firstName;
private String lastName;
public User()
public User(String loginName, String firstName, String lastName)
this.loginName = loginName;
this.firstName = firstName;
this.lastName = lastName;
public String getLoginName()
return loginName;
public void setLoginName(String loginName)
this.loginName = loginName;
public String getFirstName()
return firstName;
public void setFirstName(String firstName)
this.firstName = firstName;
public String getLastName()
return lastName;
public void setLastName(String lastName)
this.lastName = lastName;
public String update()
System.out.println("user update: " + this);
return "navToUsers";
public String toString()
return firstName + " " + lastName;
--- users.jsp ---------------------------------------------
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<html>
<body>
<f:view>
<h:form id="selectUser">
Users
<h:dataTable id="users" value="#{users.users}" var="user">
<h:column>
<f:facet name="header">
<h:outputText value="Login Name" />
</f:facet>
<h:commandLink action="#{users.edit}">
<h:outputText value="#{user.loginName}"/>
</h:commandLink>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="First Name" />
</f:facet>
<h:commandLink action="#{users.edit}">
<h:outputText value="#{user.firstName}"/>
</h:commandLink>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Last Name" />
</f:facet>
<h:commandLink action="#{users.edit}">
<h:outputText value="#{user.lastName}"/>
</h:commandLink>
</h:column>
</h:dataTable>
</h:form>
</f:view>
</body>
</html>
--- user.jsp ---------------------------------------------
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<html>
<body>
<f:view>
<h:form>
User
<h:panelGrid columns="2" cellpadding="5">
<h:outputText value="Login Name" />
 <h:inputText id="lognName" value="#{selectedUser.loginName}"/>
<h:outputText value="First Name" />
 <h:inputText id="firstName" value="#{selectedUser.firstName}"/>
<h:outputText value="Last Name" />
 <h:inputText id="lastName" value="#{selectedUser.lastName}"/>
<h:outputText value=" " />
<h:panelGroup>
<h:commandButton action="navToUsers" value="Cancel" immediate="true"/>
<%-- <h:commandButton type="reset" onclick="window.location.href='/faces/users.jsp'" value="Cancel"/> --%>
<h:outputText value=" " />
<h:commandButton action="#{selectedUser.update}" value="OK"/>
</h:panelGroup>
</h:panelGrid>
</h:form>
</f:view>
</body>
</html>
--- faces-config.xml ---------------------------------------------
<managed-bean>
<description>
Bean for TEST users.
</description>
<managed-bean-name>users</managed-bean-name>
<managed-bean-class>jsf.test.Users</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
<description>
Bean for TEST user.
</description>
<managed-bean-name>user</managed-bean-name>
<managed-bean-class>jsf.test.User</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<navigation-rule>
<from-view-id>/users.jsp</from-view-id>
<navigation-case>
<from-outcome>navToUser</from-outcome>
<to-view-id>/faces/user.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/user.jsp</from-view-id>
<navigation-case>
<from-outcome>navToUsers</from-outcome>
<to-view-id>/faces/users.jsp</to-view-id>
</navigation-case>
</navigation-rule>

Urgent Issue - Immediate=true vs Detail form behavior

I have an ADF Faces Master Table and a Detail Form (both on the same page - this is a functional requirement). They were created using the ADF Faces Master Table Detail Form Control and are based on a Master Detail Entity based View Object.
The underlying Entity Object has some basic validations (ex: Required Name, Address)
I have different actions in the page (Save, Add, Delete), all of them execute the corresponding data control methods.
For Delete and Add I want to bypass input validation so I set immediate="true". So far so good.
Now the issue (or bug):
1. The user selects a record from the master table.
2. The user modifies some values of that record in the detail form (ex: name).
3. The user hits Save - > Values are committed to the database and the master table is refreshed with the detail values.
4. The user hits Add (note that previous values are still there).
5. The user enters Add mode but the values from the previous record are still there.
Correct behavior should be that the current form values are cleared out when hitting add.
I already tried the following in the Entity Object Impl class with no luck:
protected void create(AttributeList attributeList) {
setName("");
super.create(attributeList);
The only way I see it works is by setting immediate="false", but validations are not bypassed here.
Any suggestions / experience with this issue is greatly appreciated.
Thanks,
Claudio.

Hi there, I had the same problem and between us at work we spent 5 days trying to figure this out. The solution is:
* The 'Cancel' commandButton (or commandLink) has immediate="true"
* The inputText fields do not specify immediate (and are therefore immediate="false")
* The action in the backing bean invoked on Cancel click must return an outcome, eg. "list"
* There must be a navigation rule in faces-config.xml for the action, eg. as follows
<navigation-rule>
 <from-view-id>/Admin.jsp</from-view-id>
 <navigation-case>
 <from-outcome>list</from-outcome>
 <to-view-id>/Admin.jsp</to-view-id>
 </navigation-case>
</navigation-rule>* sessionMap.remove("/Admin.jsp") is not necessary
If the action outcome string is null or cannot be found in faces-config.xml, then stale values from the component tree are re-displayed - the bane of many JSF programmers lives. Tinkering with the UIViewRoot seems to have no effect.
Hope this help...
- Adam.

Is it possible to display only dynamically selected fields in the out put?

Is it possible to display only dynamically selected fields in the out put? i need to display set of columns in the selection criteria, but in the output i have display only input given fields. because i need to convert it into .csv file. So i have to display selected fields from internal table. In oracle they are using"execute immediate". is there any equivalent in SAP?
thanks in advance.

Hi Remya,
Are you talking about dynamic programming in ABAP ?
If yes, there are concepts like RTTS which facilitates it.
Yes, the select query also supports dynamic selection of fields. ( Please care about ( ) in dynamic sql ).
Do more research on Field Symbols and statements like ASSIGN COMPONENT OF.
Regards,
Philip.

Popup cache with button has property immediate="true"

Hi
I am using jdevloper 11.1.2.2
I have caching problem with popup has contentDelivery="lazyUncached" and I add cancel button on popup with immediate="true" to skip validation in input fields at popup.
After I click cancel button it hide popup , but again If I show popup, it still cache old data in input feilds.
My popup source is as below
<af:popup childCreation="deferred" id="compPop"
 binding="#{pageFlowScope.CustomersBean.compPop}" autoCancel="disabled" contentDelivery="lazyUncached">
 <af:dialog id="d1" title="#{viewcontrollerBundle.COMPANY} #{pageFlowScope.mode}" closeIconVisible="false"
 type="none">
 <f:facet name="buttonBar">
 <af:toolbar id="t2">
 <af:commandButton text="#{viewcontrollerBundle.SAVE}" id="cb6"
 actionListener="#{pageFlowScope.CustomersBean.onClickSaveCompPop}"/>
 <af:commandButton text="#{viewcontrollerBundle.CANCEL}" id="cb7"
 actionListener="#{pageFlowScope.CustomersBean.onClickCancelCompPop}"
 immediate="true"/>
 </af:toolbar>
 </f:facet>
 <af:panelFormLayout id="pfl1">
 <af:inputText value="#{bindings.CompanyNumber.inputValue}"
 label="#{bindings.CompanyNumber.hints.label}"
 required="#{bindings.CompanyNumber.hints.mandatory}"
 columns="#{bindings.CompanyNumber.hints.displayWidth}"
 maximumLength="#{bindings.CompanyNumber.hints.precision}"
 shortDesc="#{bindings.CompanyNumber.hints.tooltip}" id="it1">
 <f:validator binding="#{bindings.CompanyNumber.validator}"/>
 </af:inputText>
 <af:inputText value="#{bindings.CompanyName.inputValue}" label="#{bindings.CompanyName.hints.label}"
 required="#{bindings.CompanyName.hints.mandatory}"
 columns="#{bindings.CompanyName.hints.displayWidth}"
 maximumLength="#{bindings.CompanyName.hints.precision}"
 shortDesc="#{bindings.CompanyName.hints.tooltip}" id="it2">
 <f:validator binding="#{bindings.CompanyName.validator}"/>
 </af:inputText>
 <af:selectOneChoice value="#{bindings.CompCategory.inputValue}"
 label="#{bindings.CompCategory.label}"
 required="#{bindings.CompCategory.hints.mandatory}"
 shortDesc="#{bindings.CompCategory.hints.tooltip}" id="soc3">
 <f:selectItems value="#{bindings.CompCategory.items}" id="si3"/>
 </af:selectOneChoice>
 <af:selectOneChoice value="#{bindings.City.inputValue}" label="#{bindings.City.label}"
 required="#{bindings.City.hints.mandatory}"
 shortDesc="#{bindings.City.hints.tooltip}" id="soc4">
 <f:selectItems value="#{bindings.City.items}" id="si4"/>
 </af:selectOneChoice>
 <af:inputText value="#{bindings.Tele1.inputValue}" label="#{bindings.Tele1.hints.label}"
 required="#{bindings.Tele1.hints.mandatory}"
 columns="#{bindings.Tele1.hints.displayWidth}"
 maximumLength="#{bindings.Tele1.hints.precision}"
 shortDesc="#{bindings.Tele1.hints.tooltip}" id="it3">
 <f:validator binding="#{bindings.Tele1.validator}"/>
 </af:inputText>
 <af:inputText value="#{bindings.Tele2.inputValue}" label="#{bindings.Tele2.hints.label}"
 required="#{bindings.Tele2.hints.mandatory}"
 columns="#{bindings.Tele2.hints.displayWidth}"
 maximumLength="#{bindings.Tele2.hints.precision}"
 shortDesc="#{bindings.Tele2.hints.tooltip}" id="it4">
 <f:validator binding="#{bindings.Tele2.validator}"/>
 </af:inputText>
 <af:inputText value="#{bindings.Fax.inputValue}" label="#{bindings.Fax.hints.label}"
 required="#{bindings.Fax.hints.mandatory}"
 columns="#{bindings.Fax.hints.displayWidth}"
 maximumLength="#{bindings.Fax.hints.precision}"
 shortDesc="#{bindings.Fax.hints.tooltip}" id="it5">
 <f:validator binding="#{bindings.Fax.validator}"/>
 </af:inputText>
 <af:inputText value="#{bindings.Website.inputValue}" label="#{bindings.Website.hints.label}"
 required="#{bindings.Website.hints.mandatory}"
 columns="#{bindings.Website.hints.displayWidth}"
 maximumLength="#{bindings.Website.hints.precision}"
 shortDesc="#{bindings.Website.hints.tooltip}" id="it6">
 <f:validator binding="#{bindings.Website.validator}"/>
 </af:inputText>
 </af:panelFormLayout>
 </af:dialog>
 </af:popup>

Hi,
can you try and add the af:resetActionListener tag to the cancel button ?
http://docs.oracle.com/cd/E28280_01/apirefs.1111/e12419/tagdoc/af_resetActionListener.html
Frank

H:inputText and immediate="true" not updating cached backing bean value

Hi,
I am having a problem with h:inputText and immediate="true" when
returning back to the same page.I looked through the forums but the
only solution to remove the page from the session works only if I
don't have to change any button label names in the page I am going back
to.Unfortunately, I have to change a button name when I go back to the
same page.The button name change works if i don't remove the page from
session but then h:inputtext has stale values in it from the backing
bean.I also need to avoid validation as it is a huge form.
I have tried looking through the JSF forums but they didn't have any
answers for a very similar question.
I am not sure how exactly to use component binding for the input text and update the model values using an actionListener.I have tried puting a binding on an input text field and then used an actionListener instead of immediate="true' in the h:commandLink.But, putting context.renderResponse() in the actionListener method results in the model values not getting updated.
I have also tried using component.processUpdates(facesContext) as in the UpdateModelValuePhase class -that too doesn't work.
Thanks for any help,
Vijay
Details:
The <h:inputText ..> does not populate the values back from a backing
bean when immediate="true" is used when an action is called.
<h:commandLink id="selectPrincipalId"
action="#{application.selectPrincipal}" immediate="true">
Only <h:inputText has the cached values from the first entry.
<h:inputText id="principalLastName1Id"
value="#{application.currentPrincipal.lastName}" size="10"/><== this
has the cached value from the backing bean application.
<h:outputText gets the new values from the backing bean when the same
page is reentered.
<h:outputText value="#{application.currentPrincipal.lastName}"></h:outputText><==
this refreshes with the new value from the backing bean application.
Here is the solution to rectify the problem:
FacesContext facesContext = FacesContext.getCurrentInstance();
ExternalContext externalContext = facesContext.getExternalContext();
Map sessionMap = externalContext.getSessionMap();
sessionMap.remove("/jsp/befg/tc/apply/enterCreditApplication.jsp");
<== this is the name of the jsf page as defined in the
faces-config.xml.

Hi,I have encountered the same problem as you,and I find a solution myself,which is shown as follows,but I don't know if these is any hidden trouble in the code.
<h:form>
<h:commandLink action="#{app.action}" immediate="true" actionListener="#{app.update}">xxxx</h:commandLink>
<h:inputText id="_id" value="#{app.val}" immediate="true"/> //must set immediate="true" else the model will be not updated
<h:message for="_id"/>
</h:form>
public class App{
public void update(ActionEvent event){
 FacesContext c = FacesContext.getCurrentInstance();
 UIViewRoot root =c.getViewRoot();
 root.processUpdates(c);//to update model and short-circuit the validators
in such circumstance,the UIViewRoot's processUpdates method will be called in the actionlistener,and the back bean who titled to immediate(true)'s inputText will be updated, but the one who titled to immdiate(false)'s inputText will not be updated,Why?
Can anyone tell me way?and how to solve?
Thanks a lot!

Select field

Hi All,
I am having trouble in dealing with 3 select fields simultaneously .
I have three select fields say A,B,C. Based on the selection in select field 'A' a corresponding new list will appear in select field 'B' and then based on seletion in select field 'B' a new list will appear in select field 'C'.
for the first time the sequence is working fine, but for the second time if I am changing the selection in select field 'A', I am getting a warning message as,
Selected value for field 'B' does not match any of the matched values
I am displaying values through 'allowedValues' property name. For every new selection it is not displaying the new list, it is trying to append with the old list and getting the warning message.
Is there a way to resolve this issue.
Please give some ideas.
Thanks in advance.

Hi,
Thanks for the reply.
The code I am using,
<Field>
<Display class='EditForm'/>
<Field name='location'>
<Display class='Select' action='true'>
<Property name='title' value='Location'/>
<Property name='allowedValues'>
<rule name='GetLocations'/>
</Property>
<Property name='nullLabel' value='--Select--'/>
</Display>
</Field>
<Field name='Server'>
<Display class='Select' action='true'>
<Property name='nullLabel' value='--Select--'/>
<Property name='title' value='Server Name'/>
<Property name='allowedValues'>
<block trace='true'>
<rule name='getServerName'>
<argument name='location' value='$(location)'/>
</rule>
</block>
</Property>
</Display>
</Field>
<Field name='Share'>
<Display class='Select'>
<Property name='title' value='Share Path'/>
<Property name='nullLabel' value='--Select--'/>
<Property name='allowedValues'>
<block trace='true'>
<cond>
<eq>
<ref>Server</ref>
<s>XYZ</s>
</eq>
<rule name='SharePaths1'/>
<rule name='SharePaths2'/>
</cond>
</block>
</Property>
</Display>
</Field>
</Field>
I will try your recommendations.
Thanks

Is it possible to submit and bypass validation without Immediate = true?

I am using JDeveloper 11.1.1.6.0.
On our form, we have a "Save" button that properly persists the binding data so that the user can come back and finish filling out the task that they are on later. For this to function properly, the save button needs to have the information on the form to be submitted. If we have no validation, and we have no required fields set, this function works properly. However, if we have any required fields that have not been filled out, the save action is not able to occur until the valiation errors have been corrected.
We have tried changing it so that the save button has "immediate=true" set, however that causes the form data not to be submitted and thus, not persisted.
We have also tried "immediate=true" and setting the form fields to "autoSubmitt=true", but this causes issues when we later have to clear out the data in an inputDate field. In this instance, we receive an illegal argument exception stating that the timestamp must be in format yyyy-mm-dd hh:mm:ss[.ffffffff]. We only see this error when "autoSubmit" is set to true on the field however, as we then need to also ensure that the back end data is cleraed in addition to the field's value as otherwise the field's value never is cleared.
Is it possible to have a component submit without validation, and without being immediate? Or is this not possible?
(On a side note, we've also noticed that if there are components that are set to "immediate", they can throw validation errors when a our save button is pressed and set to immedate, though none of the other fields throw errors)
Thank you

Hi,
I understand you have a save as draft functionality. There is no way other than to use immediate=true (which doesn't work for you) or not using field validation at all to get this use case working. Also note that right now you deal with client side validation errors; when you submit the form, bypassing client side validation you will hit binding level validation, for which you need to set skip validation to true
See this: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/40-ppr-subform-169182.pdf
Frank

Global problem with immediate="true"

JSF specifies that immediate="true" in UICommands should skip the Validation and Update Model phases.
The RI uses the Update Model phase to reset the local values of the input components after updating the model. That means that in the case of immediate="true", the local values are not reset, and thus saved by the state manager.
The problem is that the next display of the page shows the previously entered values, instead of getting the values from the model, which is somewhat strange for a 'cancel' button.
I think this is mainly a problem with the spec which clearly indicates that the clearing of the local values should be done in the update model phase.
Is it possible to have a workaround for this ?

the previous posts have been made long ago, but I'll give it a try:
I think this behavior is still buggy or at least not logical.
Example:
I've got a dataTable which shows a list of entries, each row with an "edit" commandButton and a "new" commandButton below the list.
If the user clicks an "edit" button, he is redirected to the "details" page where he can edit and save the values of this entry. This works as expected. But: On the "details" page, there's also a "cancel" button, which should navigate to the list again, without doing any validation or updating.
If I set this "cancel" button to "immediate", navigation works, but then I'll always see the values of the canceled entry, regardless of which "edit" button I click in the list.
If the "cancel" button is not immediate, validation fails when the user clicks "new" and then "cancel", because he gets an empty form, but some or all fields are required.
There are two workarounds:
1) Creating two different views, one for creating a new entry and one for editing.
2) The "cancel" button is a simple html-button, with the "onlick='location.href=xxxyyy'" attribute.
IMHO both workarounds are ugly. So, why is the view ignoring that there is a complete different entry object in the backing bean of the "details" input fields???
BTW: I'm using JSF SUN RI 1.1.01 (same with 1.2 current snapshot).
With MyFaces, everythings works but it has some other bugs, so I want to stick to the Sun RI.
Thanks,
Walter

Button action bypass validation without using Immediate=true

I have a Form in a page, and a "Query" button to popup a dialog for user to search some information, and help user to fill-in some fields.
I want the "Query" button to ignoral all the validations in the Form (e.g.: required fields). I tried to set the Immedate for the button, but I found I cannot set any inputText value inside ReturnListener event-handler with Immedate is true.
Is there anyway to have a button to action, and bypass all the validation without using Immediate=true?
Thanks,
Samson Fu

Hi,
if you are on JDeveloper 11g, have a look at the skipValidation property on the ADF binding and read: http://oracle.com/technology/products/jdev/tips/fnimphius/ppr_subform/index.html
You can implement a similar approach
Frank

Selection field credit controlig area

Dear all
i have selection field when i receive payment FB05 (without clearing ) system automatic capture defoult CCA in backround .
My question is Can i populate field in entry screen Credit control Area .
Regards
Purushottam Bawane

Hi Purushottam,
Yes that is true. The customer and vendor masters do not have the capability to take profit center in the classic view. This was never possible in the old GL. The profit center is acquired based on the offsetting line (expense or revenue accounts) at the month end when you run 1KEK. transaction.
However in the New GL, it is possible to derive a profit center online through the document splitting functionality. New tables are added (FAGLFLEXA and FAGLFEKXT) which are filled in with profit center through the document splitting functionality. The profit center is derived through the offsetting revenue account and you can see it only after the document is posted. After the document is posted you can only see it is in the GL view (new GL tables) and the classic view still does not have a profit center.
If you want to derive a profit center in the classic view please use a substitution rule based on a user exit. It is more complicated.
Regards
Sharabh

Submit values despite of immediate="true"

Hi,
This is my first try to post a question. So please don't be angry with me if my post isn't perfekt. :-)
I have a JSP with serveral inputText-fields. Each field is required and has a lick to a special search-JSP. To release the link without having the input-fields validated at this moment I had to add the attibute immediate="true". If I fill the input-field while choosing a value from the search-JSP the value will be submitted to the bean. Now my Problem: If I fill the first field without searching with the Link an then try to fill the second field while releasing the link, the first value disappears. (because of the attribute immediate it is not going to be submitted). Is there a possibility to submit this value despite of immediate="true".
I tried to add <f:param> to the link. This seems a possibility. But it could be that I have up to six input-field like this. In this case I habe to sumbit 5 values and this six times. That seems too much. And I hope there is another way to do it.
To clarify my problem here is a reduced and simplified part of my code:
<h:panelGroup>
 <h:outputText value="Field1" />
 <h:commandLink value="Search" action="#{pc_Test.executeSearch1}" immediate="true" />
 <h:inputText id="field1" value="#{pc_Test.field1}" required="true" />
 <h:message for="field1" />
</h:panelGroup>
<h:panelGroup>
 <h:outputText value="Field2" />
 <h:commandLink value="Search" action="#{pc_Test.executeSearch2}" immediate="true" />
 <h:inputText id="field2" value="#{pc_Test.field2}" required="true" />
 <h:message for="field2" />
</h:panelGroup>At the end of the JSP is the submit-Button. If this is clickes the fields will be validated.
I hope you can help me.
Thanx in advance.
Steffi

The immediate="true" attribute in the UICommand will skip under each the update model values phase.
You may find this article useful to get some more insights in the JSF lifecycle:
http://balusc.blogspot.com/2006/09/debug-jsf-lifecycle.html

Strange behaviour on delete button with immediate=true

Hi, I'm using JDev11.1.1.2
I have dragged a view object as a editable form on the page.I added navigation + delete/create buttons.
As I see it all delete buttons should be immediate=true, because I want the user to be able to delete the current row despite validation errors (or maybe this is achievable some other way ? )
But now when I press the delete button, only the readonly fields are updated with next record in the iterator, but the input fields are not updated (they remain with the delete row's values).
If I set disable=true to an inputField, then it gets updated with the next row's value.
I tried with partialTriggers on the inputFields to the delete button - but no luck!
Why I get this different behaviour on inputFields and outputText when the delete button is immediate=true?
And how to deal with this problem?
Thank you!

Thank Frank for the answer, but still no luck
Here is my code:
<af:form id="f1" partialTriggers="cb6">
 <af:panelFormLayout id="pfl1" partialTriggers="cb6">
 <af:inputText value="#{bindings.Kod4.inputValue}"
 required="true"
 id="it1" partialTriggers="cb6">
 </af:inputText>
 <af:outputText value="#{bindings.Kod4.inputValue}" id="out1"/>
 <af:commandButton actionListener="#{bindings.Delete.execute}"
 text="Delete" immediate="true" partialSubmit="true"
 id="cb6"/>
 </af:panelFormLayout>
</af:form>As you can see there are one output and one input field for a same attribute ... the output field gets updated on delete, but the input - doesn't
There are partialTriggers and partialSubmit but still no luck
My view is really a simple one - 3 fields, based on an entity. Tried with different view objects - still the same effect occurs.
I don't see how a delete button can be of any help to the user if it is NOT immediate=true. I cannot add a row and delete it right away if there are validation errors
Please help!
Thanks

Is there a way to create form fields to tab into and type and or drop down selection fields in pages as you can with microsoft word?

is there a way to create form fields to tab into and type and or drop down selection fields in pages as you can with microsoft word?

No

Selective fields redisplaying on immediate='true'

Similar Messages

Maybe you are looking for