Key filters? list and libraries reverted to classic experience.

%3CLINGO-SUB%20id%3D%22lingo-sub-1166781%22%20slang%3D%22en-US%22%3EKey%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1166781%22%20slang%3D%22en-US%22%3E%3CP%3ERecently%20all%20of%20our%20classical%20sites%20have%20reverted%20to%20the%20classic%20experience%20in%20list%20and%20libraries.%20We%20haven'r%20ruled%20out%20that%20there%20is%20some%20admin%20that%20has%20made%20this%20change%2C%20but%20we%20find%20it%20highly%20unlikely.%20And%20in%20connection%20to%20this%2C%20we've%20also%20gotten%20a%20%22Key%20filters%22%20bos%20in%20the%20left%20side%20pane%20of%20the%20pages.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20experienced%20this%3F%20Is%20this%20connected%20to%20some%20change%20that%20MS%20has%20made%20recently%20or%20is%20it%20something%20in%20our%20tenant%20that%20has%20been%20changed%20(somehow)%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22NiclasDahl_0-1581433674525.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F170349iCB9618F78CE68380%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22NiclasDahl_0-1581433674525.png%22%20alt%3D%22NiclasDahl_0-1581433674525.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1166781%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%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-1166863%22%20slang%3D%22en-US%22%3ERe%3A%20Key%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1166863%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307336%22%20target%3D%22_blank%22%3E%40NiclasDahl%3C%2FA%3E%26nbsp%3B%20I%20have%20also%20experienced%20this%20on%20Publishing%20sites%20on%20our%20tenant.%20I%20am%20the%20admin%20and%20I%20am%20certain%20that%20our%20tenant%20is%20set%20to%20the%20modern%20experience%20for%20document%20libraries.%20Later%20in%20the%20day%20on%20February%2010th%20my%20users%20have%20reported%20that%20their%20libraries%20are%20reverting%20to%20a%20classic%20view.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20the%20'fix'%20has%20been%20for%20the%20user%20to%20click%20'exit%20classic%20experience'%20on%20the%20bottom%20of%20the%20left%20rail.%20Then%20the%20other%20libraries%20appear%20as%20Modern%20as%20they%20should.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20noticed%20the%20'key%20filters'%2C%20but%20I%20will%20let%20you%20know%20if%20I%20do.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1167171%22%20slang%3D%22en-US%22%3ERe%3A%20Key%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1167171%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20investigating%20this%20behavior%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1167455%22%20slang%3D%22en-US%22%3ERe%3A%20Key%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1167455%22%20slang%3D%22en-US%22%3EIs%20this%20related%20to%20something%20rolled%20out%20recently%20that%20could%20be%20causing%20this%20behavior%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1167603%22%20slang%3D%22en-US%22%3ERe%3A%20Key%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1167603%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20is%20now%20solved.%20Please%20validate.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20identified%20a%20recent%20change%20that%20introduced%20this%20behavior.%20We%20have%20reverted%20the%20change%20to%20address%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1168702%22%20slang%3D%22en-US%22%3ERe%3A%20Key%20filters%3F%20list%20and%20libraries%20reverted%20to%20classic%20experience.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1168702%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63424%22%20target%3D%22_blank%22%3E%40Bruno%20Aleixo%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThings%20are%20back%20to%20normal%20now%2C%20thanks%20for%20speedy%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Recently all of our classical sites have reverted to the classic experience in list and libraries. We haven'r ruled out that there is some admin that has made this change, but we find it highly unlikely. And in connection to this, we've also gotten a "Key filters" bos in the left side pane of the pages. 

 

Has anyone else experienced this? Is this connected to some change that MS has made recently or is it something in our tenant that has been changed (somehow)?

NiclasDahl_0-1581433674525.png

 

5 Replies

@NiclasDahl  I have also experienced this on Publishing sites on our tenant. I am the admin and I am certain that our tenant is set to the modern experience for document libraries. Later in the day on February 10th my users have reported that their libraries are reverting to a classic view.

 

So far the 'fix' has been for the user to click 'exit classic experience' on the bottom of the left rail. Then the other libraries appear as Modern as they should. 

 

I haven't noticed the 'key filters', but I will let you know if I do.

We are currently investigating this behavior

Is this related to something rolled out recently that could be causing this behavior?

The issue is now solved. Please validate.

 

We have identified a recent change that introduced this behavior. We have reverted the change to address the issue.

@Bruno Aleixo 

 

Things are back to normal now, thanks for speedy fix.