'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft Lists Managed Metadata Changing to Auto Tags:display
Question details
Users are experiencing an issue where imported managed metadata values unexpectedly change to 'Auto Tags:display' in Microsoft Lists or SharePoint.
- Product
- SharePoint and Microsoft Lists
- Device & OS
- not provided
- Scenario
- Importing or linking taxonomy terms within a SharePoint list or Microsoft List.
- Observed behavior
- The managed metadata value incorrectly displays as 'Auto Tags:display', indicating a processing or linking error with the taxonomy terms.
Ensure you have SharePoint Admin or Site Owner permissions to access the site's TaxonomyHiddenList and the SharePoint Admin Center Term Store.
Verify TaxonomyHiddenList and Recreate Terms in Term Store
Identify broken links by checking the hidden taxonomy list and test manual term creation in the admin center to rule out import errors.
When metadata displays as 'Auto Tags:display', it usually points to a synchronization issue between your imported terms and the site's cached taxonomy list.
Navigate to your SharePoint site and append '/Lists/TaxonomyHiddenList/' to the site URL (e.g., http://YourSharePointSite/Lists/TaxonomyHiddenList/) to check if the terms are properly cached.
Log in to the SharePoint Admin Center, and navigate to Content Services, then click on Term Store.
Manually insert new taxonomy terms within the Term Store rather than importing them, and apply them to your list to see if they display correctly.
Test with a New Term Set and Site
Isolate the problem by creating a new term set or testing the metadata on a completely new SharePoint site.
Looking for a Seamless Document Management Experience? Try WPS Office
While troubleshooting complex backend metadata issues in SharePoint and Microsoft Lists, you might also need a reliable, lightweight productivity suite for your everyday document work. WPS Office is a powerful and free alternative to Microsoft Office, offering excellent compatibility and a user-friendly interface.
- 1. Download and Install: Visit the official WPS Office website to download the free suite and follow the straightforward installation instructions.
- 2. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Word, Excel, or PowerPoint files without losing formatting.
- 3. Edit and Save: Use the familiar tools to edit your documents and save them locally or upload them to your preferred cloud platform.
Frequently Asked Questions
What does 'Auto Tags:display' mean in Microsoft Lists?
It typically indicates a synchronization, formatting, or linking error between the imported taxonomy terms and the SharePoint site's hidden taxonomy list, causing the metadata column to fail to render the term name correctly.
How do I access the TaxonomyHiddenList in SharePoint?
You can access it by appending '/Lists/TaxonomyHiddenList/' to the end of your specific SharePoint site URL. This directory allows site administrators to view the cached taxonomy terms for that site.
Why should I test my managed metadata on a new SharePoint site?
Testing on a completely new site helps you isolate the problem. It determines if the metadata linking issue is widespread across your entire tenant's Term Store or isolated to a corrupted list configuration on one specific site.
