Sitecore PowerShell - Create a report with all referenced items by Lookup Items

In case if you have a list of lookup items and you would like to get a Sitecore PowerShell report of all the referenced items in Sitecore, you can make use of the below script. Also this script demonstrates the usage of PSObject by which you can create custom object and render it in the output window. This approach is using Link database and rebuilding the link database helps you to get the most accurate results. 

With PSObject, you can merge two different object and create a new custom object which can be used for rendering the results. Instead of using multi-dimensional arrays, this can be a better approach. 

	<#
	.SYNOPSIS
	Lists all referenced items by lookup items.
	.NOTES
	NEHEMIAH JEYAKUMAR
	#>
	#
	# INPUT / CONFIGURATION
	#
	$props = @{
	Title = "Lists all referenced items By Lookup Items"
	Description = "Lists all referenced items By Lookup Items"
	OkButtonName = "Run Report"
	CancelButtonName = "Cancel"
	Parameters = @(
	@{ Name = "lookupRootItem"; Title = "Lookup Item Root Folder"; Editor = "droptree"; Source = "/sitecore/Content/" }
	@{ Title = "Note"; Value = "Select the root (folder) of the Lookup Items."; Editor = "info" }
	)
	}
	$result = Read-Variable @props
	if($result -ne "ok") {
	Close-Window
	Exit
	}
	filter Where-HasGetReferencePages{
	param([Parameter(Mandatory=$TRUE,ValueFromPipeline=$TRUE)][Sitecore.Data.Items.Item]$item)
	$linkDb = [Sitecore.Globals]::LinkDatabase
	$referredItems = $linkDb.GetReferrers($item)
	foreach($rItem in $referredItems) {
	$pageItem = Get-Item -Path "master:" -ID $rItem.SourceItemID
	New-Object PSObject @{ LookupItemTitle = $item.Name; PageName = $pageItem.Name; PagePath = $pageItem.Paths.FullPath; PageItem = $pageItem }
	}
	}
	#Start Executing the Report
	$lookupItems = Get-ChildItem -Path master: -ID $lookupRootItem.ID -Recurse | Where-HasGetReferencePages
	if ($lookupItems.Count -eq 0)
	{
	Show-Alert "Did not find any items with forms";
	}
	else
	{
	# Setup a hashtable to make a more readable script.
	$props = @{
	InfoTitle = "Pages List"
	InfoDescription = "Lists all pages with item reference"
	PageSize = 25
	}
	$lookupItems | Show-ListView @props -Property `
	@{ Label = "Lookup Item Name"; Expression = { $_.LookupItemTitle } },
	@{ Label = "Page Name"; Expression = { $_.PageName } },
	@{ Label = "Page Path"; Expression = { $_.PagePath} },
	@{ Label = "Template"; Expression = { $_.PageItem.TemplateName} }
	}
	Close-Window

view raw ScPwsh-items-by-lookup-items.ps1 hosted with ❤ by GitHub

Sitecore Upgrade - Codebase Upgrade - Migrate from packages.config to PackageReference

We have been always using packages.config file to manage the nuget package references. Instead of config file, PackageReference has been introduced to provide benefits for the developers. 

Benefits:

1. Instead of showing all the dependencies in the packages.config file, only top level dependencies will be added as part of PackageReference. This gives a clean and simple view on the references. 
2. Ability to manage all the project level configuration like package references in a single csproj file itself.
3. Adding and removing packages are faster compared to Packages.config file. 

Migration of Packages.config to PackageReferences

To migration all the existing references, right-click the References node in Solution Explorer, and select the Migrate packages.config to PackageReference command.

Default to PackageReferences:

In order to add packages to PackageReferences by default, open Tools > NuGet Package Manager > Package Manager Settings menu, change the Default package management format to PackageReference.