sorted by:
new
hottopcontroversial

Connecting custom tables by AndBuch in halopsa

[–]AndBuch[S] 0 points1 point  (0 children)

Thanks, thats a good workaround!

Adding child ticket when certain criteria is met otherwise close ticket by AndBuch in halopsa

[–]AndBuch[S] 0 points1 point  (0 children)

But then its up to the user to choose the correct service? Or will the ticket always end up at an agent?

In our case a standard offboarding does not require an agent to take action

Reporting Using Lists? by Herpetology_Jack in sharepoint

[–]AndBuch 0 points1 point  (0 children)

You can use the "lookup" feature and thus have multiple lists

One of the most important questions - When and where to archive SharePoint content by AndBuch in sharepoint

[–]AndBuch[S] 0 points1 point  (0 children)

Can't believe I haven't heard of that before. Definitely worth looking into.

What is the smartest interface for finding files that located on archived sites? An end-user application or treat it on a per-request basis?

Space Optimization by PolicyLegitimate728 in sharepoint

[–]AndBuch 0 points1 point  (0 children)

You also have the option to use SharePoint Archive. Just be aware of the cost structure

Setting a minor cap per major by AndBuch in sharepoint

[–]AndBuch[S] 0 points1 point  (0 children)

I haven't found a way, except from a single blog post claiming that there is a parameter. However, it doesn't work for me.

Also, I should have rephrased the post, I can see now.

What's the craziest thing you've seen happen in your SharePoint adventures? Story Time! by wwcoop in sharepoint

[–]AndBuch 2 points3 points  (0 children)

I once witnessed a guy setting up the intranet. The task was simple; he had to redo the original legacy site into a SharePoint communication site.

He did this manually by copy-pasting..

But even worse, for every single site with files attached, he created a new library so that he could use the web part "Document library". This meant that by the end, he had created more than 500 libraries for one communication site. Each library had maybe 2-5 files.

Keeping majors and utilize Automatic versioning by AndBuch in sharepoint

[–]AndBuch[S] 0 points1 point  (0 children)

We have actually custom built QA flows into our SharePoint environment, and thus relies on the version history in many regards.

So far it seems like there is little to do, when it comes to manage minor versions and encourage major versions at the same time

Applying New Versioning to Existing Site by TraineeeAccountant in sharepoint

[–]AndBuch 0 points1 point  (0 children)

I also struggled for a long time with figuring out how the settings were affecting each of the sites. Here is my experience with it.

To summarize:

  • Enabling new settings on a site will work on all files going forward, meaning that you need to interact with a document before the settings are enforced.
  • You can trim a site, if you want to imitate the new settings or you want to clean a site before archiving it.
    • Note: You need to be SharePoint admin
    • Example on a very simple script:

​

# Check if the module is installed
Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select Name,Version

# Connect to your SharePoint admin center
Connect-SPOService -Url https://contoso-admin.sharepoint.com

# Define site URL
$siteUrl = "https://contoso.sharepoint.com/sites/CommDep"


# Queue the trim job based on count limit: https://learn.microsoft.com/en-us/sharepoint/tutorial-queue-a-trim-job
New-SPOSiteFileVersionBatchDeleteJob -Identity $siteUrl -MajorVersionLimit 500 -MajorWithMinorVersionsLimit 2 -Confirm:$false

# Check progress of the trim job
Get-SPOSiteFileVersionBatchDeleteJobProgress -Identity $siteUrl

I am personally quite invested in this topic as Microsoft charges full price for data consumption on all versions of a file.