Help with validateField() logic

(0) Share

Report

Posted on by Sachin Mittal

 public boolean validateField(FieldId _fieldIdToCheck)
    {
        boolean ret;
        ret = next validateField(_fieldIdToCheck);
        TaxInformationVendTable_IN tax;
        if(_fieldIdToCheck == fieldNUm(TaxInformationVendTable_IN, PanNumber))
        {
            while select RecId , PANNumber , VendTable from tax
                where tax.VendTable != this.VendTable
                && tax.PanNumber == this.PaNNumber
            {
                if(tax)
                {
                    ret = false;
                    Info(strFmt("@OAB:OABPanNumberExist",tax.PANNumber,tax.vendtable,VendTable::find(tax.VendTable).vendorName()));
                }
            }
        }
        return ret;
    }

For a new record, if the PAN Number field is kept blank system shall not check other records.
This pop-up shall only be as a warning and shall allow to create and save record even if the same PAN exist in other records,

I have the same question (0)

All responses (13)

Answers (1)

Suggested answer

GirishS 27,825 Moderator on at

Like (0)

Report

RE: Need Help with Code D365F&O

Hi Sachin Mittal,

Can you elaborate more on the issue?

You just added info - If you want to allow the user to save the record if the same PAN exist for other records, then ret must return true.

On your code refer to line number 14 - ret buffer must be set to true then only it will allow you to the save the record.

Thanks,

Girish S.

Was this reply helpful? Yes No
Sachin Mittal 2 on at

Like (0)

Report

RE: Help with validateField() logic

hi , after uisng advice by you , info is printing record two times

Was this reply helpful? Yes No
Martin Dráb 236,960 Most Valuable Professional on at

Like (0)

Report
RE: Help with validateField() logic

You can use the "if" statement to run your logic only if PAN Number is set. If you don't want to fail the validate, don't set ret to false.

For example:

public boolean validateField(FieldId _fieldIdToCheck) { boolean ret = next validateField(_fieldIdToCheck); switch (_fieldIdToCheck) { case fieldNUm(TaxInformationVendTable_IN, PanNumber): if (this.PanNumber) { TaxInformationVendTable_IN tax; while select PANNumber, VendTable from tax where tax.VendTable != this.VendTable && tax.PanNumber == this.PanNumber { info(strFmt("@OAB:OABPanNumberExist", tax.PanNumber, tax.vendTable, VendTable::find(tax.VendTable).vendorName())); } } break; } return ret; }

Was this reply helpful? Yes No
GirishS 27,825 Moderator on at

Like (0)

Report

RE: Help with validateField() logic

Info is not printing 2 times - I guess totally 6 vendors has same PAN number as you have given in the form.

Thanks,

Girish S.

Was this reply helpful? Yes No
Sachin Mittal 2 on at

Like (0)

Report

RE: Help with validateField() logic

no , i have also added screenshot inmf9 , inmf7 ,inmf3 is printing two times

Was this reply helpful? Yes No
GirishS 27,825 Moderator on at

Like (0)

Report

RE: Help with validateField() logic

Please debug the code and confirm that the while select you have added is looping 3 times only based on your record.

Thanks,

Girish S.

Was this reply helpful? Yes No
Sachin Mittal 2 on at

Like (0)

Report

RE: Help with validateField() logic

it is looping 6 times

Was this reply helpful? Yes No
GirishS 27,825 Moderator on at

Like (0)

Report

RE: Help with validateField() logic

I am not sure why its looping 6 times. Open "TaxInformationVendTable_IN" in table browser and see how many records against that PAN number - On the table "TaxInformationVendTable_IN" - "Vendor" field is unique. So, I don't think data might not be the issue.

Please review the while select statement you added.

Thanks,

Girish S.

Was this reply helpful? Yes No
Sachin Mittal 2 on at

Like (0)

Report

RE: Help with validateField() logic

when ret was false it was showing info only one time , when ret is true its showing two times

Was this reply helpful? Yes No
Martin Dráb 236,960 Most Valuable Professional on at

Like (0)

Report

RE: Help with validateField() logic

Why is it in validateField() at all? Will you have the same problem in modifiedField() (which sounds like a better place)?

Was this reply helpful? Yes No