SharePoint Modern Lists do not support Metadata Lookup Fields

%3CLINGO-SUB%20id%3D%22lingo-sub-1829753%22%20slang%3D%22en-US%22%3ESharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1829753%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20seeing%20this%20issue%20where%20existing%20SharePoint%20lists%20using%20the%20Modern%20interface%20do%20not%20support%20Metadata%20lookup%20fields%20defined%20in%20the%20Termstore.%26nbsp%3B%20When%20we%20try%20to%20lookup%20a%20value%20we%20get%20the%20error%20%22We%20are%20facing%20issues%20in%20rendering%20the%20MMD%20tree%20-%20Unable%20to%20get%20termset%22%26nbsp%3B%20however%20if%20you%20click%20the%20%22Return%20to%20classic%22%20link%20at%20the%20bottom%20it%20works%20fine.%26nbsp%3B%20Is%20there%20a%20solution%20for%20getting%20the%20lookup%20fields%20to%20work%20in%20Modern%3F%26nbsp%3B%20Thanks%20for%20the%20help%26nbsp%3B%20Ivan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1829753%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-1829927%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1829927%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722337%22%20target%3D%22_blank%22%3E%40IvanCole-dxcecl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20posted%20the%20same%20issue%20this%20morning%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsharepoint%2Fnew-managed-metadata-picker-is-not-working%2Fm-p%2F1827263%2Fhighlight%2Ftrue%23M45914%22%20target%3D%22_blank%22%3Enew-managed-metadata-picker-is-not-working%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20one%20seems%20to%20have%20the%20issue%2C%20nothing%20in%20the%20health%20dashboard.%20I've%20sent%20the%20issue%20with%20the%20%22Report%20an%20issue%22%20from%20the%20dashboard.%20Nothing%20from%20Microsoft...%20Does%20not%20seems%20to%20be%20very%20important%20that%20MMD%20is%20not%20working...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20I've%20tested%20the%20issue%20in%203%20other%20tenants%20from%20my%20customers.%20They%20all%20have%20the%20issue...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1829961%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1829961%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F24099%22%20target%3D%22_blank%22%3E%40Martin%20Coupal%3C%2FA%3E%26nbsp%3B%20thanks%20for%20confirming%20this%20is%20an%20issue%20as%20well.%26nbsp%3B%20At%20least%20I%20am%20not%20crazy.%26nbsp%3B%20I%20thought%20that%20maybe%20adding%20permissions%20to%20the%20term%20store%20might%20have%20helped%20but%20to%20no%20avail.%26nbsp%3B%20%26nbsp%3BPer%20this%20article.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.spguides.com%2Fterm-store-sharepoint%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.spguides.com%2Fterm-store-sharepoint%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EIt%20would%20be%20great%20if%20Microsoft%20would%20respond%20to%20the%20thread%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIvan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1830444%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1830444%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722337%22%20target%3D%22_blank%22%3E%40IvanCole-dxcecl%3C%2FA%3E%26nbsp%3BI%20did%20some%20tests%20and%20found%20out%20it%20was%20related%20to%20an%20access%20issue.%20However%2C%20there%20was%20no%20change%20made%20to%20the%203%20tenants%20I%20found%20the%20issue%2C%20so%20I'm%20100%25%20it%20is%20related%20to%20a%20change%20they%20made.%20I%20have%20one%20tenant%20that%20do%20not%20have%20the%20issue....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20If%20it%20was%20related%20to%20a%20permission%20issue%20on%20the%20termstore%2C%20it%20would%20not%20be%20working%20when%20using%20the%20standard%20(legacy)%20picker....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20call%20creating%20the%20issue%20is%20the%20following%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmytenant.sharepoint.com%2Fsites%2Fdemo-dept-finances%2F_api%2Fv2.1%2FtermStore%2FtermGroups%2Fxxxxxxx%2FtermSets%2Fxxxxxxx%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmytenant.sharepoint.com%2Fsites%2Fdemo-dept-finances%2F_api%2Fv2.1%2FtermStore%2FtermGroups%2Fxxxxxxx%2FtermSets%2Fxxxxxxx%2F%3C%2FA%3E%3CSTRONG%3EgetLegacyChildren()%3C%2FSTRONG%3E%3F%24top%3D50%3C%2FP%3E%3CP%3EIt%20returns%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22b%22%3E%7B%3C%2FSPAN%3E%3CSPAN%20class%3D%22blockInner%22%3E%3CSPAN%20class%3D%22kvov%20objProp%22%3E%22%3CSPAN%20class%3D%22k%22%3Eerror%3C%2FSPAN%3E%22%3A%26nbsp%3B%3CSPAN%20class%3D%22b%22%3E%7B%3C%2FSPAN%3E%22%3CSPAN%20class%3D%22k%22%3Ecode%3C%2FSPAN%3E%22%3A%26nbsp%3B%3CSPAN%20class%3D%22s%22%3E%22%3CSPAN%3EaccessDenied%3C%2FSPAN%3E%22%3C%2FSPAN%3E%2C%22%3CSPAN%20class%3D%22k%22%3Emessage%3C%2FSPAN%3E%22%3A%26nbsp%3B%3CSPAN%20class%3D%22s%22%3E%22%3CSPAN%3EEnd%20point%20cannot%20be%20called%20by%20the%20current%20user%3C%2FSPAN%3E%22%3C%2FSPAN%3E%3CSPAN%20class%3D%22b%22%3E%7D%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22b%22%3E%7D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22b%22%3EIf%20I%20change%20the%20rest%20call%20to%20this%2C%20it%20will%20return%20all%20terms%20successfully%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22b%22%3E%3CA%20href%3D%22https%3A%2F%2Fmytenant.sharepoint.com%2Fsites%2Fdemo-dept-finances%2F_api%2Fv2.1%2FtermStore%2FtermGroups%2Fxxxxxxx%2FtermSets%2Fxxxxxxx%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmytenant.sharepoint.com%2Fsites%2Fdemo-dept-finances%2F_api%2Fv2.1%2FtermStore%2FtermGroups%2Fxxxxxxx%2FtermSets%2Fxxxxxxx%2F%3C%2FA%3E%3CSTRONG%3EChildren()%3C%2FSTRONG%3E%3F%24top%3D50%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22b%22%3EI've%20created%20a%20MS%20ticket.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1830445%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1830445%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F24099%22%20target%3D%22_blank%22%3E%40Martin%20Coupal%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%20done.%26nbsp%3B%20You%20figured%20out%20how%20to%20help%20Microsoft%20solve%20the%20bug.%26nbsp%3B%20I%20had%20also%20opened%20a%20case%20earlier%20and%20I%20attached%20your%20updated%20thread.%26nbsp%3B%20Hopefully%20a%20fix%20will%20get%20rolled%20out%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EIvan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1837647%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Modern%20Lists%20do%20not%20support%20Metadata%20Lookup%20Fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1837647%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722337%22%20target%3D%22_blank%22%3E%40IvanCole-dxcecl%3C%2FA%3E%26nbsp%3BI%20had%20opened%20a%20case%20but%20today%20it%20is%20mysteriously%20working%20fine.%26nbsp%3B%20The%20support%20engineer%20was%20not%20aware%20of%20any%20changes%20made.%20For%20now%20this%20is%20resolved.%26nbsp%3B%20Maybe%20you%20code%20hint%20helped%20Microsoft%20solve%20it.%26nbsp%3B%20Hope%20you%20version%20is%20working%20as%20well%3C%2FP%3E%3CP%3EThanks%20for%20the%20responses%20and%20help%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIvan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I am seeing this issue where existing SharePoint lists using the Modern interface do not support Metadata lookup fields defined in the Termstore.  When we try to lookup a value we get the error "We are facing issues in rendering the MMD tree - Unable to get termset"  however if you click the "Return to classic" link at the bottom it works fine.  Is there a solution for getting the lookup fields to work in Modern?  Thanks for the help  Ivan

 

8 Replies

@IvanCole-dxcecl 

I've posted the same issue this morning

new-managed-metadata-picker-is-not-working 

 

No one seems to have the issue, nothing in the health dashboard. I've sent the issue with the "Report an issue" from the dashboard. Nothing from Microsoft... Does not seems to be very important that MMD is not working...

 

Note: I've tested the issue in 3 other tenants from my customers. They all have the issue...

 

@Martin Coupal  thanks for confirming this is an issue as well.  At least I am not crazy.  I thought that maybe adding permissions to the term store might have helped but to no avail.   Per this article.  https://www.spguides.com/term-store-sharepoint/

It would be great if Microsoft would respond to the thread

 

Thanks for the reply

 

Ivan

 

 

@IvanCole-dxcecl I did some tests and found out it was related to an access issue. However, there was no change made to the 3 tenants I found the issue, so I'm 100% it is related to a change they made. I have one tenant that do not have the issue....

 

Note: If it was related to a permission issue on the termstore, it would not be working when using the standard (legacy) picker....

 

The call creating the issue is the following:

https://mytenant.sharepoint.com/sites/demo-dept-finances/_api/v2.1/termStore/termGroups/xxxxxxx/term...getLegacyChildren()?$top=50

It returns:

{"error": {"code": "accessDenied","message": "End point cannot be called by the current user"}}

 

If I change the rest call to this, it will return all terms successfully:

 

https://mytenant.sharepoint.com/sites/demo-dept-finances/_api/v2.1/termStore/termGroups/xxxxxxx/term...Children()?$top=50

 

I've created a MS ticket. 

@Martin Coupal 

 

Well done.  You figured out how to help Microsoft solve the bug.  I had also opened a case earlier and I attached your updated thread.  Hopefully a fix will get rolled out soon.

 

Thanks

Ivan

 

@IvanCole-dxcecl I had opened a case but today it is mysteriously working fine.  The support engineer was not aware of any changes made. For now this is resolved.  Maybe you code hint helped Microsoft solve it.  Hope you version is working as well

Thanks for the responses and help

 

Ivan

 

@IvanCole-dxcecl same thing for me. It is now working this morning. I had no news from support team for my ticket. Nothing also in the health dashboard... I had a look and they fixed the issue related to getLegacyChildren because they are still calling it but now it is successful...

 

Thanks for letting me know.

 

Martin.

One last thing, do you have forms having more than one managed metadata field? When I click on the first MMD picker, everything is ok. When I click on the second MMD field picker it shows for a fraction of a second and disappear.

@Martin CoupalI just tested that as well and have the same issue. But if you click again in the same field it does appear.  I can mention this in my case as well. thanks for pointing that out.