I needed to calculate the total storage space used across multiple asset sources during my analysis. One of the most critical sources was the Sitecore Media Library, and after some googling, I quickly realized there wasn’t an easy way to calculate the total size directly from the CM server, without involving SQL queries or manual summations from reports. So, I built a simple and effective Sitecore PowerShell Extensions (SPE) script that gives you the total Media Library size in MB directly from the CM interface. No database access required!

Another goal was scored by the SPE-only Alliance!

The Script

Here’s the full PowerShell script that can be run in Sitecore PowerShell ISE:

Output Example:

Total Media Library Size: 1473.92 MB

I hope this little script helps you start the weekend with one less thing on your to-do list! If you give this script a try, please let me know how it worked for you.

And if you have improvements or tweaks, feel free to share them — after all, that’s what makes the Sitecore community so awesome!

• Sitecore Powershell Extensions (SPE) 7.0 introduces advanced packaging features, but you can also enjoy them in past SPE versions by using our package or Gist.
• You can now selectively include linked items in packages, avoiding the classic all-or-nothing approach.
• Learn how the features work and how to use them.

Introduction

Get ready for an exciting update, folks! Sitecore PowerShell Extensions (SPE) 7.0 is rolling out by the end of this year with some seriously cool new features in the packaging department. And guess what? I had the privilege of implementing these features, which were received very positively by the SPE team (shoutout to the amazing Michael West for his support!)

Also available for older versions of SPE

But fear not, even if you’re using a lower version of SPE, you can still reap the benefits by installing the necessary scripts using the following package: Advanced-Packaging-Features-1-0-zip. Or manually creating the 5 scripts at their respective paths according to this Gist.

Let’s dive into what these advanced packaging features are all about and how to make the most of them!

Rebuild your Link Database

First things first: the new features depend on the Link Database, so you will have to keep it up-to-date. If you are unsure, remember to give your Link Database a good rebuild for the “master” database, at least once before utilizing these features.

Unlocking Selective Packaging Superpowers

Currently, the SPE UI allows you to include linked items in your package, but it is an all-or-nothing deal. If you want to include media items linked to your selected item, you had no choice but to include all of them.

This is how the classic interface works, based on checkboxes:

Well, hold on to your keyboards because the new advanced packaging features now empower you to cherry-pick and selectively include linked items to your package.

The new UI will now show a different set of radio box configurations:

1. Do not include linked items: Linked items are not included in the package.
2. Include parent links only: Only items linked to the selected item (parent) will be considered for inclusion.
3. Include all linked items: All linked items (parent and children) will be considered for inclusion.

If you select either 2 or 3, a new screen will show, allowing you to cherry-pick the linked items you want to include in the package.

As you can see, there are tabs for each kind of linked items (Content, Media, Layouts, System, Templates), making the selection process much easier.

Using the New Features

To access these supercharged packaging powers, simply right-click on any item in the Content Editor and navigate to Scripts > Packaging.

• Important: Starting from SPE 7.0 the original features were substituted with the new ones, so you will see the list as above. However, if you’re using the new features in older SPE versions through my package or Gist, then you’ll notice I’ve added the new features to scripts sufixed with “Advanced”, as can be seen below:

Let’s take a closer look at the options available to fight the packaging confusion crimes, powered by Sitecore PowerShell Extensions:

Quick Download Tree as a Package (Advanced)

This option allows you to download as a package the selected item, along with the additional items you choose to include in the package. You can add child items, and selectively pick those linked items that deserve a spot in your package.

Start New Package (Advanced)

Choosing this option initiates the creation of a new package without immediately downloading it. Don’t worry, though – you’ll have the option to download it later. Once you’ve made this selection, a host of further options becomes available:

1. Add Item to Package (Advanced): This handy feature lets you add the selected item, along with any linked items you desire, to your package.
2. Add Tree to Package (Advanced): Selecting this option adds the selected item, all its children, and the linked items you choose to your package.
3. Preview Package Items (Advanced): Curious about the contents of your package before sealing the deal? This option lists all the items currently added to your package, allowing you to ensure you’ve got items you envisioned.
4. Download Package (Advanced): Finally, when you’re ready to unleash your package upon the world, hit “Download Package”. Your meticulously crafted package, complete with its formidable lineup of items, will be ready for action!

Conclusion

With Sitecore Powershell Extensions 7.0’s advanced packaging features, you now have the power to curate packages like never before. No more settling for all or nothing – select the linked items that truly matter and assemble the perfect package for your Sitecore adventures. So, go ahead and embrace these newfound packaging superpowers.
Get ready to package up greatness, fellow Sitecore heroes!

UPDATE: Michael West likes this solution and confirmed that it will be part of the next release of SPE (6.0), becoming my first contribution to SPE! Here is the ticket where this implementation is being tracked.

If you are a big fan of Sitecore Powershell Extensions like me, you probably know the Find-Item command, which allows searching your search index in Powershell scripts. This command, however, has an important limitation: you cannot use custom fields to filter and sort from the index. Due to this limitation, extended usage of Find-Item with custom code is usually not possible.

Internally Find-Item uses the base class “Sitecore.ContentSearch.SearchTypes.SearchResultItem“, which does not include any custom fields. What we usually do with C# is to create a class that inherits from “SearchResultItem“, adding our custom fields, such as below:

public class CustomSearchResultItem : SearchResultItem
{
   [IndexField("_templates")]
   [DataMember]
   public virtual List<ID> TemplateIds { get; set; }
}

The Find-Item command, however, does not allow using this field. For instance, the following script:

$props = @{
 Index = "sitecore_master_index"
 Where = "Paths.Contains(@0) And TemplateIds.Contains(@1)"
 WhereValues = [ID]::Parse("{D5B8857B-DE30-4616-84F5-812A7129ACD5}"), [ID]::Parse("{50FFE147-4F48-428B-A417-4D96DD2048FF}")
}
Find-Item @props

Will give the following error:

Find-Item : No property or field 'TemplateIds' exists in type 'SearchResultItem'

Because, yeah… that property is only defined at our custom class, not at SearchResultItem. To circumvent this limitation I built this special command.

Find-CustomItem

This command extends the original Find-Item, allowing you to pass a type that will be used instead of the base SearchResultItem class:

$props = @{
 Index = "sitecore_master_index"
 Type = [PSWebsite.Foundation.Indexing.SearchTypes.BaseSearchResultItem]
 Where = "Paths.Contains(@0) And TemplateIds.Contains(@1)"
 WhereValues = [ID]::Parse("{D5B8857B-DE30-4616-84F5-812A7129ACD5}"), [ID]::Parse("{50FFE147-4F48-428B-A417-4D96DD2048FF}")
}
Find-CustomItem @props

Create the custom command

In order to use Find-CustomItem in your project, you should:

1. Add NuGet references to Sitecore.ContextSearch and Sitecore.ContextSearch.Linq;
2. Add a reference to Cognifide.Powershell.dll;
3. Create a custom FindItemCommand class extending Cognifide.PowerShell.Commandlets.Data.Search.FindItemCommand;
   You can download the whole class here
4. Register your new command with an include patch – make sure the content is according to the following

<?xml version="1.0"?>
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
   <sitecore>
      <powershell>
         <commandlets>
            <add Name="Find Item" type="PSWebsite.Foundation.Indexing.Powershell.Commandlets.FindItemCommand, PSWebsite.Foundation.Indexing" />
         </commandlets>
      </powershell>
   </sitecore>
</configuration>

Limitations

Not all parameters from Find-Item are supported by Find-CustomItem. If you use any of the unsupported parameters along with any custom properties, it will cast the query to the base SearchResultItem, and give the same error as the original Find-Item command.

Supported parameters:

• Index
• Where
• WhereValues
• OrderBy
• First
• Last
• Skip

Unsupported parameters:

• Criteria
• Predicate
• ScopeQuery