Forum Discussion
Linking Data Fields to Glossary
Hello Gaz31,
I am hoping this will be addressed as part of the Data Observability feature, which is in preview right now.
https://learn.microsoft.com/en-us/purview/whats-new#data-governance-2
I recommend keeping an eye on the What’s New in Microsoft Purview page for the latest updates and feature rollouts.
Regards,
PI
Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.
Yes, I'm encountering a similar issue with glossary term linkage in Purview.
Despite having the updated glossary visible under the unified catalog, the data map still seems to reference an older glossary version when attempting to link terms to fields within data assets.
I'd really appreciate hearing from others in the community, especially if you've found a workaround or have insights into the roadmap for resolving this.
Is there any update from the product team on aligning glossary references across the platform without duplicating and maintaining multiple versions?
Looking forward to learning from your experiences!
I don't know what they're doing, but there are two glossary options: the one in the classic portal, where you could create different glossaries and assign terms to assets, and the one in the new portal, where you can link to data products but not to data assets.
And these two glossary options aren't connected; they're different things.
I had the old glossary full and transferred it to the new one, then I saw that it couldn't be linked to the data asset... 😣
I'm not entirely clear on all these changes on Microsoft's part, to be honest.