SharePoint lists may grow bigger with time, that’s no doubt. Depending on your user base, you might start to feel performance issues after a few thousands of items created. That’s why it should be good for you to looking after auto archive items in SharePoint using Power Automate.
Why Power Automate? It is a great tool with seamless integration with SharePoint which allows you to reduce the toil and generate value by automating tasks. If you haven’t checked Power Automate before, it is a good opportunity to start looking into the Low Code world.
A pretty common use case scenario where you might want to auto archive files in SharePoint with Power Automate. Sometimes it is important to move some files from one place to other, reducing the size of a library and the number of rows returned in a search. You can always explore the retention policies available out-of-box in SharePoint, of course. But sometimes this feature can present some problems depending on the content type or data type you are working with.
So if you have the option to work with Power Automate, why not using it? Power Automate is great when you need to automate one specific task and it is a very intuitive to use. It is fully integrated with SharePoint and you can take advantage of its connectors to do your tasks.
SharePoint lists are very powerful and we often need to export list data for our customers. One of the best option to achieve that is by PowerShell. So in this blog post we will cover how to export list in SharePoint via PowerShell. After exported to CSV, it’s easy to convert to an Excel format and do whatever you want. It’s important to say that this script will work on SharePoint Server On-Premises and you will need to enter the server to run it.
But why using a PowerShell if we can do that by the UI? Well, I need to agree with you. What I can answer about that? Basically, you can schedule exporting activities, you can take leave the script running on long lists without short timeouts, etc.
In case you want to test SharePoint e-mail settings with PowerShell, you can achieve that by sending a dummy e-mail to yourself by running a simple PowerShell script. In this way you can ensure your SMTP settings are good and all SharePoint notifications or coding solutions that send e-mails will work.
It’s important to test it during the configuration of a new Farm. The steps for configuring it can be found on Microsoft docs. Or maybe if you need to troubleshoot the e-mail features in your SharePoint solutions. SharePoint has many automated alerts that work with Workflows, Approval processes and Access control forms.
PowerShell script for testing SharePoint e-mail settings
The script is pretty straightforward and you will need to update just two lines. One with the right e-mail going to receive the message and the Site Collection URL that is going to trigger the message.
That’s it! I hope this script can help you when you want to test SharePoint e-mail settings with PowerShell. Also on creating new solutions for monitoring your e-mail settings on the SharePoint farms you happen to work with.
This blog post will cover how to batch insert items in SharePoint with Power Automate. Our Flow will explore the SharePoint REST API calling the Batch endpoint and inserting 1000 items per time. For every Batch request made, you can add multiple Changesets up to 1000 Changeset requests. Likewise, for each Changeset, you can only add up to 1000 requests. That’s why our example will try to insert 1000 items per request just to make things simple.
In the tests I have made, using this Flow we were able to insert 5000 items in 16 minutes. All of my tests were executed in a Free Microsoft Flow account. In the other hand you probably may experience a better performance if you have a licensed account. Consequently, using a licensed account, you will be able to read more than 5000 rows.
In addition to that, it’s important to say that our test is going to read data from an Excel file. Everything will be static like the filename and the table name from the file. But this doesn’t mean that you cannot do the same by passing dynamic values. If you create a flow that runs tied to a file creation event in SharePoint, you will get the data needed to make it dynamic and save your time with this automation.
This blog post will cover how to batch delete items in SharePoint with Power Automate. Our Flow will explore the SharePoint REST API calling the Batch endpoint and deleting 1000 items per time. For every Batch request made, you can add multiple Changesets up to 1000 Changeset requests. Moreover, for each Changeset, you can only add up to 1000 requests. That’s why our example will try to delete 1000 items per batch request just to make things simple.
In the tests I made, using this example we are able to delete 500 items in 2 minutes, 5.000 items in 12 minutes and 15.000 items in 40 minutes. All of my tests were ran in a Free Microsoft Flow account, so you probably may experience a better performance if you have a licensed account.
SharePoint relies on Timer Service and Admin Service to run and manage its tasks. As any Windows Service, sometimes we need to stop and start them. That’s why I wrote this post to share a script on how to restart Timer and Admin in SharePoint.
These services are present in a SharePoint Server, inside the Windows Services list. There you can see both SharePoint Administration and SharePoint Timer Service:
The Admin Service performs administrative tasks for Windows Services under the Local Admin Network rights;
The Timer Service sends notifications and performs scheduled tasks for SharePoint services. It must run with an Account with Admin rights to server.
Timer and Admin Services
Script to restart the timer and admin services
The script will load the SharePoint PowerShell dependencies and start by restarting the services in each machine present in the farm. This can throw an error if the Windows Servers are not properly configured to allow remote changes to their services.
Finally, in the end we use some objects provided by the SharePoint DLL to ensure that every Timer service is online and available.
There are other services required to run SharePoint, but it depends on how you are exploring its features. Here is the list of possible mandatory services that you may face and even restart if you want (haha):
SharePoint Tracing;
SharePoint User Code Host;
SharePoint VSS Writer;
World Wide Web Publishing Service;
SharePoint Server Search.
That’s it! I hope this post can be helpful when you want to restart Timer and Admin in SharePoint. Also you may find useful other posts related to PowerShell in the blog posts available.
This post will present a Powershell script that will let you Export user permissions in SharePoint from all Web Applications and their Site Collections.
The script creates a CSV file and fills the data in the columns like below:
Site Name;
Site Url;
Name of the Group;
Login of the Group Owner;
Display name of the Group Owner;
User Login (who has the permission);
User Display Name (who has the permission);
The role or permission the user has.
Report after being exported (in Brazilian Portuguese)Continue reading
This blog post will talk about an idea of customization of the SharePoint breadcrumb for better navigation. The solution uses the out-of-box Delta Breadcrumb Dropdown component to provide the data required to render the breadcrumb using pure JavaScript for that.
Important notes:
This solutions works only for Classic Experiences;
I would recommend enabling only to internal pages branded using the System Master Page;
The JavaScript needs to be installed using a Custom Action or calling the JS file from the Master Page;
This solution may not be a good practice for SharePoint Online environments, if you are focused on working only with Modern experiences.
When importing a list template from another Site or Site Collection built in a different language, you may not be able to see it as an App available to add to your site. It happens because SharePoint will look for the List Templates available in the current language for the Web Site. I’ve experienced it recently when migrating a list from a site collection in Portuguese to another site collection in Spanish, that’s why I decided to write this blog post that teaches how to change List Template language to reuse it in another Site with different language
In this post we will give you a PowerShell that may help you on migrating the list easily.
Wiliam is from Porto Alegre, Brazil, currently working as DevOps Engineering Advisor at Dell EMC. He has been working with Microsoft technologies for almost ten years with one year gap studying abroad in Japan attending the Science without Borders program from the Brazilian government. Also he is MCSE Productivity, a SharePoint lover.
Nowadays he is investing the most part of his time on exploring GitLab and Azure DevOps features and helping the company to develop a DevOps culture among its colleagues.
In addition of that, he spends some time on learning Japanese, doing CrossFit and playing real-time strategy games like Age Of Empires. Read More…
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Recent Comments