how to resist the new command from creating new lines?

(0) Share

Report

Posted on by Community Member

i have a form on which i have a method "validateWrite" which throws error on saving each record . As every records gets saved automatically when we click new button on that form and creates a new record.
Buut my form is throwing the error but simultaneously making new record too.
how to resist new record creation while throwing error

regards

rajesh mahato

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Most likely validateWrite implementation is incorrect. You should not throw an error, but return a false value (or checkFailed in case you want a specific validation failure text message in your infolog).

Have a look at other tables' validateWrite methods for an example.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Vilmos,

i have done the same i.e; returned a checkfailed with text message. But the message appears whenever new button is clicked but at the same time a new record gets created.

kindly let me know

regards

Was this reply helpful? Yes No
Guruprasanna 1,089 on at

Like (0)

Report

If you really want to avoid creation of new lines in the form, you can override the task method of the form and when you click new button, you will get task id as 260, by skipping executing of super() will not create new line.

write condition like this

if(_taskId == 260)

{

//ret = super(_taskId);

}

else

{

ret = super(_taskId);

}

Was this reply helpful? Yes No
Suggested answer

Nishant2408 705 on at

Like (0)

Report

Hi Rajesh,

Please check your validateWrite() on the form. Once any validation failure (checkFailed()) occurs execution doesn't stop, it goes further. Please check , is there any other condition written further which is changing your boolean variable's "isValid" value to "True".

Each time you write a condition use declared boolean inside the "if" statement like -

public boolean validateWrite()

{

boolean isValid;

isValid = super();

if (isValid && Your condition)

{

//based on your condition

isValid = checkFailed("------");

}

if (isValid && your next condition)

{

isValid = checkFailed("-----");

}

return isValid;

}

Lets say "isValid = super()" returns "false" and further in the code you are checking some condition which is changing the value to "true" then you'll end up getting a validation message and a new line as well. Which was your case

Was this reply helpful? Yes No
Verified answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Did you try debugging the insert method past the super call, to see what is the call stack where it is being successfully validated and inserted?

Why don't you change aosValidateInsert / aosValidateWrite in the table behind then if you want to prevent inserting the record under any circumstances?

Was this reply helpful? Yes No