Forum Widgets
Latest Discussions
PromotedState does not update anymore
I wish to update the promoted status to 0 (page), 1 (unpublished news) or 3 (published news). I was always doing this via SharePoints column formatting. See .json column formatting below. This worked perfectly fine until about this week. Now it doesn't seem to work anymore. Now I tried updating the PromotedState also via PowerAutomate. This also doesn't seem to work... How should I now change the PromotedState. Does someone have any clue how I can update the PromotedState or why the column formatting way of wokring, suddently doesn't work anymore? The json code for column formatting. { "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json", "elmType": "div", "style": { "flex-wrap": "nowrap", "display": "flex", "flex-direction": "row" }, "children": [ { "elmType": "div", "txtContent": "=if(@currentField == 0 ,'0 : Page' , if(@currentField == 1, '1 : News (Unpublished)' , if(@currentField == 2 , '2 : News','') ) )", "style": { "box-sizing": "border-box", "padding": "4px 8px 5px 8px", "display": "flex", "border-radius": "16px", "align-items": "center", "overflow": "hidden", "margin": "4px 4px 4px 4px", "border": "1px solid" }, "attributes": { "class": "=if(@currentField == 0 ,'ms-fontColor-themePrimary ms-borderColor-themePrimary ms-bgColor-white' , if(@currentField == 1, 'ms-fontColor-themePrimary ms-borderColor-themePrimary ms-bgColor-themeLighter' , if(@currentField == 2 , 'ms-fontColor-white ms-borderColor-themePrimary ms-bgColor-themePrimary','') ) )" } }, { "elmType": "div", "style": { "font-size": "18px", "cursor": "pointer", "padding": "10px", "border-radius": "50%" }, "attributes": { "iconName": "MoreVertical", "class": "ms-fontColor-themePrimary ms-bgColor-themeLighter--hover" }, "customCardProps": { "openOnEvent": "click", "directionalHint": "rightCenter", "isBeakVisible": true, "formatter": { "elmType": "div", "style": { "display": "flex", "flex-direction": "column", "align-items": "flex-start" }, "children": [ { "elmType": "div", "txtContent": "Change to Page (0)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "0" } } }, { "elmType": "div", "txtContent": "Change to unpublished news (1)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "1" } } }, { "elmType": "div", "txtContent": "Change to published news (2)", "style": { "padding": "10px 20px 10px 20px", "cursor": "pointer", "width": "200px" }, "attributes": { "class": "ms-bgColor-themeLighter--hover" }, "customRowAction": { "action": "setValue", "actionInput": { "PromotedState": "2" } } } ] } } } ] } The HTTP SharePoint call to update the PromotedStatus.Multiple Page Libraries on site
Hi everyone I have a strange issue that I haven't come across before. A customer has got an old subsite on SharePoint Online that was created with the STS#0 template (classic Team Site with no group) and they want to modernise their old wiki pages. This should have been straightforward as I was planning on using the https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-site-pages-powershell. However, on this site they have two page libraries - the standard Site Pages library and then what looks like a custom page library (I've blanked out the name of the custom library as it contains the company name): All of the pages they want to modernize are in the custom library but the issue with this is that the only content type available is Wiki Page: This means that although the PnP PowerShell runs successfully against pages in this library, the new versions don't actually appear in the library. I assume this is because the modern Site Page content type isn't available in the library. I was under the impression that a site could only have one page library so I'm not sure how this site has the two. On a more urgent note I need to work out the best way of modernizing these pages. Currently the only way I can see is using Power Automate to copy the pages to the Site Pages library and then convert them there. The only issue with that is that there are links within the pages to other pages so I'd need to go through them and fix these once they've been moved. here are over 300 pages so I don't really want to do this. Does anyone have any ideas on the best way forward with this. Also, if you know how there are multiple page libraries I'd be keen to hear it as I haven't come across this before. Thanks in advance for your help.
Active Site Usage Not Matching Storage Used?
At my new position our SharePoint storage is getting used quickly. As of right now we have 69GB available of 11.75TB. When look at the active sites the total Storage Used only adds up to 2TB. Where is the other 8.75TB coming from? Version history was changed to 100 major versions and to delete versions after 1 year. Is it possible that the versions still being retained could add up to 8.75TB? I archived a site that was 13GB but it's still showing 69GB available. How long does it take to reclaim that storage?
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
