Behavior change to look up fields in SharePoint list quick edit view

%3CLINGO-SUB%20id%3D%22lingo-sub-985398%22%20slang%3D%22en-US%22%3EBehavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985398%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20just%20started%20my%20working%20week%20to%20find%20that%20when%20trying%20to%20manually%20type%20in%20a%20value%20in%20a%20lookup%20field%20won't%20work%20anymore%20while%20in%20quick%20edit%20view.%20It%20is%20now%20forcing%20me%20to%20click%20with%20the%20mouse%20to%20bring%20up%20the%20list%2C%20to%20then%20scroll%20and%20select.%20This%20is%20very%20painful%20compared%20with%20being%20able%20to%20type%20in%20the%20first%20three%20to%20four%20characters%20and%20then%20select%20what%20I%20want%20without%20having%20to%20use%20the%20mouse.%3C%2FP%3E%3CP%3EIs%20this%20a%20glitch%20with%20a%20recent%20update%20since%20the%20end%20of%20October%2C%20or%20a%20deliberate%20change%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20it%20stands%2C%20this%20means%20that%20I%20have%20to%20manually%20scroll%20through%20a%20list%20of%20over%20800%20items%20on%20a%20number%20of%20fields%20as%20they%20are%20linked%20to%20other%20SharePoint%20lists.%20I%20don't%20think%20it%20is%20as%20much%20of%20an%20issue%20for%20drop-downs%20that%20have%20only%203-4%20options%20in%20them%2C%20but%20this%20is%20not%20workable%20for%20Lookup%20columns%20that%20are%20referring%20to%20lots%20of%20data%20on%20other%20lists.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20tried%20three%20different%20browsers%20(Chrome%2C%20Mozilla%20and%20IE)%20with%20all%20three%20exhibiting%20the%20same%20behavior.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-985398%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELists%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989837%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989837%22%20slang%3D%22en-US%22%3EIs%20anyone%20else%20experiencing%20this%3F%20Surely%20others%20are%20using%20lookup%20fields%20that%20link%20multiple%20SharePoint%20lists.%20I%20would%20really%20like%20to%20know%20if%20this%20is%20a%20bug%20that%20needs%20fixing%2C%20or%20if%20developers%20for%20SharePoint%20have%20decided%20that%20this%20is%20how%20lookup%20fields%20are%20going%20to%20work....Is%20there%20a%20place%20I%20should%20go%20to%20find%20info%20on%20latest%20updates%2C%20or%20is%20there%20a%20setting%20that%20I%20need%20to%20adjust%3F%20I%20can't%20seem%20to%20find%20anything%20to%20help%20at%20this%20stage.%20Any%20help%20or%20info%20would%20be%20appreciated.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-995774%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-995774%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446422%22%20target%3D%22_blank%22%3E%40LabDude09%3C%2FA%3E%26nbsp%3B-%20yes%20we%20started%20noticing%20this%20issues%20this%20week%20as%20well%20for%20both%20choice%20and%20lookup%20columns%20in%20SPO.%20Any%20resolution%20or%20workaround%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-998647%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-998647%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126108%22%20target%3D%22_blank%22%3E%40Greg%20Gieseke%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20reply%20but%20unfortunately%20at%20this%20stage%20there%20are%20no%20changes%20or%20workarounds.%20The%20closest%20I%20can%20come%2C%20is%20to%20copy%20data%20into%20the%20next%20set%20of%20rows%20that%20sits%20in%20close%20proximity%20to%20the%20data%20I%20need%20in%20the%20list%20that%20is%20being%20looked%20up%20(sorry%20if%20that%20doesn't%20make%20sense)%2C%20and%20then%20go%20back%20and%20modify%20to%20the%20correct%20data.%20What%20would%20normally%20take%20me%20one%20or%20two%20minutes%20to%20add%20data%20to%20a%20list%2C%20is%20now%20taking%20upwards%20of%205-10%20minutes%2C%20which%20is%20far%20from%20ideal%20in%20a%20work%20environment%20that%20is%20high%20paced.%20Hopefully%20it%20is%20temporary%2C%20but%20if%20anyone%20knows%20how%20to%20get%20the%20attention%20of%20SharePoint%20developers%20so%20that%20they%20can%20look%20into%20it%2C%20please%20let%20me%20know%20and%20I%20will%20follow%20it%20up%20with%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1002324%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1002324%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446422%22%20target%3D%22_blank%22%3E%40LabDude09%3C%2FA%3E%26nbsp%3B-%20I%20opened%20a%20ticket%20and%20they%20claimed%20that%20nothing%20has%20changed%20and%20it%20has%20functioned%20this%20way%20for%20at%20least%20the%20past%203%20years.%20They%20essentially%20claimed%20that%20me%20and%20my%20internal%20customers%20are%20misguided%20in%20how%20we%20thought%20the%20quick%20edit%20with%20choice%20and%20lookup%20columns%20used%20to%20work%20in%20quick%20edit%20just%20a%20few%20short%20weeks%20ago.%20Unfortunately%20whatever%20%22didn't%22%20change%2C%20changed%20in%20all%20sites%20and%20site%20collections%20so%20there%20isn't%20any%20way%20for%20me%20to%20prove%20otherwise.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1003240%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1003240%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126108%22%20target%3D%22_blank%22%3E%40Greg%20Gieseke%3C%2FA%3E-%20thanks%20for%20helping%20follow%20up%20on%20this.%20It%20is%20very%20disheartening%20to%20hear%20that%20this%20is%20their%20response....Could%20you%20please%20guide%20me%20as%20to%20where%20I%20can%20open%20my%20own%20ticket%3F%20I%20am%20thinking%20that%20if%20more%20people%20raise%20this%20directly%2C%20they%20may%20start%20to%20look%20into%20it%2C%20or%20perhaps%20acknowledge%20that%20something%20has%20changed.....%3CBR%20%2F%3EMy%20only%20other%20thoughts%2C%20are%20whether%20a%20global%20setting%20has%20been%20changed%20by%20the%20administrator%2Fowner%20of%20SharePoint%20account%20(I%20am%20not%20sure%20how%20all%20this%20works%2C%20but%20I%20would%20be%20surprised%20if%20the%20guys%20who%20oversee%20SharePoint%20for%20our%20company%2C%20would%20have%20bothered%20to%20alter%20any%20setting%20that%20would%20change%20something%20like%20this).%20I%20am%20still%20learning%20about%20permissions%20etc.%3C%2FP%3E%3CP%3EI'm%20really%20wishing%20I%20had%20kept%20some%20screen%20shots%20of%20me%20working%20with%20my%20lists%20so%20we%20had%20actual%20proof....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELastly%2C%20it%20doesn't%20make%20sense%20to%20me%2C%20for%20the%20lookup%20columns%20to%20behave%20the%20way%20they%20currently%20do.%20Why%20would%20you%20want%20to%20have%20to%20scroll%20through%20hundreds%20of%20rows%20of%20data%20to%20make%20one%20selection.%20The%20whole%20idea%20of%20a%20lookup%20column%2C%20is%20to%20link%20the%20lists%20(like%20tables%20in%20a%20traditional%20database)%20which%20I%20would%20imagine%20in%20most%20cases%2C%20are%20not%20small%20lists.%20A%20drop%20down%20selection%2C%20I%20can%20understand%2C%20but%20not%20a%20look%20up%20column.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015644%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015644%22%20slang%3D%22en-US%22%3EAs%20an%20update%20to%20this%2C%20I%20have%20started%20work%20this%20morning%20following%20all%20my%20usual%20steps%20with%20opening%20my%20SharePoint%20Lists%2C%20but%20for%20some%20reason%20when%20I%20open%20lists%20that%20don't%20contain%20any%20JSON%20formatting%2C%20they%20open%20in%20classic%20experience%3F%3F%20I%20don't%20know%20why%2C%20but%20using%20the%20lists%20this%20way%2C%20enables%20the%20Autocomplete%20function%20to%20work%20again.....%3CBR%20%2F%3ESo%20at%20the%20moment%2C%20as%20far%20as%20I%20can%20see%2C%20the%20issue%20I%20have%20been%20having%20is%20happening%20when%20editing%20a%20list%20in%20Modern%20view.%20While%20I%20prefer%20that%20I%20can%20continue%20using%20modern%20view%20over%20classic%2C%20at%20least%20I%20can%20now%20enter%20data%20efficiently.%20I%20would%20still%20say%20that%20this%20issue%20isn't%20resolved%20until%20it%20is%20possible%20for%20the%20Autocomplete%20function%20to%20work%20in%20Modern%20view%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015664%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015664%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126108%22%20target%3D%22_blank%22%3E%40Greg%20Gieseke%3C%2FA%3E%26nbsp%3BJust%20in%20case%20you%20haven't%20been%20keeping%20an%20eye%20on%20this%20discussion%20anymore%2C%20I%20have%20accidentally%20stumbled%20on%20a%20workaround.%20You%20can%20enter%20data%20as%20per%20normal%20(prior%20to%20the%20change%20a%20few%20weeks%20ago)%20by%20using%20classic%20experience.%20See%20my%20last%20reply%20for%20more%20info%2C%20but%20here%20is%20a%20screen%20shot%20to%20show%20what%20is%20happening%20with%20classic%20experience%2C%20that%20was%20happening%20while%20in%20Modern%20view%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20321px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F157770iD1461CF767A7A220%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22autocomplete.png%22%20title%3D%22autocomplete.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1017303%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1017303%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446422%22%20target%3D%22_blank%22%3E%40LabDude09%3C%2FA%3E%26nbsp%3B-%20thanks%20for%20sharing%20a%20workaround.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1014023%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1014023%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20bumping%20this%20again%20to%20see%20if%20others%20have%20been%20experiencing%20the%20same%20issue.%20I%20unfortunately%20don't%20have%20any%20screen%20shots%20as%20proof%20that%20the%20behaviour%20has%20changed%20recently%2C%20but%20I%20have%20spent%20the%20last%20six%20months%20building%20lists%20and%20entering%20thousands%20of%20rows%20of%20data%20in%2C%20where%20I%20have%20been%20able%20to%20type%20it%20in%20and%20allow%20SharePoint%20to%20start%20displaying%20the%20closest%20match.%20I%20could%20then%20press%20the%20tab%20button%20to%20move%20to%20the%20next%20column%2Ffield.%26nbsp%3B%3C%2FP%3E%3CP%3EGiven%20look%20up%20columns%20are%20designed%20to%20link%20lists%20together%2C%20and%20the%20possibility%20of%20these%20lists%20growing%20is%20extremely%20high%2C%20why%20would%20you%20want%20to%20be%20forced%20to%20scroll%20through%20thousands%20of%20data%20points%20in%20a%20drop%20down%20list%20every%20time%20you%20need%20to%20select%20data%20for%20the%20list%20you%20are%20in%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1222096%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1222096%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446422%22%20target%3D%22_blank%22%3E%40LabDude09%3C%2FA%3EI%20noticed%20this%20as%20well%20and%20have%20been%20waiting%20for%20Microsoft%20to%20address%20the%20autocomplete%20in%20the%20Modern%20view.%20Has%20there%20been%20any%20action%20or%20response%20from%20Microsoft%20regarding%20this%3F%20We%20also%20have%20lookup%20fields%20with%20hundreds%20of%20items%20and%20this%20continues%20to%20be%20an%20issue.%20To%20flip%20all%20of%20the%20lists%20to%20the%20classic%20experience%20will%20be%20a%20bit%20time%20consuming%20and%20frustrating%20for%20the%20average%20users%20on%20my%20team.%20I%20have%20been%20unable%20to%20find%20anything%20with%20a%20response%20from%20Microsoft%20on%20this%20particular%20issue.%20Thanks%20so%20much!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1657595%22%20slang%3D%22en-US%22%3ERe%3A%20Behavior%20change%20to%20look%20up%20fields%20in%20SharePoint%20list%20quick%20edit%20view%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1657595%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551787%22%20target%3D%22_blank%22%3E%40TMercier%3C%2FA%3E%26nbsp%3Bhave%20not%20done%20anything%20in%20Sharepoint%20for%20a%20while%20and%20went%20to%20set%20up%20a%20new%20list.%26nbsp%3B%20Shocking%20that%20this%20could%20be%20the%20behavior.%26nbsp%3B%20Will%20try%20your%20work%20around.%26nbsp%3B%20Thanks%20so%20much%20for%20sharing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I have just started my working week to find that when trying to manually type in a value in a lookup field won't work anymore while in quick edit view. It is now forcing me to click with the mouse to bring up the list, to then scroll and select. This is very painful compared with being able to type in the first three to four characters and then select what I want without having to use the mouse.

Is this a glitch with a recent update since the end of October, or a deliberate change?

 

As it stands, this means that I have to manually scroll through a list of over 800 items on a number of fields as they are linked to other SharePoint lists. I don't think it is as much of an issue for drop-downs that have only 3-4 options in them, but this is not workable for Lookup columns that are referring to lots of data on other lists.

I have tried three different browsers (Chrome, Mozilla and IE) with all three exhibiting the same behavior.

11 Replies
Highlighted
Is anyone else experiencing this? Surely others are using lookup fields that link multiple SharePoint lists. I would really like to know if this is a bug that needs fixing, or if developers for SharePoint have decided that this is how lookup fields are going to work....Is there a place I should go to find info on latest updates, or is there a setting that I need to adjust? I can't seem to find anything to help at this stage. Any help or info would be appreciated.
Highlighted

@LabDude09 - yes we started noticing this issues this week as well for both choice and lookup columns in SPO. Any resolution or workaround?

Highlighted

@Greg Gieseke Thanks for the reply but unfortunately at this stage there are no changes or workarounds. The closest I can come, is to copy data into the next set of rows that sits in close proximity to the data I need in the list that is being looked up (sorry if that doesn't make sense), and then go back and modify to the correct data. What would normally take me one or two minutes to add data to a list, is now taking upwards of 5-10 minutes, which is far from ideal in a work environment that is high paced. Hopefully it is temporary, but if anyone knows how to get the attention of SharePoint developers so that they can look into it, please let me know and I will follow it up with them.

Highlighted

@LabDude09 - I opened a ticket and they claimed that nothing has changed and it has functioned this way for at least the past 3 years. They essentially claimed that me and my internal customers are misguided in how we thought the quick edit with choice and lookup columns used to work in quick edit just a few short weeks ago. Unfortunately whatever "didn't" change, changed in all sites and site collections so there isn't any way for me to prove otherwise.

Highlighted

@Greg Gieseke- thanks for helping follow up on this. It is very disheartening to hear that this is their response....Could you please guide me as to where I can open my own ticket? I am thinking that if more people raise this directly, they may start to look into it, or perhaps acknowledge that something has changed.....
My only other thoughts, are whether a global setting has been changed by the administrator/owner of SharePoint account (I am not sure how all this works, but I would be surprised if the guys who oversee SharePoint for our company, would have bothered to alter any setting that would change something like this). I am still learning about permissions etc.

I'm really wishing I had kept some screen shots of me working with my lists so we had actual proof....

 

Lastly, it doesn't make sense to me, for the lookup columns to behave the way they currently do. Why would you want to have to scroll through hundreds of rows of data to make one selection. The whole idea of a lookup column, is to link the lists (like tables in a traditional database) which I would imagine in most cases, are not small lists. A drop down selection, I can understand, but not a look up column.

Highlighted

Just bumping this again to see if others have been experiencing the same issue. I unfortunately don't have any screen shots as proof that the behaviour has changed recently, but I have spent the last six months building lists and entering thousands of rows of data in, where I have been able to type it in and allow SharePoint to start displaying the closest match. I could then press the tab button to move to the next column/field. 

Given look up columns are designed to link lists together, and the possibility of these lists growing is extremely high, why would you want to be forced to scroll through thousands of data points in a drop down list every time you need to select data for the list you are in?

Highlighted
As an update to this, I have started work this morning following all my usual steps with opening my SharePoint Lists, but for some reason when I open lists that don't contain any JSON formatting, they open in classic experience?? I don't know why, but using the lists this way, enables the Autocomplete function to work again.....
So at the moment, as far as I can see, the issue I have been having is happening when editing a list in Modern view. While I prefer that I can continue using modern view over classic, at least I can now enter data efficiently. I would still say that this issue isn't resolved until it is possible for the Autocomplete function to work in Modern view
Highlighted

@Greg Gieseke Just in case you haven't been keeping an eye on this discussion anymore, I have accidentally stumbled on a workaround. You can enter data as per normal (prior to the change a few weeks ago) by using classic experience. See my last reply for more info, but here is a screen shot to show what is happening with classic experience, that was happening while in Modern view;

 

autocomplete.png

Highlighted

@LabDude09 - thanks for sharing a workaround. 

Highlighted

@LabDude09I noticed this as well and have been waiting for Microsoft to address the autocomplete in the Modern view. Has there been any action or response from Microsoft regarding this? We also have lookup fields with hundreds of items and this continues to be an issue. To flip all of the lists to the classic experience will be a bit time consuming and frustrating for the average users on my team. I have been unable to find anything with a response from Microsoft on this particular issue. Thanks so much!

Highlighted

@TMercier have not done anything in Sharepoint for a while and went to set up a new list.  Shocking that this could be the behavior.  Will try your work around.  Thanks so much for sharing.