Trimming SharePoint Version History - Minor Versions
Hello, I am a SharePoint Admin at my organization and I have been asked to reduce our total storage usage by reducing the number of versions and minor versions in our environment on all SharePoint sites. I have written a simple PowerShell script that loops through a csv file with site addresses, and runs this command per site -> New-SPOSiteFileVersionBatchDeleteJob -Identity $site.siteURL -MajorVersionLimit 100 -MajorWithMinorVersionsLimit 5 It was my understanding that for all sites in the csv file, for all document libraries on the site, and for all files in the libraries this command will reduce the file to the last 100 Major versions, and the last 5 minor versions of each major version. Unfortunately, this command is not actually reducing the minor versions. It is working with the Major versions just fine, but all minor versions are being retained for each major version retained. Is my understanding of this command wrong, or is it not working? Are there other factors to consider? Does anyone know of an alternative that can fit my needs? The overall plan is to trim the current version history, then apply the automatic version setting to each library in our tenant. Here is the MS guide I referenced, maybe I missed something -> https://learn.microsoft.com/en-us/sharepoint/tutorial-queue-a-trim-job Any help is greatly appreciated, Cam
Syntex not processing files
48 hours ago, Syntex stopped processing files in our libraries, across several SharePoint sites and models. Processing Status is currently “In Progress” for over 36 hours in some cases. No errors are shown in the “Processing status” column. We've tried removing the models and applying again, adding new files, manually choosing to Classify & Extract. This occurred 3 months ago, and Microsoft had a SharePoint service degradation issue at the time, but current nothing showing on 365 Health. Anyone else experiencing this or have ideas? We logged a support request but current they cannot find an issue.SharePoint Online filename restrictions - and SharePoint Autofill
Hi everyone, I'm working with SharePoint Online and trying autofill to generate SPO file titles so I can eventually use them a filename. As you might know SPO filenames know a few restrictions (invalid characters like `/ \ : * ? " < > |`, reserved names, path length limits, etc.), unfortunately syntex autofil is not aware of this. Has anyone ever tried the same, come around the same problem and how did you solve it. Especially since including all SPO restrictions, and filename limitations is not a feasible solution.
Syntex creates only Single line text fields for each piece of information.
I have deployed and applied "Structured document processing" model to one of my libraries in SharePoint. I chose two pieces of information to extract: Date (type date) Table, which had 6 columns (with types : text, number, date) The training of the model and the extraction itself seems fine, but after applying the model to the library, all the columns, that Syntex creates in the library for the new content type are "Single lines of text". No number, no date... Is there something I am missing or is this the Syntex situation right now? Similar problem is with longer strings, where I would like the Syntex to grap the whole string, but since he is not able to create Multi line column, he just cuts the string after the character limit is reached. Any advice for how to proceed would be highly appreciated. Thanks!Syntex Failing
Starting around 10PM EST last night all my files stopped getting processed by Syntex. All show "Failed". With the error: "The applied models can't process this type of file" These are all PDF and Excel files. Nothing new there. I suspect it is related to the general O365 issue on the Health Portal. https://admin.microsoft.com/?login_hint=nthoman%40bmic.com&source=applauncher#servicehealth/:/alerts/MO1009364
Issues with Microsoft Syntex Document Processing Model: Incomplete Extraction for Multi-Page PDFs
I'm facing several challenges with the Microsoft Syntex document processing model, particularly when dealing with multi-page PDFs and large tables. I'd appreciate any insights or suggestions from fellow users or Microsoft experts who may have encountered similar issues. Below are the specific problems I'm experiencing: Unsupported PDF Formats & Multiple Tables on a Single Page: Some PDFs that I try to process seem to be in unsupported formats. In addition, pages containing multiple tables often result in extraction errors or incomplete data. Has anyone else encountered this with complex table layouts in PDFs, and what approaches have you used to resolve it? Data Extraction from Multi-Page PDFs: When processing PDFs longer than two pages (e.g., six-page PDFs), the model often extracts data correctly from only the first two or three pages. The remaining pages, particularly those with tables spanning multiple pages, are either incomplete or entirely missing. Additionally, large tables (100+ rows) in multi-page PDFs tend to result in inaccurate extraction. Are there any best practices for handling these multi-page table scenarios? Automatic Processing Issues: Sometimes, the Syntex model doesn't process files automatically. I have to manually select the file and click "Classify" to trigger processing. Is this a known issue, or is there something I might be missing in my setup? Model Publishing Delays: After publishing changes to the model, it often takes an extended period (up to 30 minutes or more) for the new model to start processing files. In some cases, the files aren't processed at all. Has anyone experienced similar delays after publishing a model, and what could be causing this? Low Confidence Scores for Multi-Page PDFs: When processing multi-page PDFs with tables, the model returns low confidence scores (below 60%). What steps can I take to improve these accuracy scores, particularly for documents with complex table structures?Single Class document in Syntex - Excel value
Hi I'm trying to build a model using the Single Class document and then read Excel files from a SharePoint library. It reads most of the data except cells which has a value from a formula or reference! So if A2 has the value 5, i see it in the data read, if B2 has the value =sum(a2+a3) = 6 it does not show in the data output from the file. Any idea how to get around this? I have roughly 120 new Excel files each month, Ineed to compile into one CSV - whilst waiting for a proper business system ;-)
