SharePoint Syntex now makes extensive use of the Term Store (Managed Metadata Services - MMS) and does so in many different ways which I will go through in this blog. When Microsoft were working on Project Cortex and before SharePoint Syntex & Viva Topics were even known, there was a big investment by the SharePoint engineering team to improve the term store. The term store when moved to SharePoint online from SharePoint on-premise was literally moved "as is" (I believe!) to the cloud by Microsoft and it came with the old slow modern UI. Adding/administering terms took ages as users had to wait for often long periods of time whilst navigating between terms, adding terms etc. It was sometimes very painful so some people would even avoid using the termstore altogether and lose the benefit to provide a unified set of terms to apply to content in Microsoft 365 that can be reused between sites/libraries. So it was great that in early 2020 Microsoft announced they had modernised the Term Store - I was instantly curious how this was going to be utilised in Project Cortex as little was still known about it.
Over the past few months there have been a number of SharePoint Syntex updates with the purpose to more closely integrate with Viva Topics. Before this the two products have been quite separated which has been odd especially as they were born from the same Project (Cortex). This blog will focus on using Syntex to generate Viva Topics.
rule to specify to remove duplicate entities, extract only a certain number of values or lines from the entity extractor value. This happens at the same time the entity extractor is invoked on the document and allows greater control of the returned values. There is a new Refine extracted info button now available in the entity extractors section of a document understanding model.
New SharePoint Syntex functionality has recently arrived in my tenant to extend the Advanced Search functionality that is available in document libraries to allow custom columns from your Syntex models…
A new update has recently came to SharePoint Syntex to allow users to create & train their own local document understanding models in Team or Communication sites. The models can…
There is now a new document card view to display extracted model information (metadata) in a tile view in libraries that have a SharePoint Syntex document understanding model (DUM) applied. When a document understanding model is applied from a Syntex Content Center to a new library there are now three options (under advanced settings) to choose the default view of the library. Users do not have to choose to have this new document card view as their default view but it looks very good!
Recently Microsoft have provided two pre-built & pre-trained models for invoices and receipts to use with invoices and receipts in your organisation. These form processing models cater for invoices and receipts that are typically common organisational documents that every organisation will likely deal with. The models have been pre-trained to extract common invoice/receipt fields. The idea is you can install these pre-built models directly from a Syntex content centre. You can then add your own invoices/receipts for the model to analyse and it will pick out common fields and setup extractors for them. You can then modify the model to select the fields to extract rather than starting from scratch.