Form validation error when the Table is empty.

Hello Gurus,
I am getting form validation error as soon as the popup is rendered to submit new row.
I am using the this popup to add new row in the table and this is happening only when there no data in the table but it works fine when there is some data in the table.
Screen shot: [http://picpaste.com/adf_error-BAdP8Thv.JPG]
Is there any way can I defer this error till I submit the form. ( which works fine when there is some data in table )
Thanks
Abhijeet

here i tested not happend for me.
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
  <jsp:directive.page contentType="text/html;charset=UTF-8"/>
  <f:view>
    <af:document id="d1" binding="#{backingBeanScope.backing_untitled8.d1}">
      <af:form binding="#{backingBeanScope.backing_untitled8.f2}" id="f2">
        <af:messages binding="#{backingBeanScope.backing_untitled8.m1}"
                     id="m1"/>
        <af:popup binding="#{backingBeanScope.backing_untitled8.p1}" id="p1">
          <af:dialog binding="#{backingBeanScope.backing_untitled8.d3}" id="d3">
            <af:panelFormLayout binding="#{backingBeanScope.backing_untitled8.pfl1}"
                                id="pfl1">
              <af:inputText value="#{bindings.AunitctrlBe.inputValue}"
                            label="#{bindings.AunitctrlBe.hints.label}"
                            required="#{bindings.AunitctrlBe.hints.mandatory}"
                            columns="#{bindings.AunitctrlBe.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlBe.hints.precision}"
                            shortDesc="#{bindings.AunitctrlBe.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it10}"
                            id="it10">
                <f:validator binding="#{bindings.AunitctrlBe.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlUnit.inputValue}"
                            label="#{bindings.AunitctrlUnit.hints.label}"
                            required="#{bindings.AunitctrlUnit.hints.mandatory}"
                            columns="#{bindings.AunitctrlUnit.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlUnit.hints.precision}"
                            shortDesc="#{bindings.AunitctrlUnit.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it11}"
                            id="it11">
                <f:validator binding="#{bindings.AunitctrlUnit.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlCostMethod.inputValue}"
                            label="#{bindings.AunitctrlCostMethod.hints.label}"
                            required="#{bindings.AunitctrlCostMethod.hints.mandatory}"
                            columns="#{bindings.AunitctrlCostMethod.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlCostMethod.hints.precision}"
                            shortDesc="#{bindings.AunitctrlCostMethod.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it12}"
                            id="it12">
                <f:validator binding="#{bindings.AunitctrlCostMethod.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlCostMgmtOpt.inputValue}"
                            label="#{bindings.AunitctrlCostMgmtOpt.hints.label}"
                            required="#{bindings.AunitctrlCostMgmtOpt.hints.mandatory}"
                            columns="#{bindings.AunitctrlCostMgmtOpt.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlCostMgmtOpt.hints.precision}"
                            shortDesc="#{bindings.AunitctrlCostMgmtOpt.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it13}"
                            id="it13">
                <f:validator binding="#{bindings.AunitctrlCostMgmtOpt.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlCostApprMtd.inputValue}"
                            label="#{bindings.AunitctrlCostApprMtd.hints.label}"
                            required="#{bindings.AunitctrlCostApprMtd.hints.mandatory}"
                            columns="#{bindings.AunitctrlCostApprMtd.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlCostApprMtd.hints.precision}"
                            shortDesc="#{bindings.AunitctrlCostApprMtd.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it14}"
                            id="it14">
                <f:validator binding="#{bindings.AunitctrlCostApprMtd.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlJocApprMtd.inputValue}"
                            label="#{bindings.AunitctrlJocApprMtd.hints.label}"
                            required="#{bindings.AunitctrlJocApprMtd.hints.mandatory}"
                            columns="#{bindings.AunitctrlJocApprMtd.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlJocApprMtd.hints.precision}"
                            shortDesc="#{bindings.AunitctrlJocApprMtd.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it15}"
                            id="it15">
                <f:validator binding="#{bindings.AunitctrlJocApprMtd.validator}"/>
              </af:inputText>
              <af:inputText value="#{bindings.AunitctrlCreBy.inputValue}"
                            label="#{bindings.AunitctrlCreBy.hints.label}"
                            required="#{bindings.AunitctrlCreBy.hints.mandatory}"
                            columns="#{bindings.AunitctrlCreBy.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlCreBy.hints.precision}"
                            shortDesc="#{bindings.AunitctrlCreBy.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it16}"
                            id="it16">
                <f:validator binding="#{bindings.AunitctrlCreBy.validator}"/>
              </af:inputText>
              <af:inputDate value="#{bindings.AunitctrlCreDate.inputValue}"
                            label="#{bindings.AunitctrlCreDate.hints.label}"
                            required="#{bindings.AunitctrlCreDate.hints.mandatory}"
                            shortDesc="#{bindings.AunitctrlCreDate.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.id1}"
                            id="id1">
                <f:validator binding="#{bindings.AunitctrlCreDate.validator}"/>
                <af:convertDateTime pattern="#{bindings.AunitctrlCreDate.format}"/>
              </af:inputDate>
              <af:inputText value="#{bindings.AunitctrlUpdBy.inputValue}"
                            label="#{bindings.AunitctrlUpdBy.hints.label}"
                            required="#{bindings.AunitctrlUpdBy.hints.mandatory}"
                            columns="#{bindings.AunitctrlUpdBy.hints.displayWidth}"
                            maximumLength="#{bindings.AunitctrlUpdBy.hints.precision}"
                            shortDesc="#{bindings.AunitctrlUpdBy.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it17}"
                            id="it17">
                <f:validator binding="#{bindings.AunitctrlUpdBy.validator}"/>
              </af:inputText>
              <af:inputDate value="#{bindings.AunitctrlUpdDate.inputValue}"
                            label="#{bindings.AunitctrlUpdDate.hints.label}"
                            required="#{bindings.AunitctrlUpdDate.hints.mandatory}"
                            shortDesc="#{bindings.AunitctrlUpdDate.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.id2}"
                            id="id2">
                <f:validator binding="#{bindings.AunitctrlUpdDate.validator}"/>
                <af:convertDateTime pattern="#{bindings.AunitctrlUpdDate.format}"/>
              </af:inputDate>
              <af:inputText value="#{bindings.RowID.inputValue}"
                            label="#{bindings.RowID.hints.label}"
                            required="#{bindings.RowID.hints.mandatory}"
                            columns="#{bindings.RowID.hints.displayWidth}"
                            maximumLength="#{bindings.RowID.hints.precision}"
                            shortDesc="#{bindings.RowID.hints.tooltip}"
                            binding="#{backingBeanScope.backing_untitled8.it18}"
                            id="it18">
                <f:validator binding="#{bindings.RowID.validator}"/>
              </af:inputText>
              <f:facet name="footer">
                <af:panelGroupLayout layout="vertical"
                                     binding="#{backingBeanScope.backing_untitled8.pgl1}"
                                     id="pgl1">
                  <af:panelGroupLayout layout="horizontal"
                                       binding="#{backingBeanScope.backing_untitled8.pgl2}"
                                       id="pgl2">
                    <af:commandButton actionListener="#{bindings.First1.execute}"
                                      text="First1"
                                      disabled="#{!bindings.First1.enabled}"
                                      partialSubmit="true"
                                      binding="#{backingBeanScope.backing_untitled8.cb1}"
                                      id="cb1"/>
                    <af:commandButton actionListener="#{bindings.Previous1.execute}"
                                      text="Previous1"
                                      disabled="#{!bindings.Previous1.enabled}"
                                      partialSubmit="true"
                                      binding="#{backingBeanScope.backing_untitled8.cb3}"
                                      id="cb3"/>
                    <af:commandButton actionListener="#{bindings.Next1.execute}"
                                      text="Next1"
                                      disabled="#{!bindings.Next1.enabled}"
                                      partialSubmit="true"
                                      binding="#{backingBeanScope.backing_untitled8.cb4}"
                                      id="cb4"/>
                    <af:commandButton actionListener="#{bindings.Last1.execute}"
                                      text="Last1"
                                      disabled="#{!bindings.Last1.enabled}"
                                      partialSubmit="true"
                                      binding="#{backingBeanScope.backing_untitled8.cb5}"
                                      id="cb5"/>
                  </af:panelGroupLayout>
                  <af:commandButton text="Submit"
                                    binding="#{backingBeanScope.backing_untitled8.cb6}"
                                    id="cb6"/>
                </af:panelGroupLayout>
              </f:facet>
            </af:panelFormLayout>
          </af:dialog>
        </af:popup>
        <af:panelCollection binding="#{backingBeanScope.backing_untitled8.pc2}"
                            id="pc2">
          <f:facet name="menus"/>
          <f:facet name="toolbar">
            <af:toolbar binding="#{backingBeanScope.backing_untitled8.t3}"
                        id="t3">
              <af:commandButton text="insert"
                                binding="#{backingBeanScope.backing_untitled8.cb7}"
                                id="cb7"
                                action="#{backingBeanScope.backing_untitled8.cb7_action}"
                                partialSubmit="true"/>
            </af:toolbar>
          </f:facet>
          <f:facet name="statusbar"/>
          <af:table value="#{bindings.ApplUnitControlView1.collectionModel}"
                    var="row" rows="#{bindings.ApplUnitControlView1.rangeSize}"
                    emptyText="#{bindings.ApplUnitControlView1.viewable ? 'No data to display.' : 'Access Denied.'}"
                    fetchSize="#{bindings.ApplUnitControlView1.rangeSize}"
                    rowBandingInterval="0"
                    filterModel="#{bindings.ApplUnitControlView1Query.queryDescriptor}"
                    queryListener="#{bindings.ApplUnitControlView1Query.processQuery}"
                    filterVisible="true" varStatus="vs"
                    selectedRowKeys="#{bindings.ApplUnitControlView1.collectionModel.selectedRow}"
                    selectionListener="#{bindings.ApplUnitControlView1.collectionModel.makeCurrent}"
                    rowSelection="single"
                    binding="#{backingBeanScope.backing_untitled8.t4}" id="t4"
                    partialTriggers=":::cb1 :::cb3 :::cb4 :::cb5 ::cb2">
            <af:column sortProperty="AunitctrlBe" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.label}"
                       id="c6" width="105">
              <af:inputText value="#{row.bindings.AunitctrlBe.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.tooltip}"
                            id="it1">
                <f:validator binding="#{row.bindings.AunitctrlBe.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlUnit" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.label}"
                       id="c3" width="105">
              <af:inputText value="#{row.bindings.AunitctrlUnit.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.tooltip}"
                            id="it9">
                <f:validator binding="#{row.bindings.AunitctrlUnit.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlCostMethod" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.label}"
                       id="c9" width="105">
              <af:inputText value="#{row.bindings.AunitctrlCostMethod.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.tooltip}"
                            id="it6">
                <f:validator binding="#{row.bindings.AunitctrlCostMethod.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlCostMgmtOpt" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.label}"
                       id="c1" width="105">
              <af:inputText value="#{row.bindings.AunitctrlCostMgmtOpt.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.tooltip}"
                            id="it3">
                <f:validator binding="#{row.bindings.AunitctrlCostMgmtOpt.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlCostApprMtd" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.label}"
                       id="c2" width="105">
              <af:inputText value="#{row.bindings.AunitctrlCostApprMtd.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.tooltip}"
                            id="it2">
                <f:validator binding="#{row.bindings.AunitctrlCostApprMtd.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlJocApprMtd" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.label}"
                       id="c4" width="105">
              <af:inputText value="#{row.bindings.AunitctrlJocApprMtd.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.tooltip}"
                            id="it4">
                <f:validator binding="#{row.bindings.AunitctrlJocApprMtd.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlCreBy" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.label}"
                       id="c5" width="105">
              <af:inputText value="#{row.bindings.AunitctrlCreBy.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.tooltip}"
                            id="it7">
                <f:validator binding="#{row.bindings.AunitctrlCreBy.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlCreDate" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.label}"
                       id="c8" width="103">
              <f:facet name="filter">
                <af:inputDate value="#{vs.filterCriteria.AunitctrlCreDate}"
                              binding="#{backingBeanScope.backing_untitled8.id5}"
                              id="id5"/>
              </f:facet>
              <af:inputDate value="#{row.bindings.AunitctrlCreDate.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.mandatory}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.tooltip}"
                            id="id3">
                <f:validator binding="#{row.bindings.AunitctrlCreDate.validator}"/>
                <af:convertDateTime pattern="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.format}"/>
              </af:inputDate>
            </af:column>
            <af:column sortProperty="AunitctrlUpdBy" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.label}"
                       id="c7" width="107">
              <af:inputText value="#{row.bindings.AunitctrlUpdBy.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.tooltip}"
                            id="it5">
                <f:validator binding="#{row.bindings.AunitctrlUpdBy.validator}"/>
              </af:inputText>
            </af:column>
            <af:column sortProperty="AunitctrlUpdDate" filterable="true"
                       sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.label}"
                       id="c10" width="105">
              <f:facet name="filter">
                <af:inputDate value="#{vs.filterCriteria.AunitctrlUpdDate}"
                              binding="#{backingBeanScope.backing_untitled8.id6}"
                              id="id6"/>
              </f:facet>
              <af:inputDate value="#{row.bindings.AunitctrlUpdDate.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.label}"
                            required="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.mandatory}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.tooltip}"
                            id="id4">
                <f:validator binding="#{row.bindings.AunitctrlUpdDate.validator}"/>
                <af:convertDateTime pattern="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.format}"/>
              </af:inputDate>
            </af:column>
            <af:column sortProperty="RowID" filterable="true" sortable="true"
                       headerText="#{bindings.ApplUnitControlView1.hints.RowID.label}"
                       id="c11" width="105">
              <af:inputText value="#{row.bindings.RowID.inputValue}"
                            label="#{bindings.ApplUnitControlView1.hints.RowID.label}"
                            required="#{bindings.ApplUnitControlView1.hints.RowID.mandatory}"
                            columns="#{bindings.ApplUnitControlView1.hints.RowID.displayWidth}"
                            maximumLength="#{bindings.ApplUnitControlView1.hints.RowID.precision}"
                            shortDesc="#{bindings.ApplUnitControlView1.hints.RowID.tooltip}"
                            id="it8">
                <f:validator binding="#{row.bindings.RowID.validator}"/>
              </af:inputText>
            </af:column>
          </af:table>
        </af:panelCollection>
      </af:form>
    </af:document>
  </f:view>
  <!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_untitled8-->
</jsp:root>
    public String cb7_action() {
        try {
            BindingContainer bindings1 = getBindings();
            DCIteratorBinding dciter = (DCIteratorBinding)bindings1.get("ApplUnitControlView1Iterator");
            Row oldCcurrentRow = dciter.getCurrentRow();
            BindingContainer bindings = getBindings();
            OperationBinding operationBinding = bindings.getOperationBinding("CreateInsert");
            Object result = operationBinding.execute();
            if (!operationBinding.getErrors().isEmpty()) {
                return null;
            RichPopup popup = this.getP1();
            RichPopup.PopupHints hints =
                new RichPopup.PopupHints(); //empty hints renders dialog in center of screen
            popup.show(hints);
        catch (NullPointerException e)
            System.out.println(" cause " + e.getCause());
            System.out.println("message" + e.getLocalizedMessage());
            System.out.println("stack trace" + e.getStackTrace());
        return "insert";
    }Edited by: ADF 7 on Feb 10, 2012 2:05 AM

Similar Messages

  • Getting mandatory attribute validation error when the value is defaulted through customization

    Hi
    I am getting Mandatory attribute validation error when we default the value through customization.
    In the UI we have attribute called Last Name which is mandatory at EO level. Customer wanted to default Last name to some value, through page composer it is defaulted to some text and saved.
    When ever we open the page the the same value is defaulted as Last Name and appearing in the UI. But when we submit the page, EO level validation is failing. hence we are getting last name is missing.
    When i debug the code last name attribute value for EO is blank.
    In the UI the attribute last name is associated with bindings  --> #{bindings.lastname.inputvalue}
    The validation is failing if we remove the default binding associated with inputtext box.
    Can some body help what can be reason and is there any solution?
    Thanks,
    Praveen

    version 12.1.2
    I am struggling with same situation, I can't set the default value at business component because, the default value comes from a REST service at run time. In page A,  I have a field F1 that contains value from REST service. Page B has a database bound field F2, whose default value should come from F1 in Page A when a user navigates from Page A to Page B. If I set the value of F2 to be the value of F1, then it displays the value in the UI, but nothing gets submitted to EO and fails at commit.
    To make things difficult, here is my situation: Page A lives in bounded taskflow TF1, and Page B lives in bounded taskflow TF2. So I have created an input parameter P1 in TF 2, which carries over the value of F1 in Page A to Page B. When I am in Page B, I can successfully see the value of the taskflow input parameter P1. So, how do I  programmatically set the value of field F2 with the value of input parameter P1?
    I tried setting the F2.inputValue  in a method call M1 in  taskflow TF2 prior to Page B, but I get null pointer exception as it can't see field F2 yet.
    It seems like a simple thing to do, but I have spent a lot of time trying to make it work without any success.
    I would greatly appreciate any guidance.

  • How to disply the input text box when the data in the table is empty

    Hi,
    I m using JDeveloper 11g 5.1.1.1 : How to display the Input text box when the data in the table is empty or by using the dual table.
    Since there is no record in the table, screen is displying only the lable. not displying the Input text box.? Any property is there to enable?.
    One more case i tried by using dual (eg Select '0' as name from dual) created one view object and dragged in the JSF screen as input combo box with list of values.
    In this case also it is not displaying the combo box.Just displaying the Lable name and 0 only.
    Regards
    Bijesh K

    Hi,
    I didn,t get you.Could you please explain. I am not choosing the ADF table. Selecting and dragging ADF form only.
    Regards
    Bijesh K

  • LOV selection fails when there are validation errors on the base page

    Hi
    I have lovs and some other required fields on a page . If there are any validation error on one of those text fields and if I open the LOV (not related to the text fields) and tries to select
    an item from the LOV search results, it doesn't do it until unless I go back to the base page and correct all the validation errors on the text fields eventhough those text fields have nothing to do with the LOV.
    Any suggestion is appreciated.
    Thanks
    Anwar

    I am on Anwar's team, and I've been dealing with the same problem, although on a different page.
    The JSPX for a contrived example is below. I can provide backing bean code, if needed.
    The form contains two LOVs. Both fields are required. If you leave both fields blank and click Continue, you get a red box around both fields and error messages are displayed. If you then click the magnifying glass to select from the first LOV, the LOV pop-up is rendered. However, you cannot make a selection, either by double-clicking a line item or by clicking OK (the OK button has no effect). All you can do is cancel.
    Interestingly, the act of clicking the magnifying glass on the first LOV gets rid of the red box around that field. So, once you cancel out, the second LOV actually does work. If there were more than two fields on the page, that wouldn't happen. The problem seems to be that the LOV doesn't work unless there are no validation errors on the page other than for the LOV which is being invoked.
    As you can see, immediate="true" is set on both LOVs. The behavior is the same whether this is true or not.
    I'm left thinking there must be something obvious that we're missing... but none of us can see it.
    Thanks,
    KEN
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
              xmlns:f="http://java.sun.com/jsf/core"
              xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
      <jsp:directive.page contentType="text/html;charset=windows-1252"/>
      <f:view>
        <af:document title="Add Item">
          <af:form>
            <af:panelGroupLayout>
                <af:panelHeader text="Header">
                    <af:panelFormLayout>
                        <af:inputListOfValues label="Id" searchDesc="Search" popupTitle="Supplier Id"
                                              simple="true" required="true" id="supplierId"
                                              model="#{viewScope.AddItemBackingBean.supplierIdListOfValuesModel}"
                                              value="#{viewScope.AddItemValuesBean.supplier.id}"
                                              autoSubmit="true" immediate="true"/>
                        <af:inputListOfValues label="Description" searchDesc="Search" popupTitle="Supplier Id"
                                              simple="true" required="true" id="supplierDescription"
                                              model="#{viewScope.AddItemBackingBean.supplierDescriptionListOfValuesModel}"
                                              value="#{viewScope.AddItemValuesBean.supplier.description}"
                                              autoSubmit="true" immediate="true"/>
                        <f:facet name="footer">
                            <af:panelGroupLayout layout="horizontal" halign="right" >
                              <af:commandButton text="Continue"
                                                actionListener="#{viewScope.AddItemBackingBean.continueAction}"
                                                id="continueButton" />
                            </af:panelGroupLayout>
                        </f:facet>
                    </af:panelFormLayout>
                </af:panelHeader>
            </af:panelGroupLayout>
          </af:form>
        </af:document>
      </f:view>
    </jsp:root>

  • Error when opening table container file keydb read only

    Hi Guys,
    We are installing solution manager 4.0 on windows/sql but we are getting following error and couldnt continue the installation
    FKD-00070  Error when opening table container file C:\PROGRA1\SAPINS1\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml for writing. Possible reason: "read-only"
    ERROR 2008-06-04 20:10:56.843
    FKD-00049  XML - Parser error: error: no DTD specified, can't validate in line 1, 1
    in file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml.
    Please help
    Regards,
    Santosh

    Further info
    keydb.xml is empty and the directory has got write access for everyone
    regards
    Edited by: Santosh Keerti on Jun 4, 2008 1:29 PM

  • Validation Error when updating Feature work item to completed state?

    We are on the latest version of TFS 2013 and have customized process templates based off of the Scrum template.
    We have a custom workflow for the Feature work item type. I get an error when trying to update the state to custom done state of "Prod Deployment Successful". The error I receive is below:
    TF237165: Team Foundation could not update the work item because of a validation error on the server etc etc.
    I have TFS Admin rights as well as project and project collection Admin rights.
    Custom States:
    Planned
    Canceled
    On Hold
    In Progress
    Ready For QA
    QA Deployment Failed
    QA Deployment Successful
    Ready For Stage
    Stage Deployment Failed
    Stage Deployment Successful
    Ready For Prod
    Prod Deployment Failed
    Prod Deployment Successful
    Custom Workflow:
    "  "  TO    Planned
    Planned  TO  Canceled
    Planned  TO  On Hold
    Planned   TO  In Progress
    In Progress TO   On Hold
    In Progress TO   Ready For QA
    On Hold  TO  In Progress
    Ready For QA  TO  QA Deployment Failed
    Ready For QA  TO  QA Deployment Successful
    QA Deployment Failed  TO  Ready For QA
    QA Deployment Failed TO   In Progress
    QA Deployment Successful TO   Ready For Stage
    QA Deployment Successful  TO  Ready For Prod
    Ready For Stage TO   Stage Deployment Failed
    Ready For Stage  TO  Stage Deployment Successful
    Stage Deployment Failed TO   Ready For Stage
    Stage Deployment Failed TO   In Progress
    Stage Deployment Successful  TO  Ready For Prod
    Ready For Prod  TO  Prod Deployment Failed
    Ready For Prod  TO  Prod Deployment Successful
    Prod Deployment Failed  TO  Ready For Prod
    Prod Deployment Failed  TO  In Progress
    I have also updated the Process Configuration file to map the states to the meta states so I can show the custom states on the Feature board. The section in the process configuration file that relates to Feature is below:
    <States>
            <State type="Proposed" value="Planned" />
            <State type="InProgress" value="Canceled" />
            <State type="InProgress" value="On Hold" />
            <State type="InProgress" value="In Progress" />
            <State type="InProgress" value="Ready For QA" />
            <State type="InProgress" value="QA Deployment Failed" />
            <State type="InProgress" value="QA Deployment Successful" />
            <State type="InProgress" value="Ready For Stage" />
            <State type="InProgress" value="Stage Deployment Failed" />
            <State type="InProgress" value="Stage Deployment Successful" />
            <State type="InProgress" value="Ready For Prod" />
            <State type="InProgress" value="Prod Deployment Failed" />
            <State type="Complete" value="Prod Deployment Successful" />
          </States>
    The error ONLY happens when I try to update a Feature state to "Prod Deployment Successful". I have looked at other posts and searched the internet and have found no help for my exact issue in TFS 2013. For some
    reason, I can't update the state from "Ready For Prod" to "Prod Deployment Successful".  Does anyone have any ideas of what could be wrong or causing my issue?
    Thanks in advance!

    I finally figured out my issue and fixed it.
    I had to update a reference name in the WIT xml file to Common.BusinessValue instead of Closed.

  • Check Form for Errors When Digitally Signing?

    Greetings,
    I am using LiveCycle Designer ES3.  The target version of my form is Adobe version 8. 
    My form is initially completed by a document generator, then forwarded to a reviewer.  The reviewer will then use the form to document his/her determinations (approved, disapproved, etc) of the material the document generator submitted for review.  Once the reviewer is done with his/her determinations, he/she digitally signs the document using the signature field created in LiveCycle.  Once the document is signed, it is locked down and unable to be edited further.
    Is it possible to have my form check for oustanding errors when the reviewer attempts to sign?  Also, is it possible to not allow the reviewer to sign if errors are present?
    Thank you in advance for your help.

    To clarify, the document generator only fills out a few fields.  The reviewer completes the rest of the form, so the reviewer would be the one making the errors.

  • Database error when updating table ADRC

    Hi,
    We are on ECC 5.0 & are facing a problem whille maintaining anything relevant to table ADRC.
    For eg., if we try to maintain storage location or create a vendor code (XK01), for some inputs it works ...but most times the update just terminates with a message "Database error when changing table ADRC".
    Pls. help.
    Thanks,
    Saba.

    Hi
    You can refer to following SAP Notes in case they help:
    385440   Repairing inconsistencies in Customizing addresses
    417809    Customizing objects display incorrect addresses
    186910    Customers / vendors with incorrect address
    Otherwise i want to know more about the error you are getting to help you in better way.
    Thanks and Regards
    Esha Rajpal

  • Synonyms cant be recompiled when the tables are dropped and recreated?

    hi
    i have a synonym pointing to a table .
    1)when i drop and recreate a table.............
    isnt it enough to recompile the synonym? do i need to drop the synonym as well and recreate again?
    2) when i add new columns to a table will the synonym also show up the new column?
    thanks in advance
    raj

    Recompiled is probably not quite the correct word. Re-validated is more like it.
    Notice that the synonym goes invalid when the table is dropped, but does NOT become valid when the table is recreated.
    That happens the first time it's used (similar to invalid stored procedures).
    SQL> drop table t;
    Table dropped.
    SQL> select object_name, status
      2  from user_objects
      3  where object_name = 'T_SYN';
    OBJECT_NAME                    STATUS
    T_SYN                          INVALID
    SQL> create table t(c number);
    Table created.
    SQL> select object_name, status
      2  from user_objects
      3  where object_name = 'T_SYN';
    OBJECT_NAME                    STATUS
    T_SYN                          INVALID
    SQL> select * from t_syn;
    no rows selected
    SQL> select object_name, status
      2  from user_objects
      3  where object_name = 'T_SYN';
    OBJECT_NAME                    STATUS
    T_SYN                          VALID

  • Insert only if the table is empty

    hi all
    i am searching on the net and would like to check/confirm if it is possible to do insert based on the condition if the table is empty else do update
    i am doing bulk insert in the table but only want to do it if the table is empty
    else i wanna do update
    in the bulk insert
    the code is as follow :
        forall x in 1..tableabc.count
             insert into table_name values tableabc(x);
         exit when tbaleabc%notfound;
            end loopcan you please let me know where i can put the condition ** an example would be very helpfull.
    looking forward to all your suggestions/help

    Is this question related to your other multiple threads?
    bulk update/insert
    bulk update
    https://forums.oracle.com/forums/thread.jspa?messageID=9964721#9964721
    https://forums.oracle.com/forums/thread.jspa?messageID=9952576#9952576
    https://forums.oracle.com/forums/thread.jspa?messageID=9954587#9954587
    Where you were repeatedly told to use merge, and that if merge needed tuning then to post the information needed for a tuning request?
    Instead of doing that you went back and edited out most of the content of your posts and start up yet another thread, where you have been advised to use merge but you will not because you have tested it and it is too slow.
    This is forum abuse and is leading to a lot of other members wasting their time repeating information spread across all your other threads and you need to stop it immediately.

  • Error updating the table condition table 372 in J1IIN

    Hello all,
    I am facing the problem in the transaction code J1IIN (In CIN).
    I have maintained the condition type JEXP ( A/R BED %) as 16% with the Key combination Country/Plant/Control Code (Table 357). While iam saving the Excise invoice the system is throwing the error like Error updating the table condition table 372
    I have gone through the post given by Ms. Jyoti few days back and tried to do some changes in the customisation.
    I tried to maintain a different access sequence for the condition type JEXP i.e In the access sequence except condition table 372, I have maintained all other condition tables.
    Still the error is persisiting. Can anyone put some light on the issue.
    I have even traced the values being hit in the tables directly. There is no relation of table 372, then why is it being cause of the error.
    Gurus plz give ur suggestions.
    Thanks
    Srinivas

    Hello Srinivas/Sandeep
    Please ensure that access sequence in the condition type JEXC has got the table 372. If it is not there please maintain it.
    The standard access sequence used in all duty condition type
    is JEXC  which has got the table 372 this will get updated once
    you save your excise invoice.
      If the issue is resolved, kinldy close the message.
    Regards
    MBS

  • Error updating the table 372

    Hi Gurus,
    I maintained the JCEP ( A/R Cess %) as 3%. While iam saving the Excise invoice the system is throwing the error like error updating the table condition table 372
    Gurus plz give u r suggestions.
    regards,
    jyothi.
    Edited by: jyothi. on Feb 25, 2008 7:26 AM

    Hi Murali!
    Even I am facing the same problem while working in ECC 6.0 environment. I  am continuing in the same post as I feel it is most relevant post to continue the issue instead of opening a new issue.
    I tried to maintain a different access sequence for the condition type JEXP i.e a new Access sequence(ZJEX) and also a new condition tpe (ZJEP). We don't have other Excise condition type in our Pricing procedure.
    In the access sequence except condition table 372, I have maintained all other condition tables.
    We have maintained the values against table 357- Country/Plant/Control Code.
    Still the error is persisiting. Can you put some light on the issue.
    I have even traced the values being hit in the tables directly. There is no relation of table 372, then why is it being cause of the error.
    Thanks in advance,
    Regards,
    Karthik.

  • My iPhone 4S was turned off when the battery got empty, and when I put it on the charger it didn't charge at all. I tried restarting it (on/off home button for 10 sec) nothing happened except it kept giving me the "charge battery"  on its screen.

    Hi! My iPhone 4S was turned off when the battery got empty, and when I put it on the charger it didn't charge at all. I tried restarting it (on/off home button for 10 sec) nothing happened except it kept giving me the "charge battery"  on its screen. I tried with different chargers, still dead! What's weirder is that my sister who has iPhone 4 experienced the same today! No we don't live in the same house!! Does anyone have the same problem?
    Please apple support do you people have a convincing answer for us? Is there a solution? My phone is only 2 years old and was (2 hours ago), in top condition!!
    Please help....

    imanfromsweden wrote:
    Please apple support do you people have a convincing answer for us? Is there a solution? My phone is only 2 years old and was (2 hours ago), in top condition!!
    Please help....
    On belhalf of my fellow volunteers, the answer is, "We'll try our best." 
    My advice is to try not to treat this like it is a paid service provided by compensated professionals.  Ask nicely and one of the nice folks here might take some time out of their weekend to offer advice.

  • Hi,  I would like to ask you a question. a month ago I bought a battery case for iPhone 5 and it worked properly until I installed iOS 7. From that day iphone is operating normally, but when the battery is empty, unfortunately I can not charge additionall

    Hi,
    I would like to ask you a question.
    a month ago I bought a battery case for iPhone 5 and it worked properly until I installed iOS 7. From that day my iphone is operating normally, BUT when the battery is empty, unfortunately I can not charge additionally my iphone with the "extra battery case".
    Does that mean that you did not even create a new software that supports additional battery case or it is something else?
    I need your help!!,
    Thank you in advance.
    Sincerely,
    VK

    The Mophie Air is a good battery case, but doesn't offer the protection she's looking for. I suggest sticking to the Lifeproof, the iPhone has a very good battery (2-3 days moderate usage for me).
    To your 2nd to last paragraph, that is false. Verizon is allowing exisiting customers to keep Unlimited Data - but will lose it once they use a subsidized upgrade. So if you buy a 4S (or LTE device for example) outright, you will keep unlimited data. Mobile hotspot may use up a bit of data, but it is a separate add-on/feature. The new Family Share plans may change that, so it's one giant center of data all devices use.

  • LR 5.5 upgrade. I only get the the 32 bit set up and an error when the 64 bit set up should be created. It says not enough disk space and no access to write. The disk space is ok and the 32 bit file was indeed created.

    LR 5.5 upgrade. I only get the the 32 bit set up and an error when the 64 bit set up should be created. It says not enough disk space and no access to write. The disk space is okay and the 32 bit file was indeed created. I have Windows 7 Home edition.

    Hi Rob, Thanks for your input. The temp location is on the C drive with 228 GB free space. My other drives have 123 GB and 204 GB of free space. I can see how the 32 bit set up is perfectly extracted when it stops when coming to the 64 bit set up. I have done the exercise several times and also made new downloads. I am using Norton 360 and Malwarebytes anti-malware but the dowload from Adobe should be trusted.

Maybe you are looking for