Views Preview shows error but views page with autocomplete works fine [#2042631]

In using the autocomplete exposed filter, during the view build the preview shows the following error:

Field with autocomplete results is not selected for "Selected Field" filter.

"Selected Field" is the field currently selected for autocomplete. In my view I am using a text field. While not preventing expected functionality on the actual view page, it did result in spending 20 minutes trying figure out what I had done wrong. When just going to the view page to see what error was shown, there is no error and the autocomplete field works as expected.

Any chance we could get the autocomplete error fixed for the view preview as this would greatly speed up development. Thanks in advance.

If there is any other information I can provide to clarify please let me know.

Comments

Comment #1

fregan CreditAttribution: fregan commented 15 July 2013 at 21:21

Priority:

Normal

» Major

Actually... If i try to have more then one page in a view that each have a autocomplete exposed filter, I am unable to save the view because of these errors. Upping priority as we really should be able to have multiple view displays with autocompletes.

Comment #2

fregan CreditAttribution: fregan commented 15 July 2013 at 23:57

Priority:

Major

» Minor

After playing around a bit with the views and starting to understand the inner workings of the module I was able to find out that where the issue is. I can safely have multiple displays in the view only when I add all the fields that will be autocomplete fields to the master view. Including the fields in the display your using them in is not enough. This seems a little backwards but is a reasonable workaround. It should be noted somewhere in the documentation that if you have a view with multiple displays then all fields used for autocomplete need to be added to the master display.

Comment #3

vasike

Ramnicu Valcea

CreditAttribution: vasike commented 16 July 2013 at 06:32

Status:

Active

» Closed (duplicate)

it seems duplicate of #1748900: Field with autocomplete results is not selected.

Comment #4

fregan CreditAttribution: fregan commented 16 July 2013 at 15:19

Hi Vasike. Yes after some digging through I believe it is the same issue. It seems like the master display fields are an important part in making sure you do not generate errors with multiple displays. After talking with a co-worker he informed me that it is a common thing to need all of the fields in the master display for Views in general. I was not aware of this so my apologies on the bug report.

It would be nice though if you could a little disclaimer on the project page noting to people that all the fields used for autocomplete need to be in the master display of the view. Possibly in the Tips & Tricks paragraph.

Thank you for your work on this module, it has made creating dashboards for our current project very easy for the end user.