We are using the latest current LF Form version which is V10.0.0.1154.  I have setup a form with my customer and at one stage in the Form, the user is entering his ID.  From that ID, we have a lookup that is querying a SQL View that will bring a list of addresses where that user lived and the latest one is the current address.  I have setup the orderby to be in reverse order so that the latest address is positioned at ROW1.

This form is working fine for every user that only has one address in file, so only one row will be returned by the SQL Query.

This issue here is when a user has many addresses on file and multiple rows are returned. What is happening is, for any column that does contain the same information throughout all rows, these values will be published to the field, but for every column where data is not the same in every row, form fields will not be populated.  Example: One user was at address “555, Main Street, Los Angeles, CA” and moved to “666, Main Street, Los Angeles, CA” Form field information will only show “Main Street, Los Angeles, CA” and the street number field will be empty.

I have created a case about this behaviour and they say this is the normal expected behaviour.
The expected behaviour would be like in the Workflow Query activity where if multiple rows are returned, Row1 info will be used by default, and if you need to use other info in other rows, then you handle it using a “ForEachRow” activity.  The same behaviour should apply to Forms.  If I want to get all rows in Form for that query, I would setup an array or a Form-Table to push info from Query to the Table.

If your actual behaviour is the expected default behaviour, I think that what I suggested (using ROW1 information) should be the default behaviour and you should be creating a parameter within each lookup that will allow us to select the behaviour we want to use.

I would like to receive a feedback from Laserfiche Forms development team about this.

Thank you,
Daniel