Are you sure about that? What if you have multiple copies of the form in
a screen? Each copy would have the same name, but their IDs would be
unique (unique IDs are required for HTML validation to pass).
-Adrian
On 7/27/2010 3:44 AM, Scott Gray wrote:
We need to fix this in the framework at some point. A form's name attribute
and its id attribute should never differ, id is really a replacement for name
and it should be used in place of it IMO.
Regards
Scott
HotWax Media
http://www.hotwaxmedia.com
On 27/07/2010, at 10:35 PM, Ravindra Mandre wrote:
Hello Prashanthi,
Please read comments inline
On Tue, Jul 27, 2010 at 3:33 PM, prasanthi_ofbiz<
[email protected]> wrote:
Hi Varun
I want to validate voucherReference field. So I have applied
widget-style to validate-number in the form. Code for validate-number is
already exists in the validation.js file . Still its not validating the
field.
You can check my form code and the validation field is in bold.
<form name="CreateAcctgTrans"
id="createAcctgTrans"
type="single" target="createAcctgTrans"
header-row-style="header-row" default-table-style="basic-table">
<actions>
<set field="isInactive" value="I"/>
</actions>
<auto-fields-service service-name="createAcctgTrans"/>
<field name="organizationPartyId"><hidden
value="${organizationPartyId}"/></field>
<field name="acctgTransTypeId">
<drop-down>
<entity-options entity-name="AcctgTransType"
description="${description}">
<entity-constraint name="hasTable" operator="not-equals"
env-name="isInactive"/>
<entity-order-by field-name="description"/>
</entity-options>
</drop-down>
</field>
<field name="voucherRef" widget-style="validate-number"><text
size="30"/></field>
field name="voucherRef" widget-style="validate-number"
event="onchange" action="
javascript: new Validation('createAcctgTrans', {immediate:
true,onSubmit:true}); "><text size="30"/></field>
Regards
Ravindra Mandre
Bangalore
<field name="glFiscalTypeId">
<drop-down>
<entity-options entity-name="GlFiscalType"
description="${description}" key-field-name="glFiscalTypeId">
<entity-order-by field-name="description"/>
</entity-options>
</drop-down>
</field>
<field name="groupStatusId">
<drop-down allow-empty="true">
<entity-options entity-name="StatusItem"
description="${description}" key-field-name="statusId">
<entity-constraint name="statusTypeId" operator="equals"
value="ACCTG_ENREC_STATUS"/>
<entity-order-by field-name="description"/>
</entity-options>
</drop-down>
</field>
<field name="fixedAssetId">
<drop-down allow-empty="true">
<entity-options entity-name="FixedAsset"
description="${fixedAssetId}">
<entity-order-by field-name="fixedAssetId"/>
</entity-options>
</drop-down>
</field>
<field name="paymentId">
<lookup target-form-name="LookupPayment" size="20"
maxlength="20"/>
</field>
<field name="invoiceId">
<lookup target-form-name="LookupInvoice" size="20"
maxlength="20"/>
</field>
<field name="partyId">
<lookup target-form-name="LookupPartyName" size="20"
maxlength="20" default-value="${parameters.organizationId}"/>
</field>
<field name="roleTypeId">
<drop-down allow-empty="true">
<entity-options entity-name="RoleType"
description="${description}">
<entity-constraint name="hasTable"
operator="not-equals"
env-name="isInactive"/>
<entity-order-by field-name="description"/>
</entity-options>
</drop-down>
</field>
<field name="workEffortId">
<lookup target-form-name="LookupWorkEffort" size="20"
maxlength="20"/>
</field>
<field name="createButton" widget-style="smallSubmit"><submit
button-type="button"/></field>
</form>
Regards
Prasanthi
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Form-widget-validation-tp2234816p2303395.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
