document processing
77 TopicsHelp me to fetch All drive id from sharepoints
Help me to fetch All drive id from sharepoints I am using to fetch drive id using Graph API (GET call) https://graph.microsoft.com/v1.0/sites/f17253bc-a4f6-4bab-990d-ab627c6bb319/drives?$select=name,driveType,id But I am getting only below response { "id": "b!vFNy8fakq0uZDXXXXXXXXXXXXXXXsMU6nTErdZmNJLuIx_z-RrDQxfSsIyx4", "name": "Documents", "driveType": "documentLibrary" } But In SharePoint below drives is present but out of those I am getting only one Could you please help me to fetch all drive id1.1KViews0likes1CommentSharepoint Sync Onedrive - Long File Name issues
I need move some file from sharepoint to onedrive . i have add sharepoint folder to shortcut one drive . but when update on this device. , prompt up file long file name , need rename shorted after can sync . a lot of files. I tried using PnPShell to try search long file name files . but the scripts does not work .Pls share other solution to solve out the isseus.73Views0likes1CommentNEW! SharePoint Lists & Libraries: Default Approvers for Configure Approvals Explained
🚀 New SharePoint Feature Alert! Microsoft has just introduced a super useful capability in SharePoint Lists and Document Libraries: the option to set Default Approvers when configuring approval workflows. This small but powerful enhancement removes repetitive manual steps and makes approval automation more consistent across teams using SharePoint + Power Automate. In my latest YouTube video, I walk through how this feature works, how to set it up, and why it can significantly streamline your approval processes. 🎥 Watch the full breakdown here: https://youtu.be/Xxn-IrKVh6E 👍 If you find it useful, let me know in the comments! #SharePoint #Microsoft365 #PowerAutomate #Productivity #M365 #SharePointOnline #Automation #DigitalTransformation187Views1like0CommentsTrimming 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, Cam171Views1like1CommentSyntex 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.515Views0likes3CommentsSharePoint 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.67Views0likes0CommentsSyntex 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!246Views0likes1CommentSyntex 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/MO1009364497Views2likes6Comments