External users cannot see info in metadata field

%3CLINGO-SUB%20id%3D%22lingo-sub-1754071%22%20slang%3D%22en-US%22%3EExternal%20users%20cannot%20see%20info%20in%20metadata%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1754071%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20created%20a%20document%20library%20and%20invited%20a%20guest%20user%20with%20edit-access.%20Created%20a%20customized%20meta-data%20field%20and%20added%20some%20terms%20in%20the%20termset.%20Then%20added%20three%20files%20and%20attached%20the%20terms%20to%20them.%3C%2FP%3E%3CP%3EThe%20owner%20%26amp%3B%20other%20internal%20user%20can%20view%20the%20terms%20that%20has%20been%20set%20on%20the%20items%20in%20the%20library.%20But%20guest%20users%20cannot.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20else%20reproduce%20this%20strange%20behavior%20and%20what%20could%20possibly%20be%20wrong%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20I%20just%20reproduced%20this%20in%20another%20tenant.%20No%20solution%20though.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1754071%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1757197%22%20slang%3D%22en-US%22%3ERe%3A%20External%20users%20cannot%20see%20info%20in%20metadata%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1757197%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20issue%20is%20now%20gone%20without%20me%20doing%20anything.%20Looks%20like%20Microsoft%20had%20som%20issues%20yeasterday.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I just created a document library and invited a guest user with edit-access. Created a customized meta-data field and added some terms in the termset. Then added three files and attached the terms to them.

The owner & other internal user can view the terms that has been set on the items in the library. But guest users cannot. 

 

Can anyone else reproduce this strange behavior and what could possibly be wrong?

 

Edit: I just reproduced this in another tenant. No solution though.

 

1 Reply
Highlighted

This issue is now gone without me doing anything. Looks like Microsoft had som issues yesterday.