Hi everyone,

I explain my problem, but without expecting a solution, as I understand that is no bug/issue there.

My problem is that I had all the glossary terms in the Classic glossary, with some workflows.

Then when they released the new version, more oriented to data products and data mesh, I started to migrate the glossary terms to each business domain, but 1) workflows cannot be applied to new portal items (glossary terms from a business domain) and 2) the terms cannot be linked to data assets in the data map, only to data products (a container for data assets)

FYI, the Enterprise Glossary is made up of all the “Approved” glossary terms in each Business Domain, and this confused me a bit at first.

In other hand, if you go for the classic portal you loose all data quality functionalities inside data products. The classic one don’t have data quality tracking.

I think Microsoft should explain well what each portal is for and how to use it and simplify life for everyone.

For example, I think they should make it clear that we should reserve the new portal only if you use Fabric and a Datamesh approach and for the rest of the architectures/uses, it is better to use the classic one.

Or eventually unify the glossaries and data asset’s data quality to have better experience.

Thanks!

David

​Hi everyone, I explain my problem, but without expecting a solution, as I understand that is no bug/issue there. My problem is that I had all the glossary terms in the Classic glossary, with some workflows.Then when they released the new version, more oriented to data products and data mesh, I started to migrate the glossary terms to each business domain, but 1) workflows cannot be applied to new portal items (glossary terms from a business domain) and 2) the terms cannot be linked to data assets in the data map, only to data products (a container for data assets) FYI, the Enterprise Glossary is made up of all the “Approved” glossary terms in each Business Domain, and this confused me a bit at first. In other hand, if you go for the classic portal you loose all data quality functionalities inside data products. The classic one don’t have data quality tracking. I think Microsoft should explain well what each portal is for and how to use it and simplify life for everyone.For example, I think they should make it clear that we should reserve the new portal only if you use Fabric and a Datamesh approach and for the rest of the architectures/uses, it is better to use the classic one.Or eventually unify the glossaries and data asset’s data quality to have better experience. Thanks!David    Read More

​