I'm curious if this is desired behavior or if I have something not set correctly. Here is an example of a text field in a collection that has only one value as a result. Notice it sets it as a drop down option rather than populating the field. What am I missing here?
Looks like this:
Text field:
Lookup rule. Notice the 'as new row' checkbox is grayed out:
Thanks in advance. I'm out of ideas so I figured I'd serve it up in case anyone wants some easy points :)
Question
Question
Forms 11 New Designer - Lookup does not populate when only 1 result
Replies
Hi Chris,
Check this post out:
https://answers.laserfiche.com/questions/149006/Can-a-table-dynamically-add-rows
The issue seems similar to yours.
Thanks, this pointed me in the right direction. For clarification the issue is that doing a lookup in a collection doesn't want to lookup on data outside that collection. I had to add a field and use formula ( =EmpID ) and then do the lookup. The 'as new rows' checkbox is still grayed out but the data is populating.
Thanks for the assist :)
To have the "as new rows" all lookup fields have to be outside of the table/collection because forms is using each row's date field here to populate the individual row's lookups (at least i'm assuming the ">Variable" names are referencing the table)
yes they are, a collection with no label. thanks for the clarification
The field still does not populate when only one result. This seems like a field issue rather than lookup issue. Both variables used by the lookup are within the collection.
@Zachary St. Louis is this intended behavior?
Looks like this:
The lookup literally only returns one result:
EDIT: The lookup loaded the values correctly when the data type matched. Woo hoo! The returned value is an int and I had the Form field as a text field. I don't recall this being an issue in the past but does seem logical.