Modernizing SharePoint Managed Metadata Services (MMS)

Chris McNulty came across this article when looking for info about the modern termstore. 
Is the classic option of 'Site Collection Access' also coming back in the modern experience? In order to share a sitecollection termgroup with other sitecollections? 

Chris McNulty  When creating a new site, some content types fail with this error: [-2146233088] [Microsoft.SharePoint.Taxonomy.ContentTypeSync.ContentTypeSyndicationException] [Field internal name 'Related_x0020_File' conflict] 

Any ideas why?

by the way, also with the "new" Managed Metadata Service it is not possible to filter those Columns in Power Automate Flow "Get Items" Actions because of misssing ODATA Filter Query Support for Taxonomy Fields. This is Annoying and the Workarounds with HTTP Request to SharePoint and REST-CAML Queries are cumbersome. Any Plans to marry MMS with Power Platform in a truly manner? 

FYI y'all,

I've contacted Microsoft Support regarding the managed metadata filtering issue. They've confirmed the issue on their end and it's now in the hands of the engineering team. No ETA yet on when the update/fix will be released, but it's in front of them and acknowledged now so I'm happy about that.

Thanks!

As an answer to AnupamFrancis mentions that it is recommended to use Power Automate instead of what it currently links to, the old "workflow settings". How do you use Content type triggered flows? I have yet to figure that out.

Also. I have now over 3 days tried to publish a content type at a customers environment and nothing happens. How and what do you need to do in order to access the content types in your environment?

Submitted a support ticket on this issue, trying to do what I can to raise awareness about this. Has anyone had any luck contacting Microsoft regarding this issue? I'd just love to have some sort of update or acknowledgment of the issue by Microsoft. Glad to see others confirm the issue on their end. I feel like the development team completely overlooked the use case of displaying the full term path, or maybe filtering just wasn't tested this way.

So the conversation ended here without any updates from Microsoft?

I have several large customers complaining about the Tree-filter on Meta-data is no longer working. And guess what, it isn't!

It has a new look which is good, but since the actual function of a filter isn't working anymore they are already thinking of swapping systems to something else. 

Please give us a heads up Microsoft that you are at least working on this one! 

As to the SPFX solution above, it is quite impressive, even if its parts are available from pnp.github. It is certainly beyond my novice skill level nor would I have two days to devote to the task if I had the skills. Hopefully, MS will incorporate this solution into Content Services in the near future.

Hello again, 

I'd like to share briefly what I've done to move on from this issue in case it benefits anyone else. I'm somewhat new to SharePoint administration and development - so bare with me if implementing this sort of customization is common sense.

With the MMD filtering being such a poor UI experience for anyone using term paths as opposed to single terms (see my above post for an example), and with no acknowledgment (that I'm aware of) of this being an issue, I decided the best thing I could do is learn how to work with SPFX and customize our experience.

If you're unfamiliar with SPFX, a google search can get you started on setting up a dev environment and creating your first webpart.

Some kind folks have made some really nice controls on pnp.GitHub.io. I used their TaxonomyPicker to create a web part that lets you choose Taxonomy terms in a tree view or by text search. I then followed this guide to share my selected terms with another webpart that displays the library and filters by the selected terms.

My second web part implements a datatable from datatables.net, I believe I followed this guide: https://www.c-sharpcorner.com/article/display-sharepoint-list-data-with-jquery-datatable-in-sharepoint-frameworkspfx/. My intention was to display the document library in a very clean fashion that's easy to filter. I added a filter row to the top of my datatable and implemented a receiver (from guide linked above) that would get the data from my TaxonomyPicker webpart and filter my MMD column appropriately. Datatables.net had plenty of information on how to customize the table.

It took me a couple of days to figure it all out and have the webparts working properly, but the UI experience for our customers (read only users) is vastly improved now with our use case. Below is an image of what the page looks like with the two web parts. I was also pleased that without any mobile-specific customization the page works really well.

I don't really mean to create a guide here - but I'm happy if this helps anyone else to continue using MMD in the way they need to without compromising on user experience.

A little disappointed this conversation has died... this feels like an important issue to me. Is there any intention of fixing the managed metadata filtering experience? This is still grieving me and my end users, it's awful to have useful functionality we've built a dependency on get ripped away.