SharePoint Hosting – Custom RSS SPFx Feed WebPart In Modern UI

Feb 25th

Posted by Peter in European SharePoint 2013 Hosting

A client had a requirement to display the RSS feed on a modern UI page for 40,000 users.

Challenge

The main challenging part is that CORS has an issue with reading RSS feeds (xml). If the RSS feed is in a JSON format then we may use jsonpdataType to resolve the CORS issue.

Modern UI supports out of the box RSS Feed web part. But it has some limitations which are listed below:

This web part is available only for Office 365 Group Enabled team sites.
Users should have Outlook account and it has to be manually added to the Office 365 group.
Only supports 2500 users.

No options were available to alter the format in which information is displayed.

There are custom SPFx solutions available:

spfx-40-fantastics – RSS Feed Reader webpart
URL – https://github.com/OlivierCC/spfx-40-fantastics/wiki/Rss-Reader
This webpart solution is not working at the moment.
Reference – https://github.com/OlivierCC/spfx-40-fantastics/issues/97
SP-Dev-fx Webparts – React RSS Reader webpart
URL – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rss-reader
This solution uses the below ways to read RSS feed
Direct – This has an issue with CORS policy

3rd party solutions like https://feed2json.org or https://rss2json.com.

https://feed2json.org is open source but has limitations as below

It has to be hosted on a separate server
It does not support CORS.

https://rss2json.com free version has limitations as below

It takes 1 hour to display the updates.
Supports a maximum of only 10,000 requests per day.
Maximum of 25 feeds were allocated per account

Solution

To overcome this we came up with this approach with the help of Microsoft Flow, SharePoint Lists and ReactSharePoint Framework Web part.

Note

Microsoft Flow license is needed.

RSS feeds are generally available in XML file format and contain the URL, title, and summary of each page to display. So we developed a Microsoft recurring flow which reads the RSS feed XML and updates a SharePoint List Column with the XML content.

SharePoint List

We created a SharePoint List with a multi-line text column.

Microsoft Flow

We developed a Microsoft recurring flow.

The explanation of the steps of the flow:

Recurrence – specifies the schedule of execution of flow. We had scheduled it to execute the flow every 30 minutes.

Initialize variable – This initializes a variable to save the RSS url.

Get Item – This reads the RSS Feed url from a SharePoint List (We used a predefined SharePoint List to store the RSS Url. This also provides the facility to the end user to change the RSS Feed URL if needed).

Apply to each – Assigns the RSS url variable with the value for RSS Feed url from the previous step.

HTTP -Make a HTTP call with GET Method to read the text from RSS Feed XML.

Update Item –Updates a SharePoint List multi-line text column with the output of HTTP call made in the previous step.

After all the above steps are completed, the execution of the flow will update the SharePoint List multi-line text column with XML content of the RSS Feed XML file.

React SharePoint Framework Web part

We developed a simple SharePoint client-side web part to display the RSS feed on Modern site page in the same format as the OOTB RSS Web part for Modern pages. Additionally, we can customize the display format for RSS as well with our custom web part solution.

In order to convert XML text to JSON text we used npm xml-js.

The web part directly queries the SharePoint List multi-line text column value using REST API Call. Then converts the stored XML data to JSON text and loops through all the RSS feed data to display it in descending format of Published Date.

Which problem have we resolved?

Now, we are not depending on any third party webparts and third-party API to read RSS feed data, hence we don’t face any request and feed limits.
Resolved CORS issue by directly accessing feed data from already-stored feed using MS Flow.
We can customize the display format for RSS as well with our custom web part solution.

SharePoint 2013 Hosting – HostForLIFE :: How To Use PnP React Accordion Control In SPFx?

Feb 18th

Posted by Peter in European SharePoint 2013 Hosting

Accordion menus and widgets are widely used on websites to manage a large amount of content and navigation lists. In this article, we will see step by step implementation of the accordion with SharePoint list.

Scenario

In this example, we will create a list called “Accordion” and in the list, we will create a Description field (it will be multiple lines of text -Rich text) and will use Title and Description field to expand and collapse.

We will use PnPJs to get list items and then will render them in the accordion form.

At the end, our output will be like this,

Let’s see the step-by-step implementation.

Implementation

Create a list with Title and Description fields as mentioned above.
Open a command prompt
Move to the path where you want to create a project
Create a project directory using:

md directory-name

1	md directory-name

Move to the above-created directory using:

cd directory-name

1	cd directory-name

Now execute the below command to create an SPFx solution:

yo @microsoft/sharepoint

1	yo @microsoft/sharepoint

It will ask some questions, as shown below,

After a successful installation, we can open a project in any source code tool. Here, I am using the VS code, so I will execute the command:

code .

code .

Now we will install pnpjs and pnp-spfx-controls-react as shown below:

npm install @pnp/sp --save    
npm install @pnp/spfx-controls-react --save --save-exact

1 2	npm install @pnp/sp --save npm install @pnp/spfx-controls-react --save --save-exact

Now go to the src > webparts > webpart > components > I{webpartname}Props.ts file,

import { WebPartContext } from "@microsoft/sp-webpart-base";  
  
export interface IPnpReactAccordionProps {  
  description: string;  
  listName: string;  
  context: WebPartContext;  
}

import { WebPartContext } from "@microsoft/sp-webpart-base";

export interface IPnpReactAccordionProps {

description: string;

listName: string;

context: WebPartContext;

}

Create a file I{webpartname}State.ts inside src > webparts > webpart > components and create state interface as below,

interface IListItem {  
    Id?: string;  
    Title: string;  
    Description: string  
}  
  
export interface IPnpReactAccordionState {  
    listItems: IListItem[];  
    errorMessage: string;  
}

interface IListItem {

Id?: string;

Title: string;

Description: string

}

export interface IPnpReactAccordionState {

listItems: IListItem[];

errorMessage: string;

}

Create a Service folder inside src and then in this folder create a file called SPService.ts. And in this file, we will create a service to get list items as below,

Here list name will come from the webpart property pane.

import { WebPartContext } from "@microsoft/sp-webpart-base";  
import { sp } from '@pnp/sp/presets/all';  
  
export class SPService {  
    constructor(private context: WebPartContext) {  
        sp.setup({  
            spfxContext: this.context  
        });  
    }  
  
    public async getListItems(listName: string) {  
        try {  
            let listItems: any[] = await sp.web.lists.getByTitle(listName)  
                .items  
                .select("Id,Title,Description")  
                .get();  
            return listItems;  
        } catch (err) {  
            Promise.reject(err);  
        }  
    }  
}

import { WebPartContext } from "@microsoft/sp-webpart-base";

import { sp } from '@pnp/sp/presets/all';

export class SPService {

constructor(private context: WebPartContext) {

sp.setup({

spfxContext: this.context

});

}

public async getListItems(listName: string) {

try {

let listItems: any[] = await sp.web.lists.getByTitle(listName)

.items

.select("Id,Title,Description")

.get();

return listItems;

} catch (err) {

Promise.reject(err);

}

Now move to the {webpartname}Webpart.ts. And create a list name property in property pane configuration and pass context and list name property as below,

import * as React from 'react';  
import * as ReactDom from 'react-dom';  
import { Version } from '@microsoft/sp-core-library';  
import {  
  IPropertyPaneConfiguration,  
  PropertyPaneTextField  
} from '@microsoft/sp-property-pane';  
import { BaseClientSideWebPart } from '@microsoft/sp-webpart-base';  
  
import * as strings from 'PnpReactAccordionWebPartStrings';  
import PnpReactAccordion from './components/PnpReactAccordion';  
import { IPnpReactAccordionProps } from './components/IPnpReactAccordionProps';  
  
export interface IPnpReactAccordionWebPartProps {  
  description: string;  
  listName: string;  
}  
  
export default class PnpReactAccordionWebPart extends BaseClientSideWebPart<IPnpReactAccordionWebPartProps> {  
  
  public render(): void {  
    const element: React.ReactElement<IPnpReactAccordionProps> = React.createElement(  
      PnpReactAccordion,  
      {  
        description: this.properties.description,  
        listName: this.properties.listName,  
        context: this.context  
      }  
    );  
  
    ReactDom.render(element, this.domElement);  
  }  
  
  protected onDispose(): void {  
    ReactDom.unmountComponentAtNode(this.domElement);  
  }  
  
  protected get dataVersion(): Version {  
    return Version.parse('1.0');  
  }  
  
  protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {  
    return {  
      pages: [  
        {  
          header: {  
            description: strings.PropertyPaneDescription  
          },  
          groups: [  
            {  
              groupName: strings.BasicGroupName,  
              groupFields: [  
                PropertyPaneTextField('description', {  
                  label: strings.DescriptionFieldLabel  
                }),  
                PropertyPaneTextField('listName', {  
                  label: strings.ListNameFieldLabel  
                })  
              ]  
            }  
          ]  
        }  
      ]  
    };  
  }  
}

import * as React from 'react';

import * as ReactDom from 'react-dom';

import { Version } from '@microsoft/sp-core-library';

import {

IPropertyPaneConfiguration,

PropertyPaneTextField

} from '@microsoft/sp-property-pane';

import { BaseClientSideWebPart } from '@microsoft/sp-webpart-base';

import * as strings from 'PnpReactAccordionWebPartStrings';

import PnpReactAccordion from './components/PnpReactAccordion';

import { IPnpReactAccordionProps } from './components/IPnpReactAccordionProps';

export interface IPnpReactAccordionWebPartProps {

description: string;

listName: string;

}

export default class PnpReactAccordionWebPart extends BaseClientSideWebPart<IPnpReactAccordionWebPartProps> {

public render(): void {

const element: React.ReactElement<IPnpReactAccordionProps> = React.createElement(

PnpReactAccordion,

{

description: this.properties.description,

listName: this.properties.listName,

context: this.context

}

);

ReactDom.render(element, this.domElement);

}

protected onDispose(): void {

ReactDom.unmountComponentAtNode(this.domElement);

}

protected get dataVersion(): Version {

return Version.parse('1.0');

}

protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {

return {

pages: [

{

header: {

description: strings.PropertyPaneDescription

groups: [

{

groupName: strings.BasicGroupName,

groupFields: [

PropertyPaneTextField('description', {

label: strings.DescriptionFieldLabel

}),

PropertyPaneTextField('listName', {

label: strings.ListNameFieldLabel

})

]

}

]

}

]

};

}

Move to the {webpartname}.tsx file and then bind the service using current context and the call service for get list items and set values in the state and render it in accordion control as below,

import * as React from 'react';  
import styles from './PnpReactAccordion.module.scss';  
import { IPnpReactAccordionProps } from './IPnpReactAccordionProps';  
import { IPnpReactAccordionState } from './IPnpReactAccordionState';  
import { escape } from '@microsoft/sp-lodash-subset';  
import { SPService } from '../../../Service/SPService';  
import { Accordion } from "@pnp/spfx-controls-react/lib/Accordion";  
  
export default class PnpReactAccordion extends React.Component<IPnpReactAccordionProps, IPnpReactAccordionState> {  
  
  private _services: SPService = null;  
  constructor(props: IPnpReactAccordionProps) {  
    super(props);  
    this.state = {  
      listItems: [],  
      errorMessage: ''  
    }  
    /** Bind service using current context */  
    this._services = new SPService(this.props.context);  
  }  
  
  public componentDidMount() {  
    this.getListItems();  
  }  
  
  /** Get items of selected list and set values in state */  
  private async getListItems() {  
    if (this.props.listName) {  
      let items = await this._services.getListItems(this.props.listName);  
      this.setState({ listItems: items });  
    }  
    else {  
      this.setState({ errorMessage: 'Please enter the list name in property pane configuration.' });  
    }  
  }  
  
  public render(): React.ReactElement<IPnpReactAccordionProps> {  
    return (  
      <div className={styles.pnpReactAccordion}>  
        {  
          //Map list items and render in accordion  
          (this.state.listItems && this.state.listItems.length) ? this.state.listItems.map((item, index) => (  
            <Accordion title={item.Title} defaultCollapsed={true} className={"itemCell"} key={index}>  
              <div className={"itemContent"}>  
                <div className={"itemResponse"} dangerouslySetInnerHTML={{ __html: item.Description }}></div>  
              </div>  
            </Accordion>  
          )) : <p>{this.state.errorMessage}</p>  
        }  
      </div>  
    );  
  }  
}

import * as React from 'react';

import styles from './PnpReactAccordion.module.scss';

import { IPnpReactAccordionProps } from './IPnpReactAccordionProps';

import { IPnpReactAccordionState } from './IPnpReactAccordionState';

import { escape } from '@microsoft/sp-lodash-subset';

import { SPService } from '../../../Service/SPService';

import { Accordion } from "@pnp/spfx-controls-react/lib/Accordion";

export default class PnpReactAccordion extends React.Component<IPnpReactAccordionProps, IPnpReactAccordionState> {

private _services: SPService = null;

constructor(props: IPnpReactAccordionProps) {

super(props);

this.state = {

listItems: [],

errorMessage: ''

}

/** Bind service using current context */

this._services = new SPService(this.props.context);

}

public componentDidMount() {

this.getListItems();

}

/** Get items of selected list and set values in state */

private async getListItems() {

if (this.props.listName) {

let items = await this._services.getListItems(this.props.listName);

this.setState({ listItems: items });

}

else {

this.setState({ errorMessage: 'Please enter the list name in property pane configuration.' });

}

public render(): React.ReactElement<IPnpReactAccordionProps> {

return (

{

//Map list items and render in accordion

(this.state.listItems && this.state.listItems.length) ? this.state.listItems.map((item, index) => (

</div>

</Accordion>

)) : <p>{this.state.errorMessage}</p>

}

</div>

);

}

Now serve the application using the below command,

gulp serve

1	gulp serve

Now test the webpart in SharePoint-SiteURL + /_layouts/15/workbench.aspx.

Output

SharePoint 2013 Hosting – HostForLIFE :: Managing Site Storage In SharePoint Online

Feb 11th

Posted by Peter in European SharePoint 2013 Hosting

Overview

With an Office 365 subscription, we get storage space for SharePoint Online based on a number of licenses. As we create SharePoint online sites and start using them by adding our content, we start to consume the assigned storage space. It is important for us to keep a track of consumed and available site storage.

In this article, we will explore the site storage experience in modern SharePoint and its configuration.

Site Storage in SharePoint Online

The modern SharePoint online admin center gives an easy option to create new site collections.

Just a few simple fields to fill in and the site will be ready in a few seconds! But did you notice? We do not have a field to specify the storage quota for our site!

The Active sites page in the SharePoint Online admin center though, shows the storage used for each site. Also, we can see the total storage used and available for use.

Let us see from where site storage can be configured.

Site storage configuration

In the SharePoint admin center, from the left menu click Settings > Site storage limits.

The default storage limit is Automatic. The storage limit can be configured as,

Automatic
The default. All sites get the storage from a central pool. The global or SharePoint administrator does not have to manage the storage per site. It is handled automatically by SharePoint for them.
Manual
The global or SharePoint administrator can have a fined tuned site storage allocated for each of the SharePoint site collection.

Manage site storage for individual sites

If you want to manage the site storage per site, you will have to go with the manual configuration option.

With the manual option, the administrator can configure the maximum storage per site and can also set the notification for site owners when a certain percentage of the site storage limit is consumed.

The site owners or collection administrators can check the storage quota by following the below steps,

Navigate to the site settings page.
Under Site Collection Administration, click Storage Metrics.

Note

The recycle bin counts towards the site quota.

PowerShell support

The site quota can be set with PowerShell,

Set-SPOSite -Identity https://contoso.sharepoint.com -StorageQuota 1500 -StorageQuotaWarningLevel 1400

Summary

With an Office 365 subscription, we get storage space for SharePoint Online based on a number of licenses. It is important for us to keep track of consumed and available site storage. We explored the site storage experience in modern SharePoint and its configuration.

How To Fix SharePoint 404 Error After Content Database Migration?

Feb 2nd

Posted by Peter in European SharePoint 2013 Hosting

Issue Description

If we Google the above text, we will get multiple references for fixing this issue. For this, the traditional ways of fixing are:

The site might have been deleted, request to the site administrator to check the recycle bin.
Do the IIS reset.
Try to access the other layout page like /_layouts/15/settings.aspx(might be default.aspx or home.aspx has some issue).
Clear the timer job cache….etc

None of the above solutions worked for me.

Background of the issue

Let me give some background about the issue. I have migrated the Content DB using mounting from SharePoint 2013 to 2016. All site collections along with their subsites got opened in the browser without any issue but some of the subsites did not get opened in the browser and threw the “404: file not found” error.

If we go to site content structure page, those subsites are available. It looks strange to me! Not getting any clue, I kept on investigating this issue .. I tried to list out the site using SPSite collection PowerShell command. It got listed out, it made me more confused.

Then, I tried to connect one of the faulty subsites using ShareGate There, I saw object reference not set error. Then, I changed the direction of my investigation… I deleted the faulty subsite and tried to recreate it again with the same name manually. Unfortunately, I got the error, “You cannot create a site with this name <IT> as this is a reserved keyword by SharePoint”.

Well, it confused me more on how this could be a reserved keyword? Then, I went to check the managed path for this web application. Yes, I found the solution…The managed path was the issue. There was a managed path with the name IT in that web application, so we cannot create any subsite with that name with the same hierarchy of managed path. If we delete that IT manages path, we can create a subsite and can access IT along with all subsites under this. This is how I have solved this issue…but nowhere did I get any links or clues about this.

This is totally based on my personal experience. For you, the scenario may be different.

Example

Manged path in the web application: IT

I was trying to access the subsite like below.

http://server:1010/IT #here IT is the subsite.

So, if we have to manage path with the name IT, we cannot browse this subsite along with the all subsites under IT.

Solution

Check the managed path and remove the managed path which is causing the issue. Here, I have removed IT managed path, then it worked fine.

SharePoint 2013 Hosting – HostForLIFE :: How To Fix SharePoint Errors In A Few Minutes?

Jan 28th

Posted by Peter in European SharePoint 2013 Hosting

SharePoint is a flexible server program available for use today. And the main motive of Microsoft for offering SharePoint is to help the organizations build a collaborative environment among the employees. Whenever a number of users work with an application for workflows, the amount of data also increases and demands more storage space to store it. This affects the SharePoint space configuration which eventually will badly affect its overall performance. Apart from this, SharePoint has a very dynamic nature due to which administrators and normal users, both, might face some issues. Therefore, in this blog, let us see how to fix SharePoint errors with ease. Along with this, a third party tool is also discussed for SysTools SharePoint to SharePoint Migration.

Common SharePoint Errors Encountered By Users, With Solutions

This section of the blog will let users know about SharePoint problems and how they can resolve these easily.

Problem #1 – Increase in Database Size

It is clear that the SharePoint database contains lots of documents, images, presentations, videos, etc. And, everybody knows media files are generally large or heavy in size, which increases the total database size also. This will somehow increase the browser timeout and have an adverse effect on the performance of the SharePoint application.

Solution

Now, to avoid this situation, it is always recommended to fix this SharePoint file size error. If there are multiple media files, then it is suggested to save or move them to an external storage device.

Problem #2 – Unnecessary Data Take Space

It is obvious that after some time, the data becomes useless and not required by the user. Therefore, to manage or create storage space for new data, a user has to remove the unnecessary data from time to time. If this is not taken care of at the time, then it will definitely start creating issues in SharePoint application.

Solution

To overcome this storage space issue, a user is advised to Shift + Delete the data that is not necessary to free up the storage space on the cloud for new data.

Problem #3 – Database Stored in SQL Server

SharePoint database is stored in an unstructured form on the SQL Server. However, the data is stored as the BLOB (Binary Large Objects) and in the case of SharePoint, the database becomes large in size. Moreover, it uses a large number of SQL resources and whenever a user works on SharePoint, each process takes lots of time.

Solution

In this case, a user can shuffle BLOB database to the SQL secondary storage such as NAS (Network Attached Storage).

Problem #4 – Missing Site Templates

This is one of the commonly faced errors by the users when they upgrade SharePoint from one version to another. Because sometimes while doing so, site templates get deleted, which generate an error.

Solution

Look for the site definition on the earlier server. After that, simply upgrade it to support the latest version, and install it on the upgraded server.

One Stop Solution to Overcome All Troubles of SharePoint

The above discussed errors are just highlights of the issues related to SharePoint problems whose main reason is storage limit. Now, to stop them from occurring in the future, one needs to look for some SharePoint Issues alternatives. There can be several possible reasons that result in issues in SharePoint and the worst case is data loss.

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Custom Search Script in SharePoint 2013?

Jan 22nd

Posted by Peter in Other Related Post

This article will explain the PowerShell script that searches for files within document libraries in SharePoint (farm level, site collection level, web level etc.) based on the search parameters you provide. It can also be used for searching in SharePoint for any files with specified extension. The results are returned in .CSV format.

Examples of scenarios

Search the entire farm for files that have names like “Training Copy”.
Search the site collection http://sharepoint.mydreambox.com/sites/site1 for all PDF files, RDL files, etc.
Search the web http://sharepoint.mydreambox.com/sites/site1/web1 for the file named “AXL8rt.docx”, etc.

Usage of the Script

Replace the $webApp, $sites, etc. with appropriate values
Replace the $searchKey with the desired search queries or file extension that is to be searched for
Make sure the account that is running these scripts have necessary privileges in SharePoint

Script use cases

The code is presented for four different cases,

Searching for an entire farm
Searching within a web application
Searching within a site collection
Searching within a web

Output

The output will be in the form of a CSV file, as displayed below. It will contain all the file location URLs.

Case I – For searching within the entire farm

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)
{
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

$sites = Get-SPSite -Limit All
$searchKey = ".rdl"
$results = @()

foreach ($site in $sites)
{
foreach ($web in $site.AllWebs)
{
Write-Host Searching within $web.Url
foreach ($list in $web.Lists)
{
if($list.BaseType -eq "DocumentLibrary")
{
foreach($item in $list.Items)
{
if($item.Name.Contains($searchKey))
{
$RowDetails = @{
“File Location” = $web.Url + "/" + $item.Url
}
$results += New-Object PSObject –Property $RowDetails
}
}
}
}
}
}
$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

Case II - For searching within a Web Application

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)
{
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

$webApp = "http://sharepoint.dreambox.com"
$sites = Get-SPSite -WebApplication $webApp -Limit All
$searchKey = "Self Improvement"
$results = @()

foreach ($site in $sites)
{
foreach ($web in $site.AllWebs)
{
Write-Host Searching within $web.Url
foreach ($list in $web.Lists)
{
if($list.BaseType -eq "DocumentLibrary")
{
foreach($item in $list.Items)
{
if($item.Name.Contains($searchKey))
{
$RowDetails = @{
“File Location” = $web.Url + "/" + $item.Url
}
$results += New-Object PSObject –Property $RowDetails

}
}
}
}
}
}
$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)

{

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

}

$sites = Get-SPSite -Limit All

$searchKey = ".rdl"

$results = @()

foreach ($site in $sites)

{

foreach ($web in $site.AllWebs)

{

Write-Host Searching within $web.Url

foreach ($list in $web.Lists)

{

if($list.BaseType -eq "DocumentLibrary")

{

foreach($item in $list.Items)

{

if($item.Name.Contains($searchKey))

{

$RowDetails = @{

“File Location” = $web.Url + "/" + $item.Url

}

$results += New-Object PSObject –Property $RowDetails

}

$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

Case II - For searching within a Web Application

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)

{

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

}

$webApp = "http://sharepoint.dreambox.com"

$sites = Get-SPSite -WebApplication $webApp -Limit All

$searchKey = "Self Improvement"

$results = @()

foreach ($site in $sites)

{

foreach ($web in $site.AllWebs)

{

Write-Host Searching within $web.Url

foreach ($list in $web.Lists)

{

if($list.BaseType -eq "DocumentLibrary")

{

foreach($item in $list.Items)

{

if($item.Name.Contains($searchKey))

{

$RowDetails = @{

“File Location” = $web.Url + "/" + $item.Url

}

$results += New-Object PSObject –Property $RowDetails

}

$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

Case III – For searching within a Site Collection

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)
{
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

$site = Get-SPSite “http://sharepoint.dreambox.com/sites/site1”
$searchKey = ".docx"
$results = @()


foreach ($web in $site.AllWebs)
{
Write-Host Searching within $web.Url
foreach ($list in $web.Lists)
{
if($list.BaseType -eq "DocumentLibrary")
{
foreach($item in $list.Items)
{
if($item.Name.Contains($searchKey))
{
$RowDetails = @{
“File Location” = $web.Url + "/" + $item.Url
}
$results += New-Object PSObject –Property $RowDetails

}
}
}
}
}
$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)

{

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

}

$site = Get-SPSite “http://sharepoint.dreambox.com/sites/site1”

$searchKey = ".docx"

$results = @()

foreach ($web in $site.AllWebs)

{

Write-Host Searching within $web.Url

foreach ($list in $web.Lists)

{

if($list.BaseType -eq "DocumentLibrary")

{

foreach($item in $list.Items)

{

if($item.Name.Contains($searchKey))

{

$RowDetails = @{

“File Location” = $web.Url + "/" + $item.Url

}

$results += New-Object PSObject –Property $RowDetails

}

$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

Case IV – For searching within a Web

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)
{
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

$web = Get-SPWeb “http://sharepoint.dreambox.com/sites/site1/web1”
$searchKey = ".pdf"
$results = @()

foreach ($list in $web.Lists)
{
if($list.BaseType -eq "DocumentLibrary")
{
foreach($item in $list.Items)
{
if($item.Name.Contains($searchKey))
{
$RowDetails = @{
“File Location” = $web.Url + "/" + $item.Url
}
$results += New-Object PSObject –Property $RowDetails
}
}
}
}

$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null)

{

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

}

$web = Get-SPWeb “http://sharepoint.dreambox.com/sites/site1/web1”

$searchKey = ".pdf"

$results = @()

foreach ($list in $web.Lists)

{

if($list.BaseType -eq "DocumentLibrary")

{

foreach($item in $list.Items)

{

if($item.Name.Contains($searchKey))

{

$RowDetails = @{

“File Location” = $web.Url + "/" + $item.Url

}

$results += New-Object PSObject –Property $RowDetails

}

$results | Export-CSV –Path C:\MySearchedFiles.csv -NoTypeInformation

European Sharepoint 2013 Hosting Blog

SharePoint Hosting – Custom RSS SPFx Feed WebPart In Modern UI

Challenge

Solution

React SharePoint Framework Web part

SharePoint 2013 Hosting – HostForLIFE :: How To Use PnP React Accordion Control In SPFx?

Implementation

SharePoint 2013 Hosting – HostForLIFE :: Managing Site Storage In SharePoint Online

Overview

Site Storage in SharePoint Online

Site storage configuration

Manage site storage for individual sites

PowerShell support

Summary

How To Fix SharePoint 404 Error After Content Database Migration?

Issue Description

Background of the issue

Example

Solution

SharePoint 2013 Hosting – HostForLIFE :: How To Fix SharePoint Errors In A Few Minutes?

Common SharePoint Errors Encountered By Users, With Solutions

Problem #1 – Increase in Database Size

Problem #2 – Unnecessary Data Take Space

Problem #3 – Database Stored in SQL Server

Problem #4 – Missing Site Templates

One Stop Solution to Overcome All Troubles of SharePoint

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Custom Search Script in SharePoint 2013?

BLOGROLL

Featured On

European Sharepoint 2013 Hosting Blog

SharePoint Hosting – Custom RSS SPFx Feed WebPart In Modern UI

Challenge

Solution

React SharePoint Framework Web part

SharePoint 2013 Hosting – HostForLIFE :: How To Use PnP React Accordion Control In SPFx?

Implementation

SharePoint 2013 Hosting – HostForLIFE :: Managing Site Storage In SharePoint Online

Overview

Site Storage in SharePoint Online

Site storage configuration

Manage site storage for individual sites

PowerShell support

Summary

How To Fix SharePoint 404 Error After Content Database Migration?

Issue Description

Background of the issue

Example

Solution

SharePoint 2013 Hosting – HostForLIFE :: How To Fix SharePoint Errors In A Few Minutes?

Common SharePoint Errors Encountered By Users, With Solutions

Problem #1 – Increase in Database Size

Problem #2 – Unnecessary Data Take Space

Problem #3 – Database Stored in SQL Server

Problem #4 – Missing Site Templates

One Stop Solution to Overcome All Troubles of SharePoint

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Custom Search Script in SharePoint 2013?

BLOGROLL

Featured On

Tags