if add new row selected submit saves blank entry

[braddo]

I have a data entry form with some controls, and then an editable list

the editable list has 2 fields for data entry

if i add rows, and add data correctly,and press submit,my data is entered correctly into SQL

if i enter data correctly,and then if i add a row by mistake, and not add any data to the fields.  i press submit, and my data saves, but my correctly entered line of data doesn't get updated into SQL correctly

i have 2 attachments to show the entry form

with 1 entry set, and then a blank line

the 2nd attachment shows SQL not saving the data correctly

[tin]

How is the rule on your submit button configured?

Perhaps SmartObject logging can be enabled to see what is happening:

https://help.k2.com/kb000298

Maybe it is not passing in the input at all.  Or writing the data from the first row, and then wiping it out from the second row.  This is likely a behavior of how the rules are configured or how the SmartObject/Create/Save method was implemented, as I do not see a similar behavior when generating an Editable List view from a simple SmartBox SmartObject.  If so, likely we will need to revise how the rules are configured or methods are implemented.

[braddo]

• On K2ANZ.Framework.SubmitButtons.Item, when Submit is Clicked

   then complete the following one after another
  • then on View, execute the CreateLogEntry method for all the items that have been AddedList

    (configure)

i configure it to enter all data needed into the SMO

[tin]

In a generated editable list view (as an example), there is also a rule that indicates:

When the view executed 'List item added'

         then apply the changes made to the row on the editable list

Please try adding a similar rule on the View or on the Form, so see if it will handle the empty row case more correctly.

[braddo]

hi, i do have that rule on my view

[tin]

It looks like the "then apply the changes made to the row on the editable list" action will only be executed if it meets the advanced condition.

As a possible test, please also add this same rule to the 'else' block to see if the behavior changes or not; this would tell us if it is related to this rule.