Learning lessons for Sitecore, C#, .NET, SQL Server

Fixing Sitecore XM Cloud Local Installation Issues with Docker and BitLocker

2025-09-06T14:18:00.006+05:30

When setting up Sitecore XM Cloud locally, many developers face errors with Docker Desktop on Windows. The root cause is often the latest Docker versions (e.g., 4.45) conflicting with BitLocker encryption and storage drivers.

In this blog, I’ll walk you through the actual problem, the errors you may encounter, and the fixes that finally worked for me.

The Problem: Docker Desktop + BitLocker

After updating Docker Desktop to the latest version, I started facing issues running Sitecore XM Cloud containers. Even a simple container test like:

docker run --isolation=hyperv mcr.microsoft.com/windows/nanoserver:ltsc2022 cmd /c echo hello

failed with errors such as:

FSCTL_EXTEND_VOLUME \\?\Volume{GUID}: The media is write protected.

and later:

hcsshim::ExpandScratchSize failed in Win32: The system cannot find the file specified. (0x2)

This turned out to be a conflict between Docker’s Windows storage driver and BitLocker encryption.

Solution 1: Downgrade Docker Desktop

The easiest fix is to downgrade Docker Desktop to a stable version without this bug. Version 4.37.1 works perfectly.

Steps:

1. Uninstall Docker Desktop (latest version).

2. Download and install Docker Desktop 4.37.1 (https://docs.docker.com/desktop/release-notes/).

3. Restart your machine.

Solution : Update Docker Engine Settings

Another issue you may face is the buildkit warning when building containers:

Docker Compose is configured to build using Bake, but buildkit isn't enabled

To fix this, update your Docker Engine configuration:

{
"dns": [
"8.8.8.8"
],
"experimental": false,
"features": {
"buildkit": false
}
}

After saving the file, restart Docker Desktop for changes to take effect.

Solution : Fixing the hcsshim::ExpandScratchSize Error

If you see this error:

hcsshim::ExpandScratchSize failed in Win32: The system cannot find the file specified. (0x2)

it means your Docker Windows storage layers are corrupted.

Fix: Clean Docker’s Windows storage

Run this PowerShell as Administrator:

Stop-Service com.docker.service
Stop-Service docker

# Remove Windows container layers
Remove-Item -Recurse -Force "C:\ProgramData\Docker\windowsfilter" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "C:\ProgramData\Docker\containers" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "C:\ProgramData\Docker\image\windowsfilter" -ErrorAction SilentlyContinue

Start-Service com.docker.service
Start-Service docker

Now, test with a clean Windows container:

docker pull mcr.microsoft.com/windows/servercore:ltsc2022
docker run --rm --isolation=hyperv mcr.microsoft.com/windows/servercore:ltsc2022 cmd /c echo hello

✅ You should now see: hello

Final Thoughts

If you’re running Sitecore XM Cloud locally on Windows, here’s the checklist that worked for me:

- Downgrade Docker Desktop to 4.37.1

- Add correct Docker Engine settings to disable buildkit

- Clean up corrupted windowsfilter storage if you hit hcsshim::ExpandScratchSize errors

With these steps, I was finally able to get Sitecore XM Cloud running smoothly on my local machine without Docker crashes.

Sitecore Personalize Training

2025-07-14T17:41:00.003+05:30

I’m glad to share that I have recently completed the Sitecore Personalize Instructor-Led Training (ILT)—an engaging and practical learning program focused on helping teams deliver optimized, personalized customer experiences using Sitecore’s Personalize solution.

💡 About the Course

The Sitecore Personalize ILT is designed specifically for developers and business analysts who want to build the skills needed to create, test, and refine dynamic experiences across channels. This course goes beyond theory to demonstrate exactly how personalization can be operationalized and measured.

⏳ Duration

The training consists of 4 hours of live instruction, interactive demonstrations, and guided exercises.

🛠️ Prerequisites

To get the most value from the course, it is recommended that participants have experience with:

HTML, CSS libraries, and JavaScript
Any modern front-end framework (e.g., React, Angular)
Prior completion of the Sitecore Personalize e-Learning
If planning to complete the Sitecore CDP ILT, doing so before this course is also recommended

These foundations help ensure a smooth learning experience with the hands-on components.

📚 Course Modules Covered

The course covered a well-structured set of modules to build familiarity and confidence with the platform:

Defining Experiences
Understanding how experiences are structured in Sitecore Personalize.
Templates
Leveraging pre-built and custom templates to accelerate experience creation.
Web Experiences
Creating and managing web-based personalization campaigns.
Full Stack Interactive Experiences
Building experiences that combine server-side and client-side personalization.
Full Stack Triggered Experiences
Configuring triggered interactions that respond to customer behavior in real time.
Apply Experiments & A/B Tests
Setting up experiments, defining test variants, and managing traffic allocation.
Traffic Allocation
Strategies for splitting audience traffic across experiences and experiments.
Evaluate Real-Time Audiences and Segments
Working with real-time and batch segments to target the right customers.
Create Realtime Audience
Building audiences dynamically as users engage.
Evaluate Decisioning
Understanding the Sitecore decisioning engine to power dynamic personalization.
Decision Model Overview
Learning how to model decision logic and apply business rules.
Apply Offers in Decision Model
Using offers in decision models to optimize conversions and engagement.

🌟 Why This Training Matters

Personalization is no longer optional—it’s essential for any brand that wants to build lasting customer relationships. This course provided actionable knowledge on:

Defining and delivering personalized experiences at scale
Experimenting and optimizing based on data
Combining real-time insights with decisioning for impactful campaigns

With these capabilities, teams can create highly relevant interactions that drive engagement and conversions.

🙌 Next Steps

Having completed the Sitecore Personalize ILT, I am excited to put these skills into practice—designing data-driven personalization strategies and helping organizations maximize the value of their Sitecore investments.

If you’re exploring Sitecore Personalize or have experiences to share about your journey with the platform, I’d be glad to connect and exchange ideas!

Sitecore CDP Training

2025-07-14T17:39:00.002+05:30

I’m excited to share that I’ve recently completed the Sitecore CDP (Customer Data Platform) Instructor-Led Training (ILT)—an intensive, hands-on learning experience designed to equip developers and business analysts with practical skills in leveraging Sitecore’s powerful CDP capabilities.

💡 About the Course

The Sitecore CDP ILT is a focused training program that goes beyond theory and dives deep into the platform’s architecture, data model, APIs, and best practices. Whether you’re working on implementation, integration, or optimization of customer data strategies, this training provides a solid foundation to help you succeed.

⏳ Duration

The course spans 4 hours of interactive instruction, live demonstrations, and Q&A with Sitecore experts.

🛠️ Prerequisites

To get the most out of this course, it is recommended that participants have experience with:

HTML, CSS libraries, and JavaScript
Familiarity with APIs and Postman
Prior completion of the Sitecore CDP eLearning modules

These prerequisites ensure that attendees can follow the technical exercises and engage meaningfully with the platform.

📚 Course Modules Covered

The training was structured into comprehensive modules, including:

Explore Sitecore Customer Data Platform
Understanding the core purpose and capabilities of Sitecore CDP.
Architecture Overview
A look into how the platform components interact to deliver customer experiences.
Guest Profile & Data Model 2.1
Deep dive into how guest profiles are structured and how data is stored.
Analytics, Dashboard, and Data Lake Export
Learning to leverage built-in analytics and export insights for further analysis.
Ingest Real-Time Behavioral Data
Techniques for capturing user interactions in real-time.
Web Tagging with JavaScript Library
Implementing tags to track behavioral data on websites.
BrowserId vs GuestRef
Understanding identity resolution and tracking mechanisms.
Server-Side Stream Events
Setting up server-side event streams for consistent data ingestion.
Discover Interactive API & Data Extensions
Using APIs to enrich and manipulate data in the platform.
CRUD using REST API
Creating, reading, updating, and deleting records programmatically.
Apply Batch Data Ingestion
Steps and best practices to import data in bulk.
Export Segments with Audience Sync
Configuring real-time and batch segments and exporting them to other platforms.
Realtime Audience vs Batch Segments
Strategies for segmenting audiences based on real-time and historical data.

🌟 Why This Training Matters

Customer data is at the heart of delivering personalized digital experiences. This training not only clarified how Sitecore CDP works under the hood, but also provided practical approaches to:

Implement behavioral tracking
Integrate APIs effectively
Activate customer segments across channels

If you’re working on personalization, customer journey orchestration, or advanced analytics with Sitecore, I’d highly recommend this course.

🙌 Next Steps

With this training complete, I’m looking forward to applying these learnings in real-world projects to help organizations make the most of their customer data.

If you’re interested in learning more about Sitecore CDP or exchanging ideas on implementation best practices, feel free to connect!

Introducing the Sitecore Personalize Mindmap

2025-06-27T18:40:00.005+05:30

As a Sitecore enthusiast, I'm happy to share with you a project I've been working on - a comprehensive Sitecore Personalize Mindmap! 🤩

This mindmap is designed to help marketers, developers, and Sitecore professionals navigate the vast possibilities of personalization within the Sitecore ecosystem. Whether you're looking to enhance customer experiences, boost engagement, or drive conversions, this mindmap is your go-to resource.

What is Sitecore Personalize?

Sitecore Personalize is a powerful tool that enables you to create personalized experiences for your customers across multiple channels. By leveraging data, analytics, and machine learning, you can deliver tailored content, offers, and experiences that resonate with your audience

The Mindmap

For more Sitecore-related content, tips, and resources, follow me. Let's stay connected and continue the conversation!

Sitecore 10 .NET Developer Certification Exam: My Experience and Key Takeaways

2024-12-29T15:53:00.004+05:30

In December 2024, I cleared the Sitecore 10 .NET Developer Certification Exam, an essential milestone for developers working in the Sitecore ecosystem. This blog will walk you through my experience, the exam structure, preparation tips, and new questions that were included, which might help you prepare better.

Exam Structure

• Total Questions: 60
• Duration: 120 minutes
• Key Topics: No questions on ASP.NET Core, but the exam extensively covered:

o Sitecore xConnect
o xDB
o Sitecore Search and Indexing
o Sitecore Marketing Features

The questions were mostly multiple-choice and focused on practical scenarios, with several around the newer features in Sitecore. Here are new questions that they asked

1. What are the things required for Sitecore reporting?

a. Reporting API
b. Reporting services
c. Processing server
d. Reporting database

2. Whats the role of xConnect search collection?

a. Search the interaction

3. If you have to create a new model for xDB, what's the next step?

a. Create JSON file for model and deploy to xConnect project folder

4. What are the available options for IQuarable<Item> for search operations

a. GetResults
b. GetFacets
c. Where, orderby, contains
d. Groupby, sum

5. How to show same price for all version of each language in Sitecore item?

a. Make field Unversioned

6. What is the use of goals in Sitecore?

a. Measure the engagement and tracking

7. From the personalization rule what can be achieved

a. Hide the component,

b. Replace the layout of the component

8. New language is not available from available language list in Sitecore, how can you add new language?

a. Add new language from control panel

9. What is the use of <IncludeTemplate> in config file for search indexing

a. Indexing include only those items created from specific template

10. What can be achieved from Sitecore search operation

a. Search the products

11. How can you change the alt value of items that contains image field

Get the items, get all fields collection and change the alt field

13. What the use of “Item Include” in serialization file?

a. Specify the item path that need to serialise

14. Which of the following information is available within Workbox?

A. Number of editable data source items in all of Sitecore
B. Information about an item's originating template
C. Number of active campaigns divided by marketing team
D. Available workflow commands divided by associated workflow.

15. Which statement characterizes the Sitecore Extranet security domain?

A. It provides default access to the Sitecore identity server for users to log in to the appropriate environment areas.
B. It is an internal security domain for users that can access the Sitecore client tools and editing functionality.
C. It is the domain that contains user accounts as well as customized roles for managing read access to the website content.
D. It provides customized roles for controlling access to third-party environments such as a CRM or payment portal.

16. For non-SXA websites, why is it recommended to avoid setting presentation details directly on new content items?

A. Defining presentation details on standard values ensures all the fields related to an item's presentation are configured for access by content creators.
B. Sitecore does not allow presentation details to be changed at the content-item level, so they must be set and edited from the standard values of templates.
C. It allows all content items made from the same template to have the same presentation details by default and eliminates additional work during content creation.
D. It forces a prompt to appear when new content items are created so Content Authors can finalize the presentation details for the new content items.

17. Of the available options, which is a purpose of the field source in data templates?

A. The field source is a field property that designates where in the content tree the field obtains its data.
B. The field source is used to control a user’s access and permissions to folders and files in the content tree.
C. The field source defines how a field’s data appears in the Content Editor in the UI.
D. A field source maps a field to the underlying class representation in the API.

18. What is a reason to set the insert options on a specific item under the content node of the content tree?

A. To allow Content Authors to insert items into the content tree for all the templates they have access to
B. To allow Content Authors to insert items under the specific item in addition to what is included with the item's standard values
C. To allow Content Authors to insert new items under any item within the content tree
D. To allow Content Authors to insert items created from any system template into the content tree under the specific item

19. Your published layout.cshtml file contains a static placeholder with a “main” placeholder key and you want to add renderings to the presentation details of a templates standard values; however you cannot see the "main" placeholder key you added to the layout. Of the available options, which is the best explanation of what happened?

A. There is a missing configuration element in web.config for placeholders.
B. The wrong layout is associated with the current template.
C. A Sitecore publish is required to show placeholder keys when editing presentation details.
D. There is no placeholder settings item for the associated "main" placeholder key.

Preparation Tips

1. Video and PDF by Navan

I found the video and PDF tutorials by Navan extremely helpful. He comprehensively covered the topics and ensured I had a clear understanding of the Sitecore core concepts. PDF is available at here.

2. Focus Areas Beyond the Basics

Pay special attention to xConnect, xDB, and Marketing features, as these were prevalent in the exam.

3. Hands-On Practice

Create a small Sitecore project to familiarize yourself with search operations, workflows, goals, personalization rules, and field properties like "Unversioned" and "Shared."

Final Thoughts

Passing the Sitecore 10 .NET Developer Certification Exam requires a combination of practical experience, theoretical knowledge, and focused preparation. Be thorough with advanced topics like xConnect and xDB, as they often differentiate a prepared candidate from the rest. With the insights and preparation resources shared here, you’ll be better equipped to tackle the exam successfully.

Good luck to all aspiring Sitecore-certified developers!

Installing Content Hub Connector in Sitecore PaaS instance

2024-08-04T15:48:00.003+05:30

Sitecore Connect for content hub used to integrate Sitecore Content Hub to Sitecore XP or XM.

DAM stands for Digital Asset Management & DAM Module is used to interact with assets created in Content Hub inside Sitecore XP/XM. We can upload, search and insert assets from DAM directly from within Sitecore Content Editor or Experience Editor.

The Sitecore Connect for Sitecore Content Hub (DAM) Installation in Sitecore XP/XM PaaS can

be done via PowerShell Script.

You can deploy Sitecore Connect for Content Hub (SCCH) in an existing Azure PaaS

Environment.

To deploy in an existing PaaS environment, you must have an existing Sitecore XM or XP Azure

PaaS Environment and Microsoft Web Deploy installed.

Prepare an installation folder

To prepare an installation folder:

1. Create a local folder in your file system, for example, C:\Temp\SCCHInstallation.

2. Download the Sitecore Connect for Content Hub WDP Package from the Sitecore

download page and store it in the local folder you created.

3. In the local folder, create a new file and name it Deploy.ps1.

4. Open the new file with an editor such as notepad or VS Code and paste the following

script inside:

`[CmdletBinding(DefaultParameterSetName = "no-arguments")]
param(
[Parameter(HelpMessage = "Name of the resource group in Azure to target.")]
[string]$ResourceGroupName,[Parameter(HelpMessage = "Name of the web app in Azure to target.")]

[string]$WebAppName,
[Parameter(HelpMessage = "Path to the WDP to deploy to the target.")]
[string]$WdpPackagePath,
[Parameter(HelpMessage = "Content Hub Client Id.")]
[string]$CHClientId,
[Parameter(HelpMessage = "Content Hub Client Secret.")]
[string]$CHClientSecret,

[Parameter(HelpMessage = "Content Hub Username.")]
[string]$CHUserName,
[Parameter(HelpMessage = "Content Hub Password.")]
[string]$CHPassword,
[Parameter(HelpMessage = "Content Hub URI.")]
[string]$CHUri,
[Parameter(HelpMessage = "Content Hub Azure Service Bus connection string path in.")]
[string]$CHServiceBusEntityPathIn,
[Parameter(HelpMessage = "Content Hub Subscription name. (must be unique per Sitecore CM
deployment)")]
[string]$CHServiceBusSubscription,
[Parameter(HelpMessage = "Content Hub Azure Service Bus connection string path out.")]
[string]$CHServiceBusEntityPathOut,
[Parameter(HelpMessage = "Content Hub Search Page Uri.")]
[string]$CHSearchPage,
[Parameter(HelpMessage = "Content Hub External Redirect Key.")]
[string]$CHExternalRedirectKey = "Sitecore",
[Parameter(HelpMessage = "Path to MSDeploy.")]
[string]$MsDeployPath = "C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe",
[Parameter(HelpMessage = "Skips Azure Login when True.")]
[switch]$SkipAzureLogin = $False,
[Parameter(HelpMessage = "Amount of retry attempts. 6 by default which with default retryinterval would
come down to 1 minute.")]

Parameter(HelpMessage = "Amount of retry attempts. 6 by default which with default
retryinterval would come down to 1 minute.")]
[int]$RetryAttempts = 6,
[Parameter(HelpMessage = "Amount of time to wait between retries in milliseconds. 10000 by
default which is 10 seconds which adds up to 1 minute with default retry attempts.")]
[int]$RetryInterval = 10000
)
Add-Type -AssemblyName "System.IO.Compression.FileSystem"
function PreparePath($path) {
if(-Not (Test-Path $path)) {
$result = New-Item -Path $path -Type Directory -Force
} else {
$result = Resolve-Path $path
}
return $result
}
function UnzipFolder($zipfile, $folder, dst) {
[IO.Compression.ZipFile]::OpenRead(zipfile).Entries | Where-Object {
(.FullName−like".FullName−like"folder/*") -and ($.Length -gt 0)
} | ForEach-Object {
parent=Split−Path(parent=Split−Path(.FullName -replace $folder, '')
$parent = PreparePath (Join-Path $dst $parent)
$file = Join-Path $parent .Name[IO.Compression.ZipFileExtensions]::ExtractToFile(.
Name[IO.Compression.ZipFileExtensions]::ExtractToFile(_, $file, $true)
}
}
function DownloadWebsiteFile($filePath, $downloadFolderName) {
$basePath = Split-Path ".$downloadFolderName$filePath"
$fileName = Split-Path $filePath -Leaf
if(-Not (Test-Path ".$downloadFolderName$filePath")) {
New-Item -Path $basePath -Type Directory -Force
}
outFilePath=Join−Path(Resolve−Path"outFilePath=Join−Path(Resolve−Path"basePath") fileNam
eInvoke−WebRequest−Uri"https://fileNameInvoke−WebRequest−Uri"https://WebAppName.sc
m.azurewebsites.net/api/vfs/site/wwwroot/$filePath " -Headers @{"Authorization"=("Basic {0}" -
f $base64AuthInfo)} -Method GET -OutFile $outFilePath
}
function UploadWebsiteFile($filePath, uploadFilePath) { Invoke-WebRequest -Uri
"https://WebAppName.scm.azurewebsites.net/api/vfs/site/wwwroot/$filePath " -Headers

@{"Authorization"=("Basic {0}" -f $base64AuthInfo);"If-Match"="*"} -Method PUT -InFile
$uploadFilePath
}
function ApplyTransform($filePath, xdtFilePath) { Write-Verbose "Applying XDT transformation
'xdtFilePath' on '$filePath'..."
$target = New-Object Microsoft.Web.XmlTransform.XmlTransformableDocument;
$target.PreserveWhitespace = $true
$target.Load($filePath);
$transformation = New-Object Microsoft.Web.XmlTransform.XmlTransformation($xdtFilePath);
if ($transformation.Apply($target) -eq $false)
{
throw "XDT transformation failed."
}
$target.Save($filePath);
}
if(-Not (Test-Path MsDeployPath)) { Write-Host "MS Deploy was not found at
`"MsDeployPath`"!" -ForegroundColor Red
return
}
if(-Not $SkipAzureLogin) {
Write-Host "Logging into Azure..." -ForegroundColor Green
& az login
}
Write-Host "Fetching Publish Profile..." -ForegroundColor Green
$publishProfile = az webapp deployment list-publishing-profiles --resource-group
$ResourceGroupName --name WebAppName --query "[?publishMethod=='MSDeploy']" |
ConvertFrom-Json userName = publishProfile.userNamepublishProfile.userNamepassword
= publishProfile.userPWDpublishProfile.userPWDbase64AuthInfo =
[Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $userName,
$password)))
Write-Host "Preparing configuration..." -ForegroundColor Green
$xdtsPath = (PreparePath ".\xdts")
UnzipFolder $WdpPackagePath "Content/Website/App_Data/Transforms/scch/xdts" $xdtsPath
Get-ChildItem $xdtsPath -File -Include "*.xdt" -Recurse | ForEach-Object {
$targetWebsiteFile = .FullName.Replace(".FullName.Replace("xdtsPath", "").Replace("", "/").Replace(".xdt", "")
DownloadWebsiteFile targetWebsiteFile "Configuration" } configurationPath = (PreparePath
".\Configuration")
currentDateTime=(Get−Date).ToString("dd−MM−yyyy−hh−mm−ss")currentDateTime=(Get−Date)
.ToString("dd−MM−yyyy−hh−mm−ss")backupPath = (PreparePath ".\Backup-$currentDateTime")
robocopy $configurationPath $backupPath /s
Write-Host "Preparing transformations..." -ForegroundColor Green
nupkgPath=Join−Path(Resolve−Path".")"microsoft.web.xdt.3.1.0.nupkg"nupkgPath=Join−Path(R
esolve−Path".")"microsoft.web.xdt.3.1.0.nupkg"xdtDllBinPath = PreparePath ".\bin"
Invoke-WebRequest -Uri "https://www.nuget.org/api/v2/package/Microsoft.Web.Xdt/3.1.0 " -
OutFile $nupkgPath
UnzipFolder $nupkgPath "lib/netstandard2.0" $xdtDllBinPath
Add-Type -Path (Resolve-Path ".\bin\Microsoft.Web.XmlTransform.dll")
Write-Host "Fill ConnectionStrings..." -ForegroundColor Green
$connectionStringsXdtPath = Join-Path $xdtsPath "App_Config\ConnectionStrings.config.xdt"
((Get-Content -Path $connectionStringsXdtPath -Raw).Replace("{client_id}",
$CHClientId).Replace("{client_secret}", $CHClientSecret).Replace("{username}",
$CHUserName).Replace("{password}", $CHPassword).Replace("{uri}", $CHUri).Replace("{Azure
Service Bus connection string with incoming topic}",
$CHServiceBusEntityPathIn).Replace("{Subscription name}",
$CHServiceBusSubscription).Replace("{Azure Service Bus connection string with outcoming
topic}", $CHServiceBusEntityPathOut).Replace("{Content Hub search page URI}",
$CHSearchPage).Replace("{External redirect key}", $CHExternalRedirectKey)) | Set-Content -
Path $connectionStringsXdtPath
Write-Host "Running transformations..." -ForegroundColor Green
Get-ChildItem $xdtsPath -File -Include "*.xdt" -Recurse | ForEach-Object {
$targetFilePath = .FullName.Replace(.FullName.Replace(xdtsPath,
$configurationPath).Replace(".xdt", "")
if (-not(Test-Path targetFilePath -PathType Leaf)) { Write-Verbose "No matching file
'targetFilePath' for transformation '((.FullName)'. Skipping..."
} else {
ApplyTransform $targetFilePath $.FullName
}
}
Write-Host "Starting MSDeploy..." -ForegroundColor Green
verb="−verb:sync"verb="−verb:sync"source = "-source:package="$WdpPackagePath""
dest="−dest:auto,ComputerName=‘"https://dest="−dest:auto,ComputerName=‘"https://WebA
ppName.scm.azurewebsites.net/msdeploy.axd?site= WebAppName‘",UserName=‘"WebAppNa
me‘",UserName=‘"userName",Password="password‘",AuthType=‘"Basic‘""password‘",AuthType
=‘"Basic‘""iisWebAppParam = "-setParam:name="IIS Web Application
Name",value="$WebAppName""
coreParam="−setParam:name=‘"CoreAdminConnectionString‘",value=‘"Encrypt=True;TrustServ
erCertificate=False;DataSource=sitecore−xm−sql.database.windows.net,1433;InitialCatalog=s
itecore−xm−core−db;UserId=sqladmin;Password=Sitecore101;‘""coreParam="−setParam:nam
e=‘"CoreAdminConnectionString‘",value=‘"Encrypt=True;TrustServerCertificate=False;DataSour
ce=sitecore−xm−sql.database.windows.net,1433;InitialCatalog=sitecore−xm−core−db;UserId=sqladmin;Password=Sitecore101;‘""masterParam = "-setParam:name="Master Admin
Connection String",value="Encrypt=True;TrustServerCertificate=False;Data Source=sitecorexm-sql.database.windows.net,1433;Initial Catalog=sitecore-xm-master-db;User
Id=sqladmin;Password=Sitecore101;""
skipDbFullSql="−skip:objectName=dbFullSql"skipDbFullSql="−skip:objectName=dbFullSql"ski
pDbDacFx = "-skip:objectName=dbDacFx"
doNotDeleteRule="−enableRule:DoNotDeleteRule"doNotDeleteRule="−enableRule:DoNotDele
teRule"appOfflineRule = "-enableRule:AppOffline"
retryAttemptsParam="−retryAttempts:retryAttemptsParam="−retryAttempts:RetryAttempts"
retryIntervalParam="−retryInterval:retryIntervalParam="−retryInterval:RetryInterval"
verboseParam = "-verbose" Invoke-Expression "& 'MsDeployPath' --% $verb $source $dest
$iisWebAppParam $coreParam $masterParam $skipDbFullSql $skipDbDacFx
$doNotDeleteRule $appOfflineRule $retryAttemptsParam $retryIntervalParam $verboseParam"
Write-Host "Uploading configuration..." -ForegroundColor Green
Get-ChildItem $configurationPath -File -Recurse | ForEach-Object {
$targetWebsiteFile = .FullName.Replace(".FullName.Replace("configurationPath",
"").Replace("", "/")
UploadWebsiteFile $targetWebsiteFile $_.FullName
}
`

Update the connection strings for the Core and Master admin parameters.

Get ADO.NET connection information (optional - SQL Database only)

• Navigate to the database blade in the Azure portal and, under Settings, select Connection

strings.

• Review the complete ADO.NET connection string.

Copy the ADO.NET connection string if you intend to use it.

To successfully run the script and install and configure the connector, you must prepare the

following parameters:

• ResourceGroupName - the resource group name in Azure you want to install to.

• WebAppName - the name of the Web App in Azure you want to install to.

• CHClientId and CHClientSecret - a Content Hub OAuth Client ID and Client Secret. (See

Create an OAuth client for how to create these).

• CHUserName and CHPassword - a Content Hub username and password that is used as the

identification of Sitecore to access Content Hub.

• CHUri - the URI to your Content Hub instance, for example, https://mysandbox.stylelabs.io/ .

• CHServiceBusEntityPathIn and CHServiceBusEntityPathOut - to find these connection strings, in Content Hub, create a new action of the type M Azure Service Bus. Make a note of the connection strings in Hub out for CHServiceBusEntityPathIn and Hub in for

CHServiceBusEntityPathOut. For example:

CHServiceBusSubscription - the name of your Sitecore subscription.

• CHSearchPage - the URI to the Search Page you want to use to select DAM Assets, for

example, https://mysandbox.stylelabs.io/en-us/sitecore-dam-connect/approved-assets .

Run below commands in PowerShell admin mode

cd "C:\Temp\SCCHInstallation"

az account set –subscription “<subscription name or id>”

.\Deploy.ps1 -ResourceGroupName "<MyResourceGroup>" -WebAppName "<MyWebApp>" -
WdpPackagePath "C:\Temp\SCCHInstallation\Sitecore.Connector.ContentHub.WDP.5.0.0-
r00328.4145.scwdp.zip" -CHClientId "<ClientId>" -CHClientSecret "<ClientSecret>" -
CHUserName "<UserName>" -CHPassword "<Password>" -CHUri
"https://mysandbox.stylelabs.io/" -CHServiceBusEntityPathIn "<Hub out connectionstring>" -
CHServiceBusSubscription "<MySitecoreSubscription>" -CHServiceBusEntityPathOut "<Hub in
connectionstring>" -CHSearchPage "https://mysandbox.stylelabs.io/en-us/sitecore-damconnect/approved-assets"

Note:-

You must run this command against both your CM and your CD Azure PaaS Web Applications.

If you use the DAM functionality in SCCH, to allow the connector to select assets from Content Hub, add all hostnames to the Content-Security-Policy tag.

In the root folder (by default, wwwroot), open the web.config file. Make sure the URL of the

Content Hub instance (for example, content-hub-url.stylelabs.com ), other delivery hostnames

(for example, content-hub-url-delivery.stylelabs.cloud), and generated public links (for

example, content-hub-url.stylelabs.com:8686 ) are added as sources to the Content-Security-Policy tag.

For example:

<add name="Content-Security-Policy" value="default-src 'self' 'unsafe-inline' 'unsafe-eval'
https://apps.sitecore.net; img-src 'self' data: https://s.gravatar.com
https://*.wp.com/cdn.auth0.com/avatars https://ids-p-001.sitecorecontenthub.cloud/
https://ids-p-001.sitecorecontenthub.cloud/; style-src 'self' 'unsafe-inline'
https://fonts.googleapis.com; font-src 'self' 'unsafe-inline' https://fonts.gstatic.com; upgradeinsecure-requests; block-all-mixed-content; child-src 'self' https://ids-p001.sitecorecontenthub.cloud/ https://ids-p-001.sitecorecontenthub.cloud/; connect-src 'self'
https://ids-p-001.sitecorecontenthub.cloud/ https://ids-p-001.sitecorecontenthub.cloud/;
media-src https://ids-p-001.sitecorecontenthub.cloud/ https://ids-p001.sitecorecontenthub.cloud/;" />

Note

In Content Hub, you can configure different delivery hostnames for public links by using the

AssetExtensionDataConfigurationSetting setting.

If you have configured different hostnames, you must add all the hostnames as sources. You do

this in the Content-Security-Policy parameter, in the img-src, child-src and connect-src

properties.

Content Hub Configuration

To allow a Sitecore instance to access content hub, you must add a CORS configuration entry

with your Sitecore CM instance URL.

Navigate to: Manage -> Settings -> PortalConfiguration -> CORSConfiguration

Enter your CM instance URL (e.g. http://sc92.dev.local ) and click Save.

You must configure the CORS for Sitecore Digital Asset Management (DAM) to allow incoming

traffic from the Sitecore instance.

To configure the CORS:

• On the Sitecore DAM main menu, click Manage.

• Click Settings.

• On the Settings page, click PortalConfiguration, then click CORSConfiguration.

• Click Add, and add the URL for your Sitecore instance, for example, https://www.sitecore.instance.com .

• Save the changes.

Enable CMP or DAM

By default, installing Sitecore Connect for Content Hub (SCCH) disables both Sitecore Digital Asset Management (DAM) and Sitecore Content Management Platform (CMP). You must reenable CMP or DAM if you require the functionality they provide.

To enable CMP or DAM:

On your Content Management server, open the web.config file. The default location is

wwwroot/web.config

Enable DAM or CMP functionality:

• To enable DAM, change the configuration as follows: <add key="damEnabled:define"

value="yes"/>

• To enable CMP, change the configuration as follows: <add key="cmpEnabled:define"

value="yes"/>

Save the file, and refresh your browser window.

The Insert from Sitecore DAM icon is now available in the Rich Text Editor for fields that use the Rich Text Default profile. If you want to access DAM assets in profiles other than Rich Text Default:

• In the Core database, navigate to /sitecore/system/Settings/Html Editor Profiles/Rich Text Default/Toolbar 1.

• Copy the Insert from Sitecore DAM item.

• Navigate to the Rich Text Editor profile you intend to use, and paste the Insert from Sitecore

DAM item.

Security in Sitecore: An Expert Guide

2024-07-21T18:06:00.004+05:30

Introduction

In the ever-evolving digital landscape, securing web applications is of paramount importance. Sitecore, a powerful and flexible digital experience platform, offers a comprehensive set of tools and features to ensure the security of your website and data. This article aims to provide an in-depth understanding of security in Sitecore, covering best practices, configurations, and advanced strategies to protect your Sitecore environment.

The Importance of Security in Sitecore

Security is crucial in protecting sensitive data, maintaining the integrity of your website, and ensuring compliance with regulatory requirements. Security breaches can lead to data loss, financial loss, and damage to your organization's reputation. Sitecore provides robust security features to safeguard your content, user data, and application, making it an essential aspect of your overall digital strategy.

Database security recommendations

It focusses on protecting your data both at rest and in motion.

To secure data transmission between an instance of SQL Server and a client application (data in motion or transit), use Transport Layer Security (TLS) to encrypt the connection.

To secure physical files, such as data and log files (data at rest), use Transparent Data Encryption (TDE). TDE is configured on the SQL Server side and does not require any specific Sitecore configuration settings. TDE is enabled by default for newly deployed Azure SQL databases, but it is not enabled by default for on-premises deployments.

Important: TDE does not encrypt the communication channel or the data itself, meaning that anyone with database access can still read sensitive data.

For encrypting sensitive data at rest, use the Always Encrypted feature. This feature ensures a separation between those who own and process the data and those who manage it but must not access sensitive information. Only the client application can decrypt and utilize sensitive data.

Always Encrypted configures encryption for individual database columns containing sensitive data, so not all columns may be encrypted.

Note: Not all Sitecore databases support the Always Encrypted configuration. Supported Sitecore databases include the xDB Collection database and the Sitecore Cortex Processing database.

Control User Access to Web Resources

You can configure access privileges for web resources using the <location> tag in the Web.config file. The following example denies access to the /sitecore path for all users except for admin and webmaster:

<system.web>

</authorization>

</system.web>

</location>

You can also configure the Web.config file to use Windows ASP.NET groups and users.

Note: By default, only Core roles use the <location> tag, and each Core role is configured differently. We recommend auditing your location tags as part of your security review process.

Update the Administrator Password

Prior to deploying your Sitecore installation, it is essential to change the administrator password to a strong, secure password. This helps prevent unauthorized users from accessing the admin account using the default password.

Create a New Administrator Account

For additional security, Sitecore recommends creating a new administrator account with a unique name and disabling the default administrator account. This provides an extra layer of protection.

Update the Hash Algorithm for Password Encryption

By default, Sitecore uses the Microsoft ASP.NET membership provider for user management.

When setting up a new website, it is crucial to replace the default weak hash algorithm (SHA1) used for encrypting user passwords with a stronger one.

Steps to Change the Hash Algorithm:

Ensure you are logged in as an administrator while the SHA1 configuration is still active in both Sitecore XP and the Identity Server.

Modify the configuration files:

Ensure both Sitecore and the Identity Server use the same hash algorithm setting.

Update the web.config file:

In the <membership> node, set the hashAlgorithmType to a stronger algorithm. We recommend using SHA512.

Update Sitecore Identity Server:

If you are using Sitecore Identity, you must also change the algorithm in the Identity Server configuration. Specify the algorithm in the PasswordHashAlgorithm node to SHA512 in the \sitecore\Sitecore.Plugin.IdentityServer\Config\identityServer.xml file.

Restart the Identity Server:

Restart the Sitecore Identity app service.

Change the admin password:

Use the User Manager application to update the admin password so that it is hashed with the new algorithm.

Note: After changing the hash algorithm, you cannot manually type a new admin password to change it. Instead, click "Generate" to create a new hashed admin password.

Update other user passwords:

Ensure all user passwords are updated to be hashed with the new algorithm.

Enabling and Disabling Administrative Tools

Sitecore administrative tools can be helpful for troubleshooting issues in a production environment, but for security reasons, you must:

Always disable them as part of the deployment process.
Always disable them when they are not in use.
Never enable them on the Content Delivery and xDB Processing roles. It's safe to delete the administrative tools folder on these roles.
Only enable them on Content Management roles that are not exposed to the internet.

Administrative tools are ASPX files with .aspx extensions, located in the <webroot>\sitecore\admin\ folder and its subfolders.

Disabling an Administrative Tool

To disable an administrative tool:

Navigate to the administrative tools folder.
Click on the tool you want to disable.
Add .disabled to the tool's filename. For example, rename cache.aspx to cache.aspx.disabled.

Admin files

Disabling Client RSS Feeds

If your Sitecore installation contains sensitive information that you want to protect, you can disable the Sitecore client RSS feeds.

RSS technology allows users to follow an RSS link directly to the item specified in the feed's URL. Most RSS readers do not support authentication, meaning users subscribed to Sitecore client RSS feeds can access the specified items directly without identifying themselves through the Sitecore security system. However, the Sitecore security system verifies user authorization when they attempt any actions associated with the client feed.

If an unauthorized user gains access to the URL of a client RSS feed:

They can follow the link and view all the content in the client feed, even if their security permissions do not grant access to the item.
They cannot perform any actions on the content.
They cannot view any other content.
They cannot gain access to the username or password of the original feed owner.
They cannot modify the link to access other content.

Important: Sitecore users should not share client RSS feeds.

To disable Sitecore client RSS feeds:

Open the web.config file.
Locate the <httpHandlers> section (it may be called <Handlers> depending on your IIS pool).
Remove the following handler:

Removing this handler disables all client feeds available within Sitecore. Any public RSS feeds you have created will still be accessible to website visitors.

Disabling SQL Server Access from XSLT

Sitecore includes an xslExtension helper for use with SQL Server. It is strongly recommended to disable this helper if:

You do not need it.
You are not using Sitecore XSLT renderings.

To disable the xslExtension helper:

In the App_Config/Include folder, create a patch file. Name the file with a .config extension.
Insert the following code into the patch file:

<patch:delete/>

</extension>

</xslExtensions>

</sitecore>

</configuration>

Enhance Login Security

You can enhance the security of the Sitecore login page by taking the following steps:

Enable SSL: Make the login page accessible only through SSL.
Turn off autocomplete for usernames: Prevent Sitecore from automatically completing usernames during login. This is especially useful if content authors log in from shared or public computers.
Disable the "Remember me" checkbox: Remove the option for users to save their login credentials on the login page.

Steps to Implement:

Turn off autocomplete for usernames:

Open the sitecore.config file.
Set the Login.DisableAutoComplete setting to true. This disables autocomplete on the Sitecore login forms located at /sitecore/login/default.aspx and /sitecore/admin/login.aspx.

Disable the "Remember me" checkbox on the login page:

On the Sitecore Identity Server role, open the sitecore/Sitecore.Plugin.IdentityServer/Config/identityServer.xml file.
Set the AllowRememberLogin setting to false. This also ignores any existing "Remember me" cookies, requiring all users to log in again.

Disable the "Remember Last Logged In User Name" setting:

Open the sitecore.config file.
Set the Login.RememberLastLoggedInUserName setting to false. This prevents the browser from remembering the username of the last logged-in user.

Implementing these measures will significantly improve the security of your Sitecore login process.

Restrict Access to XML, XSLT, and MRT Files

To enhance the security of your Sitecore installation, you should limit access to XML, XSLT, and MRT files. This involves editing the web.config file with general Sitecore settings and disabling the web.config file with EXM settings.

Steps to Limit Access:

Open the web.config file with general Sitecore settings:

This file is located in the top-level folder of your installation or in the Website folder.

Add the following lines in the <system.webServer><handlers> section:

<system.webServer>

</handlers>

</system.webServer>

This configuration restricts access to all XML, XSLT, and MRT files.

Disable the web.config file with EXM settings:

This file is located in the \sitecore modules\Shell\EmailCampaign\ folder.

Allow Unrestricted Access to a Specific File Path

After restricting general access, you might need to allow access to specific files.

Open the web.config file with general Sitecore settings.
Add the following line before the handlers that limit access:

Replace sitemap.xml with the specific file to allow unrestricted access to.

Restrict Access to PhantomJS

By default, PhantomJS is not disabled on Content Delivery, xDB Processing, and xDB Reporting roles. It is used by Sitecore for content testing and generating thumbnails. To enhance security, you should move PhantomJS outside the webroot folder, limit its permissions, and disable it on roles where it is not needed.

Steps to Secure PhantomJS:

Move PhantomJS Outside the Webroot Folder:

By default, PhantomJS is located in the <webroot>\$(dataFolder)\tools\phantomjs\ folder. The $(dataFolder) variable defaults to App_Data, placing PhantomJS in <webroot>\App_Data\tools\phantomjs\.
This location can potentially expose the phantomjs.exe program file if Sitecore security settings are not properly configured.

Update Configuration Settings:

Sitecore references PhantomJS for content testing through the ContentTesting.PhantomJS.ExecutablePath setting in the <webroot>\App_Config\Sitecore\ContentTesting\Sitecore.ContentTesting.config patch file.
For thumbnail generation, Sitecore uses the following settings:

PhantomJsExePath references the phantomjs.exe file.
PhantomJsRenderScriptPath references the render.js file.

Example Configuration to Move PhantomJS:

Move the PhantomJS Folder:

Move the <webroot>\App_Data\tools\phantomjs\ folder to a new location, such as C:\phantomjs1\. Optionally, you can define separate folders for content testing and thumbnails (e.g., phantomjs1 for content testing, phantomjs2 for thumbnails).

Create a Patch File:

In the <webroot>\App_Config\Include\ folder, create a patch file named MovePhantomJSFolder.config.

Insert the Following Configuration:

</settings>

</sitecore>

</configuration>

Move Contents from the App_Data Folder:

Transfer the contents from the App_Data folder to the new data folder (e.g., D:\SC\Data).

Important Considerations:

The App_Data folder is defined by default in the dataFolder variable in the Sitecore.config file.
When creating a new location for PhantomJS.exe (e.g., C:\PhantomJs), ensure only the files originally found inside the <webroot>\App_Data\tools\phantomjs folder are moved to the new location.

By following these steps, you can secure your Sitecore installation by limiting access to PhantomJS and reducing potential vulnerabilities.

Protect Media Requests

The media request protection feature in Sitecore restricts media URLs with dynamic image-scaling parameters, ensuring that only valid server-generated requests are processed. This helps optimize server resource usage and disk space by avoiding unnecessary processing of invalid requests.

To enhance the security and functionality of media request protection, you can patch the Sitecore.Media.RequestProtection.config file.

Steps to Optimize Media Request Protection:

Create a Patch File:

In the App_Config\Include\ folder, create a new patch file named MediaRequestProtectionSecret.config (or another name of your choice).

Insert the Configuration Code:

Add the following code to the patch file:

<setting

name="Media.RequestProtection.SharedSecret" value="YourRandomGeneratedString"/>

</settings>

</sitecore>

</configuration>

Save the Patch File:

Save the newly created patch file to apply the changes.

Important Note:

Consistency in Multi-Server Environments:

In a multi-server setup, the same Media.RequestProtection.SharedSecret value must be used across all servers. This ensures that dynamic image scaling works correctly, regardless of which server generates the image URL and which server handles the request.

By implementing these changes, you can strengthen the protection of media requests and ensure efficient and secure handling of dynamic image-scaling requests in your Sitecore environment.

Remove Header Information from Responses

Enhancing security and saving bandwidth can be achieved by removing header information from responses sent by your website. These headers often reveal details about your website's framework that are unnecessary to disclose.

Remove the X-Aspnet-Version HTTP Header

The X-Aspnet-Version header reveals the version of ASP.NET being used, which can be useful for potential attackers. By removing this header, you not only save a small amount of bandwidth but also obscure this information.

To remove the X-Aspnet-Version HTTP header, add the following configuration to your web.config file:

<system.web>

</system.web>

Remove the X-Powered-By HTTP Header

The X-Powered-By header indicates which version of ASP.NET is being used. Removing this header helps prevent the exposure of this information.

To remove the X-Powered-By HTTP header, include the following code in your web.config file:

<system.webServer>

</customHeaders>

</httpProtocol>

</system.webServer>

Implementing these changes will contribute to your website's security by obscuring the details of your framework and saving a minimal amount of bandwidth.

Restrict Access to the Client

Disable Forms Authentication

To ensure Sitecore does not handle any authentication requests, you can disable Forms authentication.

To disable Forms authentication:

Open the <webroot>\Web.config file.
Locate the <authentication> node.
Modify the mode attribute from Forms to None.

Deny Access to the Copyrights Folder

The sitecore/Copyrights/ folder on the CD server contains license text files for third-party components used by Sitecore. To prevent unauthorized access to this folder, configure Sitecore to deny access.

To deny access to the folder:

Add the following setting to the <handlers> section of the web.config file on your CD server:

These measures will enhance security by restricting unauthorized access and ensuring that authentication requests are handled appropriately.

Disable the Upload Watcher

To ensure that files can only be uploaded to Sitecore through the Media Library and to maintain control over file uploads, you should disable the Upload Watcher. This will prevent automatic uploads of files placed in the upload folder to the Media Library.

To disable the Upload Watcher:

Open the web.config file.
Locate the <system.webServer><modules> section.
Remove the following line:

By disabling the Upload Watcher, you restrict file uploads to the Sitecore client interface, ensuring better management and security of uploaded files.

Secure Telerik Controls

Sitecore utilizes certain Telerik UI controls, which are only employed in a Content Management environment. To minimize security risks:

In Non-Content Management Environments:

Open the web.config file.
Remove the following nodes:

In Content Management Environments:

Configure the encryption keys for the Telerik upload control by modifying the web.config file.
In the <appSettings> section, add nodes for the Telerik configuration encryption keys:

</appSettings>

Replace YOUR_ENCRYPTION_KEY_HERE with a secure string of random characters and numbers. The key should be at least 32 characters long, with a maximum length of 256 characters.

Separate Content Management and Content Delivery Servers

To enhance security as part of a defense-in-depth strategy, it's crucial to minimize the exposure of your deployment.

Sitecore advises deploying distinct servers for Content Management (internal use only) and Content Delivery (public-facing) in a production environment. Your Content Management server should not be accessible from the internet.

If it is necessary to expose your Content Management server to the internet, you should:

Use HTTPS to encrypt communications with the Content Management server.
Implement IP Filtering to restrict access to a whitelist of approved clients.

Enforce a Strong Password Policy

Sitecore utilizes the Microsoft ASP.NET Membership Provider for user management by default. It is advisable to customize the password policy to align with your organization's security requirements.

In the web.config file, within the <membership> section, you can configure the following properties to enforce a robust password policy:

minRequiredPasswordLength
minRequiredNonAlphanumericCharacters
maxInvalidPasswordAttempts
passwordAttemptWindow
passwordStrengthRegularExpression

Protect Connection String Passwords from Unauthorized Access

Sitecore stores connection string passwords in the App_Config\ConnectionStrings.config file. To prevent unauthorized access to these passwords, it is advisable to encrypt this file.

For securing connection strings in PaaS deployments using Kudu:

Navigate to App Service, then Development Tools, and click on Advanced Tools.

Open Kudu.
Click on Debug console, select Powershell, and navigate to site/wwwroot/App_config. Open the ConnectionStrings.config file.

In the ConnectionStrings.config file, remove the values for the database connection strings and save the changes. For instance, remove the values for core, master, security, and web.

Go back to App Service and navigate to Settings, then Configuration. In the Connection strings section, click New connection string. Add the connection strings for all the databases you need and click OK.

Click Save to apply the changes.

Updates and Disaster Recovery

We recommend using the latest version of Microsoft Windows supported by Sitecore and ensuring that your system remains updated with the latest security patches. Utilize the Windows Update/Automatic Update service to keep your systems current.

Additionally, we advise developing a comprehensive disaster recovery plan that includes:

A strategy for obtaining new or temporary equipment.
Procedures for restoring backups.
Regular testing of the recovery plan.

Conclusion

Securing your Sitecore environment requires a comprehensive approach that encompasses application security, data protection, and infrastructure security. By following the best practices and strategies outlined in this article, you can ensure that your Sitecore deployment is secure and resilient against potential threats.

By following the detailed guidelines and implementing the solutions provided in this article, you will be well-equipped to secure your Sitecore environment and protect your digital assets from potential threats.

My Sitecore Contributions for Year 2023

2023-12-05T13:58:00.003+05:30

As the digital landscape continues to evolve, so does the realm of Sitecore development, with each passing year bringing new challenges, advancements, and opportunities. As I reflect on the strides made in 2023, I am thrilled to share my journey and contributions within the Sitecore community. Over the past year, my dedication to pushing the boundaries, exploring innovative solutions, and collaborating with fellow developers has led to a series of meaningful contributions that have enriched the Sitecore ecosystem. In this article, I aim to highlight some of my most impactful endeavors, shedding light on the tools, insights, and experiences that have shaped my involvement and growth within the vibrant world of Sitecore.

Around 80,000+ Blog views in 2023

As a testament to my commitment in delivering impactful content that connects with audiences, I am honored to achieve a milestone of 1,050,000+ total views on my blog articles, with approximately 80,000 views amassed solely in the year 2023. Over the past decade, I have remained steadfast in maintaining, curating, and sharing valuable Sitecore-related insights on my blog. Notably, my journey began with my inaugural Sitecore blog post published on June 5, 2013.

http://www.sitecorelessons.com/

Blog Analytics for 12 months

SUG Pune : Emotion Recognition Model

Presented a webinar as a Speaker in SUG Pune forum and conducted session on - From dummies to pro Utilizing Sitecore Edge Powered Recommendations Enhanced by an Emotion Recognition Model

Link

Published 26 blog articles

Published 26 blog articles for year 2023 on my blog site http://www.sitecorelessons.com/

Link

Total 24 recorded videos on My Sitecore YouTube channel

Recorded 24 videos on YouTube for this year on Sitecore available in on my YouTube channel.

ChatGPT with Sitecore
Sitecore Transfer : Your Last Minute Content Publish Option
Sitecore Mindmap
Simplest way to sort child items in Sitecore
OData Services in Sitecore
12 Approaches for Content Migration in Sitecore
Fastest and best way to upload images in Sitecore
Webhooks in Sitecore 10.3
Sitecore PowerShell scripts as a datasource
Sitecore Content Hub as a Secondary CMS : An Overview
How To: Embed Sitecore 10.3 form to external website page
Sitecore with CSharp REPL
Poster : 20 Years of Sitecore Journey
Sitecore SXA module: SmartFill
8 ways to Find and Replace text in Sitecore
Moving from Sitecore XP to Sitecore XM cloud
Sitecore Technology Radar
5 ways to set Alt text for images in Sitecore
Funny observations in Sitecore XM Cloud
Sitecore Public Feed Migration
A Comics : What is Sitecore DAM?
Sitecore CDP Comics
When NOT to use Headless CMS
Sitecore Comics

Link

SUG Bangalore - Sitecore Pipelines From dummies to pro

Speaker in SUG Bangalore and conducted session on - Sitecore Pipelines : From dummies to pro

Link

Speaker in SUGCON India 2023 Conference

I was a speaker in SUGCON India 2023 Conference and conducted session on "Utilizing Sitecore Edge-Powered Recommendations Enhanced by an Emotion Recognition Model" . Here is Recap summary of my blog for this 2 days event http://www.sitecorelessons.com/2023/08/recap-of-sugcon-india-2023.html

Link

Speaker in Sitecore User Group Pune

Presented webinar in Sitecore User Group Pune on topic - Sitecore Pipelines : From Dummies To Pro

Link

Sitecore Public Feed Migration

Sitecore Director of Developer Relations - Jason St-Cyr mentioned my timely video for Nuget outage reference in LinkedIn post. Here is my YouTube video for the same https://www.youtube.com/watch?v=2sjaBSLrXnY

Link

Sitecore Digital Asset Management Comics

Created a comics on Sitecore Digital Asset Management.

Link

Speaker in SUG Bangalore Group

Delivered webinar in Sitecore User Group Bangalore on - 15 ways of Content Migration to Sitecore

Link

Sitecore Technology Radar

Created Sitecore Technology Radar which can help organizations stay informed about these changes and make informed decisions about which technologies to adopt, trial, assess, or hold

Link

Speaker in Sitecore User Group in Delhi NCR

Delivered a session on Sitecore Content Migration on 15 April at the Sitecore User Group in Delhi NCR

Link

Sitecore CDP Comics

I created a comics on Sitecore CDP.

Link

Poster for 20 Years of Sitecore Journey

Created a jumbo poster for showing the 20 years of Sitecore journey.

Link

Sitecore Hackathon 2023 - SmartFill

I successfully created a Sitecore SXA module - SmartFill for the Sitecore Content and Experience Editor as a part of Sitecore Hackathon 2023.

YouTube link - http://www.sitecorelessons.com/2023/03/sitecore-hackathon-2023-smartfill.html

Blog article link - https://www.youtube.com/watch?v=cUCQejpMqYE

Link

Sitecore Comics

Created Sitecore comics which explain Content management systems in an engaging and entertaining way

Link

Sitecore Mindmap

I created a Sitecore Mindmap diagram for quick reference

Youtube link - https://www.youtube.com/watch?v=c_AYSyearOA

Link

15 Approaches For Content Migration to Sitecore

2023-11-09T12:14:00.000+05:30

Introduction

The purpose of this article is to comprehensively examine the various methods of content migration in Sitecore. It serves as a complete guide for both beginner and experienced Sitecore developers looking to embark on the journey of content migration.

This article begins by exploring the basic, inbuilt methods and progresses to more advanced and custom solutions, as well as third-party tools. It covers a range of common and less commonly used migration techniques in Sitecore.

Sitecore is a leading digital experience software used by organizations globally to create seamless, personalized digital experiences. Sitecore is an integrated platform powered by .Net CMS, commerce and digital marketing tools.

Data Migration

Data migration is the process of transferring data from one storage system to another, or from one format to another, in order to upgrade, consolidate or modernize the data. This process can occur within a single organization, between organizations, or even between different data storage systems and formats. The goal of data migration is to ensure that all data is accurately and efficiently transferred to the new system or format, and that data integrity is maintained throughout the process.

What is content migration in Sitecore?

Content migration in Sitecore refers to the process of moving items from one Sitecore instance to another. This can include migrating content, media, templates, and other items from one Sitecore environment to another. The goal of content migration is to ensure that the content in the new environment is accurate, up-to-date, and consistent with the data in the previous environment. Content migration can be a complex process and requires careful planning, testing, and execution to ensure that all data is properly moved and that there are no disruptions to the website or other systems that depend on the Sitecore environment.

It's important to note that data migration can be a intricate process that can take a lot of time and resources. Before performing any migration, it is essential to make a backup of the source and destination instances, and to test the migration in a development environment before migrating to production.

Content migration can be done in various ways as shown here

Sitecore Package

A Sitecore Package is a compressed archive file containing Sitecore items, files, and other assets that can be easily exported from one Sitecore instance and imported into another. Sitecore packages can include a range of different types of data, such as content, templates, media files, and configurations, and they are used to share and distribute data between Sitecore instances, or to transfer data from a development environment to a production environment.

Creating a Sitecore package in Sitecore is a relatively simple process.

Sitecore packages can be created using the Sitecore Package Designer, and they can be imported using the Sitecore Installation Wizard or the Package Installer module.

Package Designer is a more advanced method of creating a package, as it allows you to include dependencies, files and assemblies in the package.

Here are the steps to create package:

Launch the Package Designer: Go to the Sitecore Desktop, click on the Start button, and select Development Tools > Package Designer.
Create a new package: Click on the New Package button to create a new package and enter a name and description for the package.

Select the items to include in the package: Use the Select Items tab to select the items you want to include in the package. You can select items from the content tree, and you can also use search and filters to find specific items.
Configure the package options: Use the Options tab to configure the package options, such as whether to include subitems, whether to include binary data, and whether to include security information.
Save and create the package: Once you have configured the package options, click on the Save & Build Package button to save the package and create the .zip file.
Install the package: Use the Sitecore Installation Wizard or the Package Installer module to install the package into the target Sitecore instance. You can also upload the package to a shared network location and install it from there.

Pros

Out of the box feature
It allows you to include items, roles, dependencies, files and assemblies in the package.
It allows to include dynamic items based on filters

Cons

Package with heavy size may be failed to create or install.

Administration Tools - Package Item

The Package Item tools can be used to generate packages of items with their dependencies. The UI here is much more limited but the tool will package the dependencies of an item as well: all item references, presentation items if you’re using Webforms, custom assemblies, workflow items and templates. Its very useful for creating packages of pages for distribution.

Follow below steps to create package:

Log in to Sitecore as an administrator.
Navigate to /sitecore/admin/PackageItem.aspx in your web browser.
Specify database and items paths
Select if you need their descendants as well in package.
Click on Generate and download Package button.

Pros:

Easy to use
Create package with descendants and dependents items.

Cons:

Require admin access
All admin pages access are normally disabled on production environment.

Sitecore Media Upload Watcher

The Sitecore Media Upload Watcher is a feature that enables Sitecore to automatically detect changes in the server file system and create media library items with the corresponding files automatically attached and organized into the appropriate directories within the upload folder.

This method of uploading media is often more efficient, particularly when uploading a large number of files, than other uploading methods.

Steps to upload images:

Copy and paste your all images in /upload folder of website root directory.
In few seconds, you will get all these images in Sitecore media library as a media item automatically.

Disable the Upload Watcher

Disabling the Upload Watcher in Sitecore, specially on production environment, is one way to ensure that files can only be uploaded to the Media Library from within the Sitecore client, giving you better control over the files that are uploaded.

When the Upload Watcher is disabled, any files placed in the upload folder will not automatically be added to the Media Library.

To disable the Upload Watcher:

• Open the web.config file and remove/comment the following line from the <system.webServer><modules> section:

Pros:

Time-saving: Media Upload Watcher automates the process of uploading media files, which saves time compared to manually uploading files.
Consistency: Media Upload Watcher ensures that media files are uploaded in a consistent way, reducing the likelihood of errors or inconsistencies.
Flexibility: Media Upload Watcher provides various options for media file uploads, including creating new media items or updating existing ones, which allows developers to choose the best option for their use case.
Scalability: Media Upload Watcher can handle large numbers of media files, which can be a time-consuming task when done manually.
Customizable: Media Upload Watcher can be customized to suit the specific needs of a Sitecore instance, enabling developers to create a tailored solution.

Cons:

Dependency on the tool: Developers who use Media Upload Watcher may become dependent on the tool for media file uploads, which can be problematic if the tool becomes unavailable or is discontinued.
Developer dependency: As images need to copy in “Upload” folder which generally can only be accessed by developers or by technical people.
Configuration: Media Upload Watcher requires configuration and setup, which may require significant effort to set up and configure, especially when uploading large numbers of media files.
Limited functionality: Media Upload Watcher is designed specifically for media file uploads, which means that developers will need to use additional tools or approaches for other types of assets to upload.

Using Express Migration tool

The Express Migration tool is a Sitecore tool that allows you to migrate data between Sitecore instances. Here are the basic steps to perform a migration using the Express Migration tool:

Install the Express Migration tool: To use the Express Migration tool, you will first need to install it on your Sitecore instance. This can be done by downloading the Express Migration package from the Sitecore website and installing it on your Sitecore instance using the Sitecore Installation Wizard.
Choose Source and Target Versions: Once the Express Migration tool is installed, you will need to choose source and Target Sitecore versions. You can also select files, security roles and config files as a migration asset.

Configure the Express Migration tool: You will need to configure the tool by specifying the connection details for the source and destination Sitecore instances, such as the website folder, core and master database connection strings.

Select the items to migrate: Using the Express Migration tool, you can select the items that you want to migrate. You can select items using various criteria, such as by path, template, or date range.
Configure the migration options: Before migrating the items, you can configure various options such as handling of duplicate items, handling of links, handling of versions, handling of languages and media.
Perform the migration: Once you have configured the migration options, you can use it to perform the migration. The tool will copy the selected items from the source instance to the destination instance.
Verify the migration: After the migration, you can use it to verify that the items were migrated correctly. You can compare the items in the source and destination instances to ensure that they are the same.

Pros

Sitecore developed tool.
Its super-fast.
Apart from Sitecore items, it can also migrate files, security roles and config files as a migration assets.

Cons

Using this, migration can only be performed on-premise and is not supported for Sitecore versions hosted in PaaS or the cloud.
It supports only till 9.0 initial version.

Data migration using Razl

Razl (Rapid Automated Sitecore Link) is a third-party tool that can be used to perform data migration in Sitecore. Here are the basic steps to perform data migration using Razl:

Install Razl: To use Razl, you will first need to install it on your Sitecore instance. This can be done by downloading the Razl package from the Razl website and installing it on your Sitecore instance using the Sitecore Installation Wizard.
Connect to the source and destination Sitecore instances: Once Razl is installed, you can use it to connect to both the source and destination Sitecore instances. You will need to enter the connection details for both instances, such as the URLs, usernames, and passwords.
Select the items to migrate: Once connected, you can use Razl to select the items that you want to migrate. You can select items using various criteria, such as by path, template, or date range.
Configure the migration: Before migrating the items, you can configure various options such as handling of duplicate items, handling of links, handling of versions and handling of languages.
Perform the migration: Once you have configured the migration, you can use Razl to perform the migration. Razl will copy the selected items from the source instance to the destination instance.

Verify the migration: After the migration, you can use Razl to verify that the items were migrated correctly. You can compare the items in the source and destination instances to ensure that they are the same.

Pros:

Time-saving: Razl automates the data migration process, which saves time compared to manually migrating data between Sitecore instances.
Accuracy: Razl ensures that data is migrated accurately and without errors, which helps to maintain data integrity and avoid issues that can occur during manual data migration.
Ease of use: Razl provides a user-friendly interface that simplifies the data migration process, making it accessible to developers with different levels of expertise.
Flexible migration options: Razl provides various options for migrating data, including copying, merging, and deleting data, enabling developers to choose the migration strategy that best suits their needs.
Automation: Razl allows developers to automate the data migration process by creating scripts, which can save time and ensure consistency in the migration process.

Cons:

Cost: Razl is a licensed tool that requires a paid subscription, which may not be affordable for all organizations.
Dependency on the tool: Developers who use Razl may become dependent on the tool for data migration, which can be problematic if the tool becomes unavailable or is discontinued.
Technical expertise required: Razl requires a certain level of technical expertise to use effectively, which may be a challenge for developers who are new to Sitecore or lack experience with data migration.
Potential for data loss: Razl can delete or overwrite data during the migration process, which can lead to data loss if not used carefully.
Complexity: Razl can be a complex tool to use, which may require significant effort to set up and configure, especially when migrating large amounts of data.

Razl is a powerful tool for data migration in Sitecore, it provides a user-friendly interface, and it can automate many of the tasks involved in migrating data. However, it's important to note that data migration can be a complex process that can take a lot of time and resources. Before performing any migration, it is essential to make a backup of the source and destination instances, and to test the migration in a development environment before migrating to production.

Sitecore PowerShell

Data migration using Sitecore PowerShell is a process that allows you to migrate data from external sources to Sitecore instance using the Sitecore PowerShell module.

Here is the basic script to import data from csv file to Sitecore using Sitecore PowerShell:

# Load the CSV file

$csv = Import-Csv -Path "path/to/your.csv"

# Loop through each row in the CSV file

foreach ($row in $csv) {

# Create a new item using the values from the CSV file

$item = New-Item -Path "path/to/your/Sitecore/item" -ItemType "Template Name"

$item.Editing.BeginEdit()

$item["Field Name 1"] = $row."Column 1"

$item["Field Name 2"] = $row."Column 2"

# Add additional fields as needed

$item.Editing.EndEdit()

}

Note: You can use more advanced commands and scripts to migrate data more efficiently. Also, it is important to test the migration process in a development environment before migrating to production environment.

Pros

Out of the box feature
Better than writing C# code as entire Sitecore can be access via Powershell
Sitecore itself using PowerShell for lots of background functionalities.

Cons

Learning curve
Security concerns for remote script execution
You have to upgrade the PowerShell module in case of Sitecore upgrade.

Using Sitecore Sidekick

Sitecore Sidekick includes a Content Migrator tool that can be used to migrate content items from one Sitecore instance to another.

Here are the general steps to use Sitecore Sidekick to migrate content items:

Install and configure Sitecore Sidekick on both the source and target Sitecore instances.
Open the Content Migrator tool from the Sitecore Sidekick menu in the Sitecore content editor.

Choose the source and target databases from the dropdown menus.

Select the items you want to migrate by using the search and filtering tools in the Content Migrator tool.
Review the items to be migrated and make any necessary changes or updates.
Choose the migration options, such as whether to include child items or media files.
Start the migration process and wait for it to complete. The progress of the migration can be monitored in the Content Migrator tool.
Once the migration is complete, review the migrated items in the target Sitecore instance to ensure they have been migrated correctly.

Content Migrator is also useful as a diff tool between Sitecore servers even if not pulling content. It has UI elements that indicate not only whether an item has changes, but also where an item's children have changes.

Pros:

Time-saving: The Content Migrator tool can be used to quickly migrate large amounts of content from one Sitecore instance to another. This can save significant amounts of time compared to manually recreating the content in the target instance.
Flexible: The Content Migrator tool offers a range of options to customize the migration process, such as filtering by template, including or excluding child items, and mapping fields from the source to target instance. This flexibility can help ensure that the migrated content is consistent with the target Sitecore instance's requirements.
User-friendly: The Content Migrator tool is easy to use and comes with an intuitive interface that enables users to preview, edit, and validate migrated content items before the migration process begins.

Cons:

Complexity: The Content Migrator tool requires an understanding of the Sitecore data model and can be complex to use for users who are not familiar with Sitecore. Additionally, because the tool is so powerful, it is important to exercise caution when using it to avoid accidental data loss or corruption.
Security concerns: The Content Migrator tool has the potential to modify or delete large numbers of items in the Sitecore content tree. This could pose a security risk if used carelessly or without proper permissions in place.
Compatibility issues: The Content Migrator tool may not be fully compatible with all Sitecore versions, which could cause errors or unexpected behaviour. It is important to check compatibility and test thoroughly before using the Content Migrator tool in a production environment.

It is important to note that Sitecore Sidekick's Content Migrator tool is a powerful tool that can modify or delete items in the Sitecore content tree. It is important to test the tool thoroughly and to have a backup of the content tree before using it to migrate items. Additionally, ensure that the source and target Sitecore instances are of the same version to avoid compatibility issues.

Using JSS

To migrate content from a JSS YML file to Sitecore, you can follow these general steps:

Install the Sitecore JSS package: Install the Sitecore JavaScript Services (JSS) package on your Sitecore instance. This package includes the necessary components to support JSS applications.
Create a new JSS app: Create a new JSS app in Sitecore that corresponds to the JSS YML file you want to migrate. This can be done using the Sitecore JSS CLI, which is a command-line interface that enables you to create and manage JSS apps.
Map the YML fields to Sitecore fields: Identify the fields in the JSS YML file that correspond to Sitecore fields. This can be done using the Sitecore JSS Mapper, which is a tool that enables you to map JSS fields to Sitecore fields.
Convert the YML file to Sitecore content: Convert the JSS YML file to Sitecore content using the Sitecore JSS Importer, which is a tool that enables you to import JSS content into Sitecore such as

deploy jss items -c -d

deploy jss app -c -d

Review and publish the imported content: Review the imported content in Sitecore and make any necessary updates. Once you are satisfied with the content, publish it to make it available to your website visitors.

Pros:

Easier deployment: Migrating content from a JSS YML file to Sitecore enables you to deploy content changes without needing to modify the underlying code or configuration of your JSS app.

Cons:

Increased complexity: Migrating content from a JSS YML file to Sitecore may introduce additional complexity to your architecture, as you may need to integrate your JSS app with Sitecore and manage content in two separate systems.
Learning curve: Migrating content from a JSS YML file to Sitecore may require learning new tools, processes, and workflows, which can be a challenge for development teams that are new to Sitecore.
Potential for data loss: Migrating content from a JSS YML file to Sitecore requires careful planning and execution to ensure that data is not lost or corrupted during the migration process.

Please note that the specifics of this process may vary depending on the version of Sitecore and the JSS framework you are using, so it is important to refer to the relevant documentation and resources for your specific setup.

Manual Content Operation

To enter content into a Sitecore item manually, follow these steps:

Open the Sitecore content editor by logging into the Sitecore CMS and selecting the "Content Editor" option from the launchpad or the Sitecore menu.
Navigate to the item you want to add content to. You can use the search feature or browse the content tree to find the item.
Select the item by clicking on it in the content tree.
In the right-hand pane, click on the "Fields" tab. This will display a list of all the fields associated with the item.
Select the field you want to add content to and enter your content in the field.
Repeat steps 4 and 5 for any additional fields you want to add content to.
Once you have entered all the necessary content, click on the "Save" button at the top of the right-hand pane to save the changes.
To preview the item, click on the "Preview" button in the Sitecore ribbon at the top of the screen. This will open a new tab with the preview of the item.
If you are satisfied with the content, you can publish the item by clicking on the "Publish" button in the Sitecore ribbon. This will make the item visible to users on the website.

It's important to note that the fields displayed in the right-hand pane will vary depending on the template used to create the item. Some templates may have more fields than others, and the names and types of the fields may also vary. Additionally, some fields may have specific validation rules or formatting requirements, so it's important to follow any guidelines or best practices provided by your organization or Sitecore documentation when entering content.

Pros:

Complete control: Entering content manually gives you complete control over the content that is entered into Sitecore. You can ensure that the content is entered in the correct format and style that is consistent with the rest of the website.
Accuracy: By entering the content yourself, you can ensure that all the necessary information is entered correctly, reducing the risk of errors that could occur if the content was entered automatically.
Flexibility: It allows you to add content to a specific item and control exactly how it appears on the website. This can be useful when you need to make quick changes or updates to a specific piece of content.
Familiarity: Manual entry is a familiar process for most users and requires little to no training, making it easy for users to enter content into Sitecore.

Cons:

Time-consuming: Entering content manually can be time-consuming, especially if you have to enter a large amount of content. This can be a disadvantage if you need to add a lot of content to Sitecore on a regular basis.
Error-prone: Manual entry can be prone to errors if the user is not careful or does not have enough knowledge about the content structure, format, or style of the website.
Limited automation: Manual entry does not allow for the automation of the content entry process, which can be a disadvantage if you have a large amount of content to enter or if you need to update content frequently.
Formatting challenges: Some content fields in Sitecore may have specific formatting requirements, such as character limits or specific input formats. If these requirements are not met, the content may not be displayed correctly on the website.

Overall, manual entry is a useful option for entering content into Sitecore, particularly for smaller amounts of content or for quick updates. However, it may not be the most efficient option for larger volumes of content, and it does require careful attention to ensure accuracy and consistency in the content.

Sitecore OData service

Exporting data using Sitecore OData service is a process that allows you to export data from Sitecore items in the form of an OData feed which is in JSON format.

Here are the basic steps to export data using Sitecore OData service:

Log in to Sitecore as an administrator.
Navigate to the item or items that you want to export in the Sitecore Content Editor.
The service authenticates requests using API keys.
Open the OData service endpoint in your browser by going to the URL: https://your-site-url/sitecore/api/ssc/aggregate/content/Items
You can see the list of all the items available in the OData service, you can filter the item by using query options available in OData service, like $filter, $select, $orderby etc.
OData services return data in the form of an JSON, which can be easily consumed by various applications and systems.

For example, if you hit URL https://your-sitecore-instance-name/sitecore/api/ssc/aggregate/content/Items('%7B110D559F-DEA5-42EA-9C1C-8A5DF7E70EF9%7D')?sc_apikey=your-api-key&$expand=FieldValues , it should show you Sitecore home item details in JSON format as

Pros:

Data accessibility
Simplified data querying
Reduced development time
Improved integration capabilities

Cons:

Limited functionality:
Security concerns
Performance
Only support in latest Sitecore versions

Sitecore OData service is available only in Sitecore 8.2 and above versions, also it needs to be enabled by configuring the OData services in Sitecore. Also, the OData feed only contains the fields that are selected in the OData service endpoint, so you should select the fields that you need for the export.

Migrate data using C#

Migrating data in Sitecore can be accomplished using C# code. Here is a high-level overview of the steps involved:

Retrieve the source data: Depending on where your data is coming from, you will need to retrieve it from the appropriate source. This could be a SQL database, an Excel file, a CSV file, or some other data source.
Create a connection to the Sitecore database: Use the Sitecore API to connect to the Sitecore database where you want to store the migrated data. This can be accomplished by creating a new instance of the Sitecore Data.Database class.
Create the new items in Sitecore: For each item that you want to migrate, create a new Sitecore item using the Sitecore API. You can set the fields and other properties of the item using the Sitecore.Data.Items.Item class.
Map the data from the source to the Sitecore items: Once you have the new items created in Sitecore, map the data from the source to the appropriate fields in the Sitecore items. You can do this by iterating over the source data and using the Sitecore API to set the values of the appropriate fields on the Sitecore item.
Save the changes: Once you have updated all of the items, use the Sitecore API to save the changes to the Sitecore database.

Here is some sample C# code that demonstrates how to migrate data from a CSV file into Sitecore:

// Step 1: Retrieve the source data from a CSV file

var csvData = File.ReadAllLines("data.csv");

// Step 2: Connect to the Sitecore database

var db = Sitecore.Configuration.Factory.GetDatabase("master");

// Step 3: Create the new items in Sitecore

foreach (var row in csvData)

{

var columns = row.Split(',');

var newItem = db.CreateItem(columns[0], db.GetItem("/sitecore/content"), Sitecore.TemplateIDs.StandardTemplate);

// Step 4: Map the data from the source to the Sitecore items

newItem.Editing.BeginEdit();

newItem["Title"] = columns[1];

newItem["Description"] = columns[2];

newItem.Editing.EndEdit();

}

// Step 5: Save the changes

db.Commit();

Pros:

Full control: Using C# code to migrate data gives you complete control over the process. You can write custom code to handle complex data transformations or business logic, and you have full access to the Sitecore API to create, update, and delete items as needed.
Scalability: Depending on the size and complexity of your data, migrating data in Sitecore using C# may be more scalable than using the Sitecore content editor. With custom code, you can handle large data sets more efficiently and in a more automated way.
Flexibility: With custom code, you can tailor the migration process to your specific needs. For example, you can map fields in a custom way, skip certain items or data, or transform data in real-time as needed.

Cons:

Development time: Migrating data in Sitecore using C# requires development time and resources, which can add to the overall project cost. It may also require more expertise in C# programming and the Sitecore API.
Maintenance: Custom code can be more difficult to maintain and update over time, especially if the code becomes more complex or relies on specific dependencies or libraries.
Error handling: With custom code, you are responsible for handling errors and exceptions that may arise during the migration process. This can require additional testing and debugging efforts to ensure that the data is migrated correctly and without any data loss or corruption.

Overall, using C# code to migrate data in Sitecore can be a powerful and flexible approach, but it requires careful consideration of the pros and cons, as well as your specific business requirements and technical capabilities.

Sitecore Serialization

Sitecore Serialization is a feature that allows you to export and import Sitecore items in a serialized format, which can be used to transfer items between different environments or to version control Sitecore content.

To export and import content tree items using Sitecore Serialization, you can follow these steps:

Exporting Items:

Open the Content Editor in Sitecore and navigate to the item you want to export.
Right-click on the item and select "Serialize Item" or "Serialize Tree" from the context menu. This will generate a serialized file for the item and its children in the folder specified in the serialization configuration file.
Repeat this process for each item you want to export.

Importing Items:

Copy the serialized file for the item you want to import to the serialization folder in the target environment.
Open the Content Editor in the target environment and navigate to the parent item where you want to import the item.
Right-click on the parent item and select "Update Item" or "Update Tree" from the context menu. This will reload the serialized files for the item and its children.

The imported item should now be visible in the Content Editor.

Pros:

Easy to use: Sitecore Serialization is a built-in feature that is easy to use and requires minimal setup. It allows developers and content authors to quickly export and import content items without any additional tools or software.
Version control: Serialized items can be version controlled, which means that you can keep track of changes made to the content tree over time and roll back to a previous version if necessary.
Portability: Serialized items can be easily moved between different environments, such as from a development environment to a production environment. This makes it easier to manage content items across different environments.
Automation: Serialized items can be exported and imported programmatically using PowerShell or other scripting languages, which allows you to automate the process and save time.

Cons:

Performance: Exporting and importing large content trees can be time-consuming and may impact the performance of the Sitecore instance. It is recommended to use Sitecore Serialization on smaller content trees or to use serialization tools that offer delta synchronization.
Manual process: The export and import process using Sitecore Serialization is a manual process that requires a person to initiate the export and import. This may not be feasible for larger content trees or in cases where frequent updates are made to the content tree.
Serialization issues: Serialization can sometimes fail or generate invalid serialized files, which can lead to data loss or corruption. It is recommended to test the serialization process thoroughly and to keep a backup of the content tree in case of issues.
Complex items: Sitecore Serialization may not always handle complex items or items with custom fields or functionality as expected. It is recommended to thoroughly test the serialization process on these types of items before using it in a production environment.

You may also use serialization tools like TDS, Unicorn, or Sitecore Content Serialization, which will make the export and import process more user-friendly and provide additional features like automated deployment, delta synchronization, and more.

Update Center

The Sitecore Update Center provides a new, effective and efficient method of managing Sitecore upgrades.

The Sitecore Update Center is utilized to locate, download, install, and manage updates and hotfixes for the Sitecore platform and its modules. It connects to a package management service for update information and the actual update packages. Sitecore offers a package management service, or you can opt to install and host your own. The Update Center is capable of installing updates from a package stored in the file system.

When logging into a Sitecore 9 Update 2 instance, a new application called the Sitecore Update Center can be seen on the LaunchPad.

If you click the application, the Update Center opens as below

In the left pane, you have three options:

Updates – click to see a list of available updates from the package management service. By default, Updates is selected.
Installed modules – click to see a list of already installed modules.
Install custom update – click to select an update package in the file system.

The final element of the Update Center is the Enter update mode/Exit update mode button that toggles the update mode on and off.

When you install an update, you use the Ready to install window to set options and start the process:

To search for Sitecore updates, Update Center internally uses a package management service which refers a new connection string, named PackageManagementServiceUrl, in the ConnectionStrings.Config.

Pros

Out of the box feature
Its like windows upgrade where separate instance not required.
You can also upgrade installed modules.

Cons

Its valid for Sitecore 9.x to Sitecore 10.1.

Upgrade the Sitecore database

Upgrading a Sitecore database can be a complex process, and it will depend on the specific version of Sitecore that you are currently running and the version to which you are upgrading. Generally, the process can be broken down into the following steps:

Prepare: Before starting the upgrade, make sure that you have a backup of your current Sitecore database. It's also important to review the release notes of the version you want to upgrade to, and understand any breaking changes, prerequisites, and compatibility issues.
Install: Install the new version of Sitecore on your web server. Make sure that you have the correct licenses for the new version.
Upgrade the databases: Once the new version is installed, you will need to upgrade the databases. This will typically involve running SQL scripts that update the schema and data in the databases.
Update the config files: Next, you will need to update the Sitecore config files with any new settings or changes required by the new version.
Test: After the config files are updated, you should test the upgraded Sitecore instance to ensure that everything is working as expected.
Deploy: Once you have tested the upgraded Sitecore instance and are satisfied that it is working correctly, you can deploy the new version to your production environment.

Pros:

Improved functionality: Upgrading the Sitecore database can improve the functionality and performance of your website, which can lead to a better user experience for visitors.
Access to new features: Upgrading the database may provide access to new features or functionality that were not available in previous versions of Sitecore.
Security: Upgrading the database can help to ensure that your website remains secure, by addressing any known security vulnerabilities in previous versions of Sitecore.
Support: Upgrading the database can ensure that your website remains compatible with the latest versions of Sitecore and that you can continue to receive support from Sitecore and its partners.

Cons:

Cost: Upgrading the Sitecore database can be costly, particularly if there are significant changes to the database schema or if additional hardware is required.
Complexity: Upgrading the Sitecore database can be a complex process, particularly if there are significant changes to the database schema or if there are customizations or integrations that need to be taken into consideration.
Downtime: Upgrading the Sitecore database may require some downtime, which can impact your website's availability and performance during the upgrade process.
Compatibility issues: Upgrading the Sitecore database may result in compatibility issues with customizations or third-party integrations that were developed for previous versions of Sitecore.

It's important to note that this process can be complex and time-consuming, so it's recommended that you work with a Sitecore partner or experienced developer to ensure a smooth upgrade process.

Sitecore Data Exchange Framework

The Sitecore Data Exchange Framework (DEF) is a tool that allows for data migration between Sitecore and external systems. It provides a set of services and APIs that allows developers to create connectors that can import and export data between Sitecore and external systems, such as CRM or ERP systems.

To migrate data using DEF, you would typically follow these steps:

Install DEF: To use DEF, you will first need to install it on your Sitecore instance. This can typically be done through the Sitecore Marketplace.
Create connectors: Next, you will need to create connectors that will import and export data between Sitecore and the external system. A connector is a set of components that define how data is exchanged between Sitecore and an external system.
Create endpoints: You will also need to create endpoints, which define the external system that the data is being exchanged with.
Create pipeline: You will also need to create a pipeline, which is a sequence of steps that are executed to import or export data. This pipeline can be customized to include any additional steps that are needed to process the data.
Create the mapping: Create mapping, which defines how data is mapped between Sitecore and the external system. This can include field-by-field mapping, as well as any custom logic that is needed to handle specific data types or transformations.
Run the pipeline: Once everything is configured, you can execute the pipeline to import or export data.

Pros:

Flexibility: Sitecore DEF provides a flexible and extensible framework for integrating data between Sitecore and other systems, which can be tailored to meet specific business requirements.
Integration: Sitecore DEF enables integration with a wide range of systems, including popular CRM and ERP systems, which can help to provide a seamless user experience for website visitors.
Time-saving: Sitecore DEF provides pre-built connectors for popular systems, which can save development time and effort. In addition, Sitecore DEF's mapping capabilities can simplify the process of mapping data between systems.
Scalability: Sitecore DEF is designed to handle large volumes of data, which can be useful for organizations with high traffic websites.

Cons:

Complexity: Sitecore DEF can be complex to set up and configure, particularly for organizations with limited technical resources.
Learning Curve: Sitecore DEF requires a certain level of technical expertise to use, which can lead to a steep learning curve for developers who are new to the tool.
Maintenance: It requires ongoing maintenance and updates to ensure that it continues to work effectively as systems evolve over time.

Overall, Sitecore DEF can be a powerful tool for organizations looking to integrate data between Sitecore and other systems, but it requires a certain level of technical expertise to use effectively. It's important to note that the process of migrating data using DEF can be complex and time-consuming, so it's recommended that you work with a Sitecore partner or experienced developer to ensure a smooth migration process.

References

Whitepaper : Sitecore Pipeline

2023-10-26T11:38:00.003+05:30

Pipeline in general

In programming, a pipeline is a concept used to describe a sequence of data processing elements or functions that are connected in a chain, where the output of one element serves as the input for the next element. This technique is commonly used to organize and streamline the flow of data or operations in various computational processes.

Pipeline Flow

In a pipeline, data flows through different stages or processing units, with each stage performing a specific operation on the data. Each stage typically focuses on a particular task, and the combination of all stages allows for complex data processing or transformations to be achieved efficiently.

The pipeline pattern is widely used in various areas of software development, such as data processing, data analysis, and even web application development.

Examples of Pipelines

Data Processing Pipeline: In data processing, a pipeline might involve several stages for transforming and analyzing data. For example, in a data analysis pipeline, data could flow through stages like data ingestion, cleaning, feature extraction, machine learning model training, and finally, result evaluation.

Image Processing Pipeline: In image processing, a pipeline could be used to process images through various stages, such as image resizing, noise reduction, color correction, edge detection, and image enhancement.

Web Development Pipeline: In web development, a pipeline can be used for tasks like asset compilation and optimization. For instance, a pipeline could involve concatenating and minifying CSS and JavaScript files, optimizing images, and caching assets for faster loading times.

Continuous Integration/Continuous Deployment (CI/CD) Pipeline: In software development, a CI/CD pipeline automates the process of building, testing, and deploying code changes. This pipeline might include stages like code compilation, unit testing, integration testing, and finally, deployment to production servers.

Natural Language Processing (NLP) Pipeline: In NLP, a pipeline could be employed to process text data through various stages, such as tokenization, part-of-speech tagging, named entity recognition, sentiment analysis, and text summarization.

Audio Processing Pipeline: In audio processing, a pipeline might involve stages for audio file decoding, noise reduction, audio feature extraction, speech-to-text conversion, and text-to-speech synthesis.

Video Editing Pipeline: In video editing, a pipeline could include stages like video clipping, adding special effects, transitions, audio synchronization, and video rendering.

These examples demonstrate how pipelines can be used to break down complex tasks into manageable steps, where each step in the pipeline performs a specific operation, and the output of one step serves as the input for the next step. This modular approach to programming allows for easier development, testing, and maintenance of software systems.

Introduction of Sitecore Pipeline

Sitecore Pipeline is a fundamental concept of the Sitecore CMS architecture. It's a way of defining a sequence of steps that execute in a particular order to handle specific events or processes within the Sitecore request processing lifecycle. This approach allows for highly extensible and modular development of Sitecore solutions.

In this article, I will provide an in-depth look at Sitecore Pipeline with practical examples of how to leverage this architecture to extend and customize Sitecore functionality.

Understanding Sitecore Pipeline

Before diving into Sitecore Pipeline, it's essential to understand the Sitecore request processing lifecycle. Sitecore request processing lifecycle has various stages, and each stage is a specific event that occurs within Sitecore.

When an HTTP request arrives at a Sitecore website, the request is processed through various stages before rendering a response. Each stage consists of one or more pipelines, and each pipeline consists of one or more processors.

A processor is a C# method that executes a specific operation or handles a particular event within the request processing lifecycle. The processor can modify the request, perform additional operations or even prevent the request from proceeding to the next stage of the lifecycle.

Sitecore Pipeline Architecture

Sitecore Pipeline architecture is based on the idea of a sequence of processors that execute in a specific order. The sequence of processors is grouped into a pipeline. Each pipeline executes at a specific stage in the Sitecore request processing lifecycle.

Pipeline and Processors

Few types of pipelines in Sitecore are:

InitializePipeline - Executes when an Sitecore instance start.

HttpPipeline - Executes when an HTTP request is made to the Sitecore website.

PublishPipeline - Executes when the Sitecore items are being publish.

Each pipeline consists of a sequence of processors that execute in a specific order. These processors can be Sitecore-built-in processors, custom processors, or a combination of both.

Creating Custom Processors

Creating custom processors is a straightforward process. You create a C# method that performs the operation you want and then add it to the pipeline.

The first step is to define the pipeline where the processor will execute. You can add a processor to an existing pipeline or create a new pipeline.

Once you have identified the pipeline, you will define the processor. In this step, you will create a C# method that performs the operation you want.

After defining the processor, you will register it with the pipeline. You can register the processor at the beginning or the end of the pipeline or somewhere in between.

Best Practices for Sitecore Pipeline

Here are some best practices to keep in mind when working with Sitecore pipelines:

Plan Your Pipeline Carefully: Plan your pipeline carefully to ensure that processors execute in the correct order and that they do not conflict with each other.

Keep Your Pipeline Simple: Keep your pipeline simple by breaking it down into small, reusable processors.

Use Sitecore-Built-in Processors: Whenever possible.

Pipeline Examples

Now that we have a good understanding of how pipelines work, let's take a look at some examples of how we can use pipelines to perform specific tasks.

1. Http Request Processor for Page not found

This example shows that how to create custom Page not found for Sitecore website.

using Sitecore.Data.Items;

using Sitecore.Pipelines.HttpRequest;

namespace AlexaSearch.Pipelines

{

public class HttpRequestProcessor404 : HttpRequestProcessor

{

public override void Process(HttpRequestArgs args)

{

if (Sitecore.Context.Item != null || Sitecore.Context.Site == null || Sitecore.Context.Database == null

|| Sitecore.Context.Database.Name == "core"

|| args.RequestUrl.AbsoluteUri.ToLower().Contains("/sitecore/api/layout/render/jss")

|| args.RequestUrl.AbsoluteUri.ToLower().Contains("/sitecore/api/jss/import")

|| args.RequestUrl.AbsoluteUri.ToLower().Contains("/api/sitecore/"))

{

return;

}

var alexa404PageId = Sitecore.Configuration.Settings.GetSetting("Alexa404");

var pageNotFound = Sitecore.Context.Database.GetItem(alexa404PageId);

if (pageNotFound == null)

return;

args.ProcessorItem = pageNotFound;

Sitecore.Context.Item = pageNotFound;

args.HttpContext.Response.StatusCode = 404;

}

Web.config entry

<processor type="AlexaSearch.Pipelines.HttpRequestProcessor404,AlexaSearch"

patch:after="processor[@type='Sitecore.Pipelines.HttpRequest.ItemResolver, Sitecore.Kernel']"/>

</httpRequestBegin>

2. Item Processed Processor for Publish Items

This example shows that how to create processor to get publish items and logging their activities.

using Sitecore.Data.Items;

using Sitecore.Diagnostics;

using Sitecore.Publishing.Pipelines.Publish;

using System;

using System.Collections.Concurrent;

using System.Collections.Generic;

using System.Linq;

using System.Web.UI;

namespace AlexaSearch.Pipelines

{

public class ItemProcessedProcessor : PublishProcessor

{

public override void Process(PublishContext context)

{

if (!context.Aborted)

{

var publishItems = context.ProcessedPublishingCandidates.Keys;

foreach(var tempItem in publishItems)

{

var currentItem = context.PublishOptions.TargetDatabase.GetItem(tempItem.ItemId);

if(currentItem != null)

Sitecore.Diagnostics.Log.Info("My Publish item is " + currentItem.Name, this);

}

Web.config entry

</publish>

3. Log Request Begin processor

This example shows that how to log HttpRequestBegin pipeline activities.

using Sitecore.Pipelines.HttpRequest;

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

namespace AlexaSearch.Pipelines

{

public class LogRequestBegin

{

public void Process(HttpRequestArgs args)

{

Sitecore.Diagnostics.Log.Error(DateTime.Now + " Hello HttpRequestBegin pipeline executed ", this);

}

Web.config entry

</httpRequestBegin>

4. Custom Field Processor

This example shows that how to capture each fields in processor. It will check for rich text field and append extra text at the end of rich text field content.

using Sitecore.Pipelines.RenderField;

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

namespace AlexaSearch.Pipelines

{

public class MyCustomFieldProcessor

{

public void Process(RenderFieldArgs args)

{

if (!(args.FieldTypeKey == "rich text"))

return;

args.After = "<div><h3>Copyright Alexa</h3></div>";

}

Web.config entry

<processor patch:after="processor[@type='Sitecore.Pipelines.RenderField.GetTextFieldValue, Sitecore.Kernel']"

type="AlexaSearch.Pipelines.MyCustomFieldProcessor, AlexaSearch" />

</renderField>

5. Set Default Alternate Text in media item

This example shows that how to Set Default Alternate Text in media item.

using Sitecore.Diagnostics;

using Sitecore.Pipelines.GetMediaCreatorOptions;

namespace AlexaSearch.Pipelines

{

public class SetDefaultAlternateTextIfNeed

{

public void Process(GetMediaCreatorOptionsArgs args)

{

Assert.ArgumentNotNull(args, "args");

if (!string.IsNullOrWhiteSpace(args.Options.AlternateText))

{

return;

}

args.Options.AlternateText = GetAlternateText(args);

}

protected virtual string GetAlternateText(GetMediaCreatorOptionsArgs args)

{

Assert.ArgumentNotNull(args, "args");

if (string.IsNullOrWhiteSpace(args.Options.Destination) || args.Options.Destination.IndexOf("/") < 0)

{

return string.Empty;

}

int startofNameIndex = args.Options.Destination.LastIndexOf("/") + 1;

return args.Options.Destination.Substring(startofNameIndex);

}

Web.config entry

</getMediaCreatorOptions>

What is CorePipeline.Run()

CorePipeline.Run() is used in Sitecore when you want to execute a pipeline programmatically. Pipelines in Sitecore are used to execute a series of processors in a specific order. They are defined in configuration files and are typically triggered by specific events or user actions.

Here are some situations where you might want to use CorePipeline.Run():

Implementing custom business logic: If you have custom business logic that needs to be executed as part of a Sitecore pipeline, you can create a new pipeline and use CorePipeline.Run() to execute it.

Modifying the behavior of existing Sitecore pipelines: If you need to modify the behavior of an existing Sitecore pipeline, you can add your own processor to the pipeline and use CorePipeline.Run() to execute it.

Triggering pipelines programmatically: If you need to trigger a pipeline programmatically, for example in response to a user action, you can use CorePipeline.Run() to do so.

Integrating with third-party systems: If you need to integrate Sitecore with a third-party system that requires custom processing, you can create a new pipeline and use CorePipeline.Run() to execute it.

Example

using Sitecore.Pipelines;

using System;

namespace AlexaSearch.Pipelines

{

public class MyCustomPipelineArgs : PipelineArgs

{

public string CustomValue { get; set; }

}

public class MyCustomPipelineProcessor

{

public void Process(MyCustomPipelineArgs args)

{

Sitecore.Diagnostics.Log.Error(DateTime.Now + " My Custom Pipeline Processor " + args.CustomValue, this);

}

Call this pipeline from some Views as

var args = new AlexaSearch.Pipelines.MyCustomPipelineArgs { CustomValue = "Hello, World!" };

Sitecore.Pipelines.CorePipeline.Run("myCustomPipeline", args);

}

<div>

This is my Footer Component<br>

</div>

Web.config entry

</myCustomPipeline>

Monitor Sitecore pipelines

There are a few ways to monitor Sitecore pipelines:

Log files: Sitecore writes detailed log files that can be used to monitor pipelines. By default, Sitecore logs are located in the App_Data/Logs folder. You can configure the logging level in the Sitecore configuration file to get more detailed information.

Debug mode: You can also monitor pipelines in debug mode by setting breakpoints in your custom pipeline processors and stepping through the code. This can be useful for troubleshooting issues or testing new pipeline functionality.

Pipeline Profiler: It is a Sitecore tool that helps developers to monitor the performance of pipelines in real-time

Pipeline Profiler

Pipeline Profiler is a Sitecore tool that helps developers to monitor the performance of pipelines in real-time. It is a visual representation of the Sitecore pipeline events that occur during an interaction with a website, such as page rendering or a form submission.

The Pipeline Profiler can be accessed it from /sitecore/admin/pipelines.aspx. It displays the execution time for each pipeline and the time taken by each processor within that pipeline. This information can be used to identify performance bottlenecks in the pipeline and to optimize pipeline execution.

Advantages of Sitecore Pipeline:

Flexibility: Sitecore pipelines provide a flexible way to add, remove, or modify functionality at different stages of a process. This allows for customizations without impacting the existing codebase.

Reusability: Since pipelines are modular, they can be reused in different contexts, making development faster and more efficient.

Maintainability: Separating code into smaller, more manageable pieces makes it easier to maintain and debug.

Extensibility: Pipelines can be extended with new processors to meet changing business requirements.

Disadvantages of Sitecore Pipeline:

Overhead: Pipelines can add some overhead to processing times, especially if there are many processors involved.

Complexity: Understanding the Sitecore pipeline model and how to work with it can be complex and requires some experience.

Performance: While pipelines can be used to optimize performance, if not implemented carefully, they can have a negative impact on performance.

Debugging: Debugging pipeline issues can be challenging because of the number of processors involved and the complex interactions between them.

When not to use Sitecore pipelines?

While Sitecore pipelines offer a lot of benefits, there are some situations where they might not be the best fit. Here are some cases where using pipelines may not be ideal:

Simple, straightforward tasks: If a task is simple and straightforward, it may not require the use of a pipeline. For example, if you only need to update a single item, you could do that directly without creating a pipeline.

Performance-critical tasks: While Sitecore pipelines are very flexible and powerful, they do have some overhead associated with them. If you have a task that needs to be performed as quickly as possible, using a pipeline may add too much overhead and slow things down.

Tight coupling between components: If components within your application are tightly coupled, it may not make sense to use a pipeline. Pipelines are designed to loosely couple components, so if there is already a tight coupling between the components, adding a pipeline may just add unnecessary complexity.

Inflexible requirements: If the requirements for a task are very rigid and not likely to change, it may not make sense to use a pipeline. Pipelines are designed to be very flexible and adaptable, so if the requirements are unlikely to change, you may not need that level of flexibility.

Conclusion

In this article, we have explored the Sitecore pipeline framework and how it can be used to perform various tasks in Sitecore. I have covered the basics of how pipelines work, how to configure them in Sitecore, and some examples of how they can be used.

By understanding the Sitecore pipeline framework and how to use it effectively, developers can create more powerful and flexible solutions in Sitecore. With this knowledge, you will be able to leverage the pipeline.

Authentication failed because the remote party has closed the transport stream

2023-09-14T11:07:00.005+05:30

Sitecore Content Hub is a powerful tool for managing digital assets and content. When it comes to integrating Content Hub with your Sitecore instance, you may encounter some weird challenges. One of the issues that users may face is the "Authentication failed because the remote party has closed the transport stream" error. In this article, we will explore the causes of this error and how to resolve it.

The Scenario

Imagine you have a Sitecore instance running on Azure PaaS, and you've installed the Content Hub connector. Everything seems to be working smoothly – you can retrieve images and links from the Digital Asset Management (DAM) system and display them in Image and Rich Text fields. However, trouble arises when you attempt to use the "Insert DAM link" feature within the General Link field. Instead of successfully inserting a link, you encounter the perplexing "Authentication failed" error.

General link field error for Sitecore Content Hub

Initial Troubleshooting

Naturally, our first instinct is to check our credentials. We've logged into Content Hub in another browser tab, and there don't seem to be any issues with authentication for Image and Rich Text fields. The problem only arises when interacting with the General Link field as

Checking internal code

Digging deeper into the issue, we examine the code responsible for communicating with the Content Hub API. This line of code is executed exclusively when we use the "Insert DAM link" command within the General Link field which basically retrieves additional properties.

value = GetAdditionalPropertyValue(chKey, DAMHelper.GetEntity(long.Parse(result[Constants.SelectedAssetId])));

Suspecting TLS Issue

At this point, we might suspect a Transport Layer Security (TLS) issue, as TLS configuration can sometimes lead to connectivity problems. However, we verify that our development environment is configured to use TLS 1.2, eliminating TLS as the root cause.

Azure VNET to the Rescue

With conventional troubleshooting avenues exhausted, we turn our attention to our Azure Virtual Network (VNET) configuration. After reviewing our VNET traffic rules, we discover the key to resolving the issue. We open up the traffic for the Sitecore Content Hub URL at the Azure VNET level.

The Solution

To our relief, this Azure VNET setting proves to be the missing piece of the puzzle. Once we've made the necessary adjustments, the "Authentication failed" error becomes a thing of the past. The General Link field now functions seamlessly, and we can insert DAM links without encountering any connectivity problems.

Finally

Troubleshooting errors like "Authentication failed because the remote party has closed the transport stream" can be a complex process. It often requires a systematic approach to identify the root cause and find a solution. In this case, a careful examination of the code, consideration of TLS configurations, and ultimately, the adjustment of Azure VNET settings, resolved the issue.

By sharing this experience, we hope to assist others who may encounter similar challenges when using Sitecore Content Hub connectors. Remember that troubleshooting can be a learning opportunity, and persistence often leads to a successful resolution.

Troubleshooting Sitecore Content Hub Connector Authentication Issue with General Link Fields

2023-09-04T16:33:00.001+05:30

Sitecore Content Hub Connector is a powerful tool that enables seamless integration between Sitecore and Content Hub. This integration allows content authors to easily access and manage digital assets from Content Hub within Sitecore. However, like any integration, it can encounter occasional issues. In this blog post, we'll discuss a specific problem some users have faced: an authentication error when working with General Link fields in Sitecore.

The Scenario:

You've set up Sitecore 10.3 on Azure PaaS and successfully integrated it with Sitecore Content Hub using PowerShell installation script. Everything seems to be working fine like RichText and Image field able to get images from Content Hub successfully. But while using the "Insert DAM Link" option within a General Link field, you encounter an error message that says, "Unable to authorize with the specified credentials."

Authentication error

Troubleshooting the Issue:

Let's walk through the steps to diagnose and resolve it.

Review Connection String:

The actual Content Hub user password is "123456789$ASDfghjkl", but when I checked connection string, I notice that the password for the Content Hub user is truncated, like "123456789$". This "$" sign in the password can be the root cause of the problem.

Password Correction:

To resolve this issue, simply correct the password in your connectionstring.config. Change it to "123456789$ASDfghjkl " or whatever your actual password is without the "$" sign.

Root Cause:

PowerShell script have a problem with "$" sign. PowerShell script can truncate your password and update your ConnectionStrings.config file with wrong password. So need to update connectionstring.config file manually with correct and full password.

Testing:

After making this correction, test the "Insert DAM Link" functionality in the General Link field again. You should no longer encounter the authentication error.

Lessons Learned:

Never keep $ sign in password while installing and running Powershell scripts for installing Sitecore Content Hub Connector.

Connection to Your Rendering Host Failed with a Body Exceeded 2MB Limit

2023-08-31T11:58:00.000+05:30

In the ever-evolving landscape of digital experiences, Sitecore JSS (JavaScript Services) combined with Next.js has emerged as a powerful duo for building headless websites. This approach provides flexibility, scalability, and performance. However, as with any technology, challenges may arise.

In this blog post, we'll delve into one such challenge: the "Connection to Your Rendering Host Failed with a Body Exceeded 2MB Limit" error and how to tackle it effectively.

Understanding the Error

We have deployed our Next.js app on Azure Web App and we started to get the “Connection to your rendering host failed with a Body exceeded 2mb limit error. Ensure the POST endpoint at URL https://mynextjs-sitecore-test.azurewebapp.net/api/editing/render has been enabled” error. Its typically occurs when a request made to the Sitecore rendering host exceeds the predefined request size limit. This limit is set at 2MB by default to prevent excessively large requests from overwhelming the server and causing performance issues.

When building a Sitecore JSS-based headless website with Next.js, it's common to transfer data between the front end (Next.js) and the back end (Sitecore) using API calls. These API calls may involve sending large payloads, especially when dealing with extensive content or complex data structures.

Solutions

Once you've diagnosed the issue, it's time to implement a solution. We try to solve it in lots of

different way, but ultimately the solution that work for us is

• Open “\src\pages\api\editing\render.ts” file and change size from 2 MB to 50 MB as

export const config = {

api: {

bodyParser: {

sizeLimit: '50mb',

responseLimit: false,

};

• Open “\src\pages\api\editing\data\[key].ts” file and change size from 2 MB to 50 MB as

export const config = {

api: {

bodyParser: {

sizeLimit: '2mb',

responseLimit: false,

};

• Build and deploy your application, it should work now.

I hope this trick may solve your problem as well. Happy coding!

Recap of SUGCON India 2023

2023-08-26T13:19:00.011+05:30

The Stage

Recap of SUGCON India 2023: A Grand Celebration of Sitecore Excellence

Date: August 24-25, 2023

Venue: The Grand, New Delhi

Hotel The Grand

The Sitecore community in India witnessed an exhilarating two days at the SUGCON India 2023 conference, held at the prestigious venue The Grand in New Delhi, on August 24th and 25th. For those who couldn't make it to this grand event, here's a recap of the key highlights and takeaways.

A Phenomenal Start with 150 Registrations

Day 1 of SUGCON India 2023 got off to an electrifying start as the registration count soared to an impressive 150 participants. This enthusiastic response underscored the immense interest and anticipation that surrounded this year's conference. It's clear that Sitecore enthusiasts were eager to be a part of this remarkable event from the very beginning.

A Busy Morning of Registration, Training, and Certification

Day 1 of SUGCON India 2023 commenced at 8 AM with a flurry of activity as attendees, both participants and speakers, arrived at The Grand, New Delhi. Registration desks were buzzing with anticipation as 150 eager individuals geared up for two days of Sitecore excellence.

Registration and Differentiated Access

Notably, the conference organizers had made provisions for different coloured badges to distinguish participants from speakers. I proudly donned my speaker's badge, knowing that I would be contributing to the wealth of knowledge sharing at the event. I came at around 11 AM and done with my registration and received my badge.

Paid Training: "Introduction to XM Cloud Pages"

For those looking to kickstart their SUGCON experience with in-depth training, the day began with a paid training session, "Introduction to XM Cloud Pages" running from 8 AM to 10 AM.

Sitecore Certification Exam Opportunity

Simultaneously, an opportunity for Sitecore certification exams was available from 10 AM to 12 PM. (Its fees was I think $50 or $60). Although I had opted not to participate in the certification exam this time, it was a golden chance for attendees to validate their Sitecore expertise and add an esteemed certification to their portfolio.

Somebody was asking for second chance as he was unable to clear this exam this time 😉

First Session: "Digital Experience is a Team Sport!" by Pieter Brinkman

After a delightful lunch break, attendees reconvened to dive into the heart of SUGCON India 2023's technical sessions. My first session of the day was a true highlight: "Digital Experience is a Team Sport!" presented by none other than Pieter Brinkman (The Tallest Guy).

In this captivating presentation, Pieter Brinkman shed light on Sitecore's visionary perspective regarding the future of Digital Experience Platforms (DXPs). The central theme revolved around the concept of a composable DXP, one that adapts to the ever-evolving digital landscape. It was a testament to Sitecore's commitment to innovation and staying ahead of the curve.

What stood out most was Sitecore's recognition of the significance of embracing a team-oriented approach to crafting compelling digital experiences. Whether you're a business leader, a marketer, an IT professional, or a developer, Sitecore's vision is unwaveringly focused on meeting the unique needs of every team member.

It was well crafted presentation. One can easily find Pieter from the crowd of 150 people as he was the tallest guy in the town.

Second session "Implementing Sitecore Search" by Rob Earlam

In this session Rob Earlam (The next Santa) explained how they implemented Sitecore Search on Developer Portal. Rob gave an overview of the project and the different learnings on Federated Search, Search Widgets, Search Configuration, Eventing & Analytics, React SDK, Challenges Faced

He walkthrough the main features of Sitecore Search and discuss some of the challenges faced to help audience with any future implementation issues they might face.

He also explained the variety of different Index Sources that have been configured, including a walkthrough of the different configurations required to pull in a selection of diverse content locations.

Some people are debating that Rob will be a part of the next Sitecore Santa Series Season on Sitecore Youtube channel😉.

3rd session Pure lightweight Headless CMS - Sitecore Content Hub One with GenAI by Marvin Glenn Lacuna

Following the main session, the conference continued with three concurrent sessions held in different breakout rooms. These sessions were:

Introduction to Sitecore CDP
Pure Lightweight Headless CMS - Sitecore Content Hub One with GenAI
Elevate Your Sitecore Solution: Migrating from MVC to Headless for Unparalleled Agility

I chose to attend the session led by Marvin Glenn Lacuna, where he provided comprehensive insights into the features of Content Hub One.

Marvin explained that Content Hub One represents a cloud-native, Software as a Service (SaaS) solution—a lightweight Headless Content Management System (CMS). It leverages Content Hub technology while maintaining its unique user interface and APIs. This platform is tailored for tech-savvy teams seeking rapid omnichannel experience development.

In addition to detailing the platform's capabilities, Marvin shared the forthcoming six-month roadmap for Content Hub One's development and exciting upcoming features.

The highlight of Marvin's session was a live demonstration where he invited attendees to scan a QR code, granting him access to real-time analytics for the application. This demonstration application is publicly accessible on the Sitecore Github account.

What truly resonated with the Indian audience was Marvin's choice of examples—cricket legends Sachin Tendulkar and Virat Kohli. The fact that people in the regions like Singapore and the Philippines follow cricket was a delightful revelation.

I hope BCCI is hearing that as their next Cricket tournament place.

The day's agenda included a coffee break at 4 PM, providing an ideal opportunity for reconnecting with former colleagues and fellow Sitecorians. It was a time for networking and sharing experiences, enriching the overall conference experience.

4th Session “Weddings in the Cloud with Sitecore Connect!” by Sandeep Bhatia and Ankit Joshi

Once again, there were three simultaneous sessions held in separate breakout rooms, namely:

Weddings in the Cloud with Sitecore Connect!
Sitecore Discover in Action: Live Showcase of AI-Powered Hyper-Personalization
Complete your composable story with Sitecore Ordercloud.

My choice was the session titled "Weddings in the Cloud with Sitecore Connect!" facilitated by Sandeep Bhatia and Ankit Joshi.

During this session, Sandeep and Ankit elucidated the concept of Warkato which is now Sitecore Connect. They delved into why businesses find Sitecore Connect indispensable for their operations.

Moreover, a live demonstration was conducted, providing an overview of the Sitecore Connect portal. Attendees gained insights into the fundamental building blocks of Sitecore Connect, which include connections, recipes, triggers, and actions.

Sandeep and Ankit showcased how Sitecore XM Cloud, with the assistance of webhooks, can be seamlessly integrated with Sitecore Connect, facilitating the creation of items in Content Hub One.

These two guys always delivering session together as a perfect pair. Happy wedding !!!

5th Session Beyond Buzzwords: Composable Tech and Generative AI for Real by George Smith, Sheetal Jain

During the fifth session titled "Beyond Buzzwords: Composable Tech and Generative AI for Real," led by George Smith and Sheetal Jain, Sheetal Jain was at his best in the session.

Sheetal Jain was in his element as he elucidated the art of designing one's own physical product and swiftly bringing it to life within a tight timeframe.

During a remarkable demonstration, he showcased an impressive application where a commerce store was developed in an astonishing six weeks (if this is indeed the case, hats off to the team!). This store was hosted on Vercel, utilizing a versatile suite of composable products that included Content Hub Operations, Content Hub DAM, OrderCloud, and DALL-E. This ingenious setup empowered individuals to create custom T-shirts and promptly launch them as marketable products with ease.

Furthermore, Sheetal shared his personal journey, evolving from a developer to the esteemed position of CTO. He also highlighted his role in steering a successful training program that transformed backend developers into Next.js developers—a transition that could ultimately lead them to becoming full-stack developers. Sheetal's core message revolved around the importance of customers expressing their needs concisely, with technologists stepping up to provide them with the finest solutions available in the market.

In a captivating twist during the live demo, Sheetal engaged the audience by inviting them to design their own T-shirts, promising to have these creations delivered to their doorstep. (Hope its not a joke otherwise people will ask their Tshirt from Sheetal in SUGCON 2024 😊)

I think Sheetal doesn't require a microphone due to his naturally robust and high-pitched voice.

6 Session “Utilizing Sitecore Edge-Powered Recommendations Enhanced by an Emotion Recognition Model” by “Surendra Kumar Sharma”

This was one of the best session of the day (shhhhhhh) which audience just love(shhhhhhh) where Surendra showed app demo (developed in just 3 days) which combines the power of Sitecore Edge and an advanced emotion recognition model to revolutionize personalized music experiences. By capturing a live video feed from webcam and analyzing facial expressions, this emotion recognition model accurately detects and predicts emotional state of the person in real-time. By using Sitecore Edge's powerful recommendation engine, this app provide you with a curated selection of songs that align with your emotions.

Did I forget to mention that its me!!!

MVP Program and the Community Mentorship by Nicole Montero

This marked the final session of the day, during which Nicole shared insights from her two-year Sitecore journey.

Nicole's presentation revolved around the coveted MVP (Most Valuable Professional) designation, wherein she provided a roadmap on how to attain this esteemed recognition. She also shed light on the MVP Mentorship program, an initiative facilitated by Sitecore, inviting interested individuals to participate. Most of the MVP programs are taking care by Tamas Verga and Nicole.

One can easily spot her in conference as she was the only white lady in conference.

Following this enlightening session, MVP trophies were distributed to many recipients, concluding with a delightful photo session to commemorate the occasion.

The day culminated with a delectable dinner at 8 PM, allowing attendees to expand their network by engaging in conversations and connecting with new faces within the Sitecore community.

Although it was nearly 10 PM by the time we returned home, it was undeniably a day filled with fruitful interactions and valuable experiences.

Day 2:

Day 2 of SUGCON India 2023 began bright and early, with attendees arriving by 8:30 AM. The first order of business for many of us was a hearty breakfast, setting the tone for another day filled with enriching insights and interactions.

The crowd on Day 2 numbered around 120 participants, slightly smaller than the previous day. It's likely that a few attendees were still feeling the effects of the lively gathering from the previous night's party and drinks n daruu.

1st session Build for XM Cloud according to the Architect of XM Cloud by Andy Cohen

Andy's session began on an interactive note as he initiated a game that piqued the curiosity of attendees. The challenge: Who had worked on the maximum number of Sitecore versions? Alistair emerged victorious, having embarked on his Sitecore journey from the 5.x version era, showcasing the enduring dedication of Sitecore enthusiasts.

The heart of Andy's presentation revolved around demystifying XM Cloud. He walked attendees through the essential steps to get started, from adding content and designing your site to creating a tunnel using ngrok for seamless development.

Dos and Don'ts on XM Cloud

One of the most invaluable aspects of Andy's session was his guidance on best practices. He emphasized the need to focus more on front-end technologies rather than diving deep into .NET and back-end code. Furthermore, he advocated for caution when it comes to Sitecore customizations for XM Cloud, highlighting the importance of aligning your strategy with the unique demands of a cloud-based environment.

2nd session Exploring the Experience Edge GraphQL Schema by Alistair Deneys

The second session of Day 2 was a class in the power of GraphQL, presented by none other than Alistair Deneys— the oldest guy ever met in the Sitecore community. Alistair holds the distinction of being the first MVP from Australia and has been an unwavering force in the Sitecore space for the past 18 years.

Alistair's vast experience shone through as he commenced his session by imparting the fundamentals of GraphQL. He then seamlessly transitioned into the fascinating realm of Experience Edge, Sitecore's pioneering foray into headless architectures.

Sitecore Veteran didn't just talk the talk; he walked the walk by conducting live demonstrations. Attendees had the privilege of witnessing how to craft queries for accessing published content and how the source system intricately shapes the schema of the GraphQL API. He unveiled the secrets of effortlessly navigating the documentation generated by the GraphQL schema.

One of the standout moments of the session was when Alistair unveiled how the type of source system (be it Content Hub, Content Hub One, XM, or XM Cloud) dynamically influences the schema. This, in turn, has a profound impact on how developers craft queries against the API.

Alistair went the extra mile by demonstrating practical consumption scenarios. Attendees witnessed how to harness the power of Sitecore's Experience Edge using Powershell scripts and .NET Core C# applications. This hands-on approach left a lasting impression, showing that theoretical knowledge can swiftly transform into real-world solutions.

3rd session FeaaS and Furious - XM To Cloud Component, A true composable offering by Daivagna Nanavati, Akshay Barve

The highlight of this session was the unveiling of XM Cloud Components, a revolutionary low-code, no-code development paradigm. While still in its early stages, the potential was evident as Daivagna and Akshay took attendees on a journey into the future of Sitecore development.

One of the most jaw-dropping moments of the session came when Daivagna and Akshay demonstrated their prowess by creating a page for the SUGCON India website in a matter of minutes. This was achieved by seamlessly crafting components powered by XM Cloud. The process boiled down to the simplicity of drag-and-drop functionalities and the assignment of data sources. Data sources could be direct JSON text, JSON outputs from APIs, or even crafting GraphQL queries.

Attendees were also treated to insights on themes within XM Cloud and effortlessly applying them to components. However, what truly set XM Cloud Components apart was the revelation that all these components are essentially created in Azure Blob, making them independent requests that render as separate HTML. This architecture ensures blazing-fast load times and a seamless user experience.

XM Cloud Components promised not only speed but also a new level of simplicity, making it accessible to developers of all levels of expertise.

Super easy, super fast!!!

4th session Integration of Generative AI within Sitecore: Enhancing Digital Experiences and Content Creation by Khushboo Sorthiya, Priyanka Gulia

It was undoubtedly one of these important sessions. Unfortunately, due to a delightful encounter with former colleagues who had specially visited the conference for few hours, I was unable to attend this session in its entirety.

The good news, however, is that SUGCON India 2023 recognizes the value of knowledge sharing. Sessions are recorded, ensuring that attendees who miss out on any particular session can catch up later. I am eagerly looking forward to watching the recording of this session to gain insights into the integration of Generative AI within the Sitecore ecosystem.

Last session Seamless Migration: Implementing XM Cloud with SXA Headless by Gunasekaran Kuppayee Sengodan, Harender Kumar

Again multiple session were scheduled here. I picked “Seamless Migration: Implementing XM Cloud with SXA Headless”.

Gunasekaran and Harender shared invaluable insights and practical strategies for executing a seamless migration. They emphasized the importance of understanding the unique needs and categories of customers' existing systems. This knowledge serves as the foundation upon which a well-planned migration can be built.

In this session, speakers also explained how the categories customers current system and then plan a process of transitioning from Sitecore XM/XP or other CMS products to a composable DXP using XM Cloud. They also highlighted valuable insights, practical strategies, and key considerations for a smooth migration.

Closing keynote

As the curtains began to fall on SUGCON India 2023, attendees gathered once more for the closing keynote—a heartfelt moment where panel speakers shared their sentiments about India, its people, and the vibrant Sitecore community that calls it home.

A Love for Indian Culture

The keynote was not just about technology; it was a celebration of the rich culture and culinary delights of India. Panelists expressed their affection for Indian food, a cuisine renowned for its diversity and flavors. The warmth of the Indian people also left an indelible impression on their hearts.

Passion for Sitecore in India

The keynote underscored the passion that the Indian Sitecore community brings to the table. The enthusiasm and dedication of Indian developers and marketers for the Sitecore platform was a recurring theme throughout the conference. It was a testament to the dynamic and thriving nature of the community.

Insights and Questions

The audience had the opportunity to pose questions to the panelists. Topics ranged from Sitecore Search and migration to upcoming programs for Sitecore developers. This interactive session ensured that attendees left with valuable insights and answers to their burning questions.

Promise of Tomorrow : Looking Ahead to 2024

As the conference drew to a close, the promise of the next gathering in 2024 hung in the air. Attendees eagerly awaited the announcement of the location, with Goa and Gujarat emerging as the top contenders. The excitement was palpable, and votes were cast. My preference is for Goa, adding to the anticipation for what the next conference will bring.

Creating Lasting Memories

The conference concluded with a memorable photo session, capturing the smiles and camaraderie of Sitecore enthusiasts. The day's experiences were sweetened with tea and delicious pakodas, a perfect ending to a day filled with learning and networking.

With great memories in their hearts, attendees bid adieu to SUGCON India 2023, knowing that they had been part of something special.

Big Thanks to all organisers, sponsors, speakers, audience and to all who contributed to make this Conference successful.

Bye Bye SUGCON India 2023, Hello SUGCON India 2024!!!

Sitecore PowerShell scripts as a datasource

2023-07-06T11:58:00.000+05:30

Powershell script can be used in a data source to solve complex problems in Sitecore.

· For this you can create script which is used to provide a list of child items of a parent item within a data source. For example, the script returns all the child items of the event folder that were created from the event detail template.

· The script tag and full path of the script must be specified in the data source.

· The script can be used in a template data source, a data source location, or a rendering data source.

· The script must return either one item or a list of items for Sitecore to display to the end user.

Here is my YouTube video for the same

Stay tuned for more such articles, tips and tricks.

Embed Sitecore 10.3 form to external website page

2023-06-30T10:13:00.001+05:30

Today, we are going to discuss how to embed a Sitecore 10.3 form on an external website. Sitecore 10.3 is available in the market and offers many new features, including headless SXA and web hooks. The new Sitecore forms use an Embeddable Form Framework, which means that you can create the forms within Sitecore and use them on any type of website, regardless of the technology used.

The benefit of this is that you can collect data from non-Sitecore-based websites and import it into the Sitecore website. This feature is similar to the old FXM feature.

Here are the steps to implement it

· Install Sitecore 10.3

· Rebuild the master and web index

· Install Sitecore Headless Service 21.0.0

· Create and publish an API key

· Create and publish a new form in Sitecore

· Download the Sitecore Embeddable Forms

· Copy the CSS folder and Javascript file to your website's root folder

· Specify the form ID in your HTML or PHP website

· Include the script in your HTML or PHP page

· Pass the API key to the script

· Specify any necessary CSS elements on your HTML or PHP page

Here is my Youtube video for the same

Stay tuned for more such articles, tips and tricks.

Sitecore Mindmap

2023-06-29T09:56:00.001+05:30

Sitecore is a complex platform with many products, features and functionalities, and it can be challenging to keep track of all the details.

A mind map can serve as a single source for quick and easy access to information about a Sitecore products and its different features. It can also be used as a reference guide to quickly find specific information or to communicate the products to the clients, team members and stakeholders.

So I created Sitecore mindmap for reference

I am open to any suggestions or feedback on what else could be included in this mind map that may have been missed!!!!

Here is my YouTube video for the same

Stay tuned for more such articles, tips and tricks.

Webhooks in Sitecore 10.3

2023-05-31T10:18:00.001+05:30

Today we are going to see new features of Sitecore called Web Hooks. Before understanding web hooks, let's try to understand the concept of hooks in general life. Just like we have hooks in our home to hang clothes or fishing hooks, these hooks can hold two different things and join them. Similarly, in programming, web hooks can allow interaction between different applications.

When two different web applications are present, they can be interacted through a callback function. One application can receive real-time notifications through an event. For instance, if something is happening in application one, it will trigger a notification for the other application, which will receive it in code terms. Web hooks can be used in two places: events and workflows. Whenever an item is created, deleted, copied, published or a workflow is submitted, these actions are considered events.

Web hooks can be used to track these events. Sitecore will send information about the event in terms of a JSON request payload to the other application. The Sitecore HTTP post request will be sent to the other application with the payload in JSON or XML format. The other application will receive the request and further process it. There are three types of web hooks that can be created: web hook event handler, workflow, and validation actions.

Here are the steps to implement

· In Sitecore, web hooks can be created through the System section and Web Hooks option.

· To create a web event handler, select a specific event (item added, copied, deleted, etc.).

· Specify the URL for the other application and enable the event.

· A demo was shown with a method created in the Target application to receive input from Sitecore and save it to a file.

· When an item was added in Sitecore, the event was triggered and a file was created on the local machine with the input received from Sitecore.

Here is my YouTube video for the same

Stay tuned for more such articles, tips and tricks.

Simplest way to sort child items in Sitecore

2023-05-28T15:13:00.001+05:30

Today, we're going to explore another hidden feature of the Sitecore.

By default, all items created within the Sitecore are sorted alphabetically. However, if the position of the items has been changed by the content author, the list may not be sorted. In this case, sorting the items manually by clicking on the "up" or "down" option for each item would take a lot of time, especially if there are hundreds of items under a single parent item.

To solve this problem, the easiest way is to select the folder and click on the " sorting" option. This will open a "sort order" window where you can sort the items by different options such as "created date" or "reverse". To reset the order, simply click on "reset", and the items will be sorted accordingly.

This feature is hidden and simple to use, so I hope you will take advantage of it in your project.

Here is my YouTube video for the same

Stay tuned for more such articles, tips and tricks.

ChatGPT with Sitecore

2023-05-25T10:09:00.000+05:30

Today, we are going to take a look at something really cool - Chat GPT. In recent weeks, this technology has been a hot topic of discussion. Chat GPT is a dialog-based artificial intelligence chatbot that can answer your questions in a conversational manner. It's developed by OpenAI, a well-known research lab. The best thing about Chat GPT is that it is stateful, meaning it can remember previous questions and respond accordingly within the same context. You can find more information about Chat GPT on the OpenAI website.

As a developer, one use case for Chat GPT is to migrate CSV or Excel data to Sitecore. For example, if a client asks for assistance in migrating data, a developer can use Chat GPT to determine the best approach for accomplishing this task. The first step is to find out the different ways to migrate data and choose the best option. Once the data is migrated, the developer can assign icons, create packages in Sitecore, and publish the items.

The Chat GPT home page provides lots of information about the technology and can be used to help with a developer task such as migrating Excel file data to Sitecore. By asking Chat GPT for help, the chatbot can provide information on different methods, such as using a custom script or a C# code. Chat GPT can even provide the necessary code to complete the task, such as a C# script or a PowerShell script. The developer can then copy and paste the code into their application and test it.

Here is my YouTube video for the same

Stay tuned for more such articles, tips and tricks.

Insights from the "15 Ways of Content Migration to Sitecore" webinar

2023-05-22T10:05:00.001+05:30

Introduction:

On May 20, 2023, I presented webinar on "15 Ways of Content Migration to Sitecore", offering valuable insights and practical strategies for successfully transitioning content to the Sitecore platform.

Understanding the Complexity of Content Migration:

Content migration is a critical phase in any Sitecore implementation project, requiring meticulous planning, strategic decision-making, and a thorough understanding of both the source and target systems. The webinar emphasized the importance of recognizing the complexity involved in content migration and provided attendees with a different way to achieve it.

Exploring 15 Effective Content Migration Strategies:

The core focus of the webinar was to equip participants with a diverse set of strategies and techniques to tackle content migration effectively. I navigated through 15 different approaches, each tailored to address specific scenarios and requirements. From manual content transfer to automated migration tools, attendees gained insights into a wide range of methodologies to streamline the migration process.

Empowering Sitecore Professionals:

The "15 Ways of Content Migration to Sitecore" webinar left attendees feeling empowered and equipped with a wealth of knowledge to tackle content migration projects with confidence.

Here is the YouTube video for the same!!!

5 ways to set Alt text for images in Sitecore

2023-04-30T19:47:00.000+05:30

Introduction:

Alt text is a crucial part of website accessibility and SEO, as it provides a description of the content of an image to people with visual impairments. Sitecore provides various ways to set Alt text for images, from manual to automatic using AI. In this article, we will explore the different ways to set Alt text for images in Sitecore, including manual, via C# code, via PowerShell, using Config setting "Media.AutoSetAlt", and AI with sample code.

Manual:

The most basic and straightforward way to set Alt text for images in Sitecore is to do it manually. You can do this by uploading the image to the Media Library and setting the Alt text manually in the "Alt" field of the image. When you click on the image, you will see the editing options on the right-hand side of the screen. In the "Alt" field, add a description of the image, which will be read by screen readers.

AI with image tagging:

This approach uses Azure Cognitive Services' Computer Vision API to generate a description of an image and sets it as the alt text of the corresponding image item in Sitecore using C# code.

The steps involved in this approach include installing the Azure Cognitive Services Computer Vision NuGet package, creating an instance of the ComputerVisionClient class with your subscription key and endpoint, and calling the AnalyzeImageAsync method to get a description of the image.

The retrieved description is then set as the alt text field of the image item in Sitecore using the Sitecore API.

This approach can be useful when you have a large number of images in Sitecore that require alt text descriptions, as it can automate the process of generating descriptions and setting them for each image item.

However, it's important to note that the accuracy of the generated descriptions may vary depending on the image and the complexity of its content. Therefore, it's recommended to review and potentially modify the descriptions as needed to ensure they accurately reflect the content of the image.

Via C# code:

If you want to set Alt text for images programmatically, you can do so using C# code. You can use the Sitecore API to set the Alt text for an image. Here is an example code snippet:

using Sitecore.Data.Items;

using Sitecore.Resources.Media;

// Get the MediaItem for the image

var mediaItem = (MediaItem)Sitecore.Context.Database.GetItem("/sitecore/media library/Images/my-image");

// Save the changes

mediaItem.Editing.BeginEdit();

mediaItem.Alt = "This is my image";

mediaItem.Editing.EndEdit();

In the code above, we first get the MediaItem for the image we want to set the Alt text for. Then, we set the Alt text using the "Alt" property of the media item. Finally, we save the changes by calling "BeginEdit" and "EndEdit" on the media item.

Via PowerShell:

Sitecore PowerShell is a powerful tool that allows you to automate tasks in Sitecore. You can use PowerShell to set Alt text for images in bulk. Here is an example script that sets the Alt text for all images in a folder:

$imagesToBeUpdated = "/sitecore/media library/2023 Images"

$images = Get-ChildItem -Path $imagesToBeUpdated -Language * -Recurse |

Where-Object { ($_.Fields["Alt"] -ne $null) -and ($_.Fields["Alt"].Value -eq '' -or $_.Fields["Alt"].Value -eq '$name') }

$images |

ForEach-Object {

write-host "Updating Alt text for - " $_.Name

$_.Editing.BeginEdit()

$_["Alt"] = $_.Name

$_.Editing.EndEdit() | Out-Null

}

In the script above, we first get the folder we want to set the Alt text for. Then, we loop through all the media items in the folder using the "Get-ChildItem". For each media item, we check if the Alt text is empty, and if it is, we set the Alt text using the "BeginEdit" and "EndEdit" methods.

Using Config setting "Media.AutoSetAlt":

Sitecore also provides an automatic way to set Alt text for images using a configuration setting called "Media.AutoSetAlt". When this setting is enabled, Sitecore will automatically set the Alt text for an image using its file name. Here's how to enable this setting:

1. Open the Sitecore.config file located in the \App_Config\Include\ folder

2. Search for the "Media.AutoSetAlt" setting in the file.

3. <setting name="Media.AutoSetAlt" value="true" />

3. Save the Sitecore.config file.

Now, when you upload an image to the Media Library, Sitecore will automatically set the Alt text using the file name. For example, if you upload an image named "my-image.jpg", Sitecore will set the Alt text to "my-image".

Conclusion:

In conclusion, setting Alt text for images is essential for website accessibility and SEO. Sitecore provides various ways to set Alt text for images, from manual to automatic using AI. Each method has its own advantages and disadvantages, and you should choose the method that best fits your needs. Manual and C# code methods are suitable for setting Alt text for individual images, while Sitecore's with AI solution provides an advanced way to set Alt text by analyzing the image. Whereas PowerShell is suitable for bulk operations. Finally, using the "Media.AutoSetAlt" setting is suitable for setting Alt text automatically based on the file name. By using these methods, you can ensure that all images on your website have appropriate Alt text and are accessible to everyone.

Here is video for the same

Sitecore Technology Radar

2023-04-23T18:58:00.007+05:30

Sitecore is a leading digital experience platform that empowers organizations to deliver personalized and engaging digital experiences to their customers. As with any technology, there are constantly new tools and trends emerging in the Sitecore ecosystem that can impact an organization's digital strategy. A Sitecore technology radar can help organizations stay informed about these changes and make informed decisions about which technologies to adopt, trial, assess, or hold.

Sitecore technology radar typically consists of four rings, each representing a different level of adoption and maturity for a particular technology: Adopt, Trial, Assess, and Hold. Let's explore each of these rings in more detail.

Adopt

In the Adopt ring, technologies are widely adopted and proven to be effective in the Sitecore ecosystem. These technologies are generally stable and reliable, and organizations can confidently use them to support their business needs. Some examples of technologies in the Adopt ring for Sitecore include:

Sitecore Experience Platform (XP)
Content Hub DAM
Sitecore JSS (JavaScript Services)

Trial

In the Trial ring, technologies are emerging and have shown potential, but are not yet widely adopted. Organizations may experiment with these technologies to gain experience and assess their potential value. Some examples of technologies in the Trial ring for Sitecore include:

Sitecore XM Cloud
Sitecore SXA (Sitecore Experience Accelerator)
Sitecore CDP

Assess

In the Assess ring, technologies are on the horizon and are being evaluated for their potential value. These technologies are not yet fully understood, and organizations need to carefully evaluate their potential benefits and risks before making any decisions. Some examples of technologies in the Assess ring for Sitecore include:

OrderCloud
Sitecore Search

Hold

In the Hold ring, technologies are no longer recommended for use. These are technologies that have become outdated, are no longer supported, or have been replaced by newer technologies. Some examples of technologies in the Hold ring for Sitecore include:

Sitecore Commerce
Web Forms for Marketers (WFFM)
Sitecore Experience Database (xDB)

By regularly reviewing and updating their Sitecore technology radar, organizations can stay ahead of emerging trends and make informed decisions about which technologies to adopt, trial, assess, or hold. This can help organizations to optimize their Sitecore digital experience and stay competitive in the rapidly evolving digital landscape.

Here is the Youtube video for the same!!!

Reasons to move from Sitecore XP to Sitecore XM Cloud

2023-04-10T10:49:00.002+05:30

As businesses continue to evolve and innovate, their digital strategies and web development needs must also adapt. In recent years, we have seen a shift towards using cloud-based platforms for web development and deployment, and the adoption of JavaScript-based frameworks for front-end development. Sitecore, a leading digital experience platform, has embraced this trend with the introduction of Sitecore XM Cloud and Next.js.

If you currently have a Sitecore XP MVC-based website, you may be wondering why you should consider moving to Sitecore XM Cloud and Next.js. Today, we will explore some of the key benefits of making the move, and why it could be the right choice for your business.

Here are some of the key reasons why businesses may want to consider moving from Sitecore XP to Sitecore XM Cloud:

.NET Framework
Scalability
Improved Performance
Reduced Costs
Flexibility
Security
Faster time to market
Global reach
Ease of use
Improved collaboration
Continuous innovation
Better customer experiences
Reduced complexity
Lower total cost of ownership

.NET Framework

Since the .NET framework is on its way out, it would be wise to steer clear of it and redirect attention towards Javascript frameworks. As cloud is the future, it's a favorable time to start investing and focusing on cloud-based technologies.

Scalability

One of the main benefits of Sitecore XM Cloud is its scalability. Sitecore XM Cloud is a cloud-based platform that is designed to handle large amounts of traffic and data, making it ideal for businesses that need to scale quickly to meet demand. With Sitecore XM Cloud, businesses can easily scale up or down as needed, without having to worry about infrastructure management or capacity planning.

Improved Performance

Sitecore XM Cloud also offers improved performance compared to Sitecore XP. Sitecore XM Cloud is designed for high availability and reliability, ensuring that your website or application is always up and running. Additionally, Sitecore XM Cloud includes a range of performance optimization tools, such as Content Delivery Networks (CDNs) and caching, which can improve page load times and reduce server response times.

Reduced Costs

Another benefit of Sitecore XM Cloud is that it can help businesses reduce costs. Sitecore XM Cloud is a fully managed service, which means that businesses don't need to worry about infrastructure management or maintenance. This can significantly reduce the costs associated with managing and maintaining an on-premises infrastructure.

Flexibility

Sitecore XM Cloud also offers greater flexibility than Sitecore XP. Sitecore XM Cloud is a headless platform, which means that it can be integrated with a wide range of front-end frameworks, allowing developers to use the tools and frameworks that they are most comfortable with. This can help businesses build highly customized, tailored solutions for their clients.

Security

Sitecore XM Cloud provides enhanced security features, such as automatic updates and patches, proactive monitoring, and 24/7 security operations support. This can help businesses ensure that their websites and applications are protected against cyber threats.

Faster time to market

Sitecore XM Cloud includes a range of pre-built templates and components, which can help businesses get their websites and applications up and running quickly. This can significantly reduce the time to market for new digital experiences.

Global reach

Sitecore XM Cloud is designed to support businesses with a global presence. It includes a range of features, such as geo-targeting, multi-language support, and local hosting options, which can help businesses deliver personalized, localized experiences to users around the world.

Ease of use

Sitecore XM Cloud includes a user-friendly interface that makes it easy for businesses to manage their digital experiences. It also includes a range of tools for content management, analytics, and personalization, which can help businesses improve the efficiency and effectiveness of their digital operations.

Improved collaboration

Sitecore XM Cloud includes collaboration tools that can help teams work together more effectively.

Continuous innovation

Sitecore XM Cloud is a cloud-based platform that is continually updated with new features and capabilities. This means that businesses can benefit from the latest innovations and best practices without having to worry about upgrading their infrastructure or software.

Better customer experiences

Sitecore XM Cloud is designed to help businesses deliver exceptional customer experiences across all channels and touchpoints. By leveraging the power of Sitecore XM Cloud, businesses can create personalized, targeted experiences that engage and delight their users, driving loyalty and advocacy.

Reduced complexity

Sitecore XM Cloud is designed to simplify the digital experience management process, making it easier for businesses to manage and optimize their websites and applications. By reducing complexity, businesses can free up resources to focus on other areas of their business, such as innovation, product development, and customer engagement.

Lower total cost of ownership

Sitecore XM Cloud can help businesses reduce their total cost of ownership by eliminating the need for on-premises infrastructure and reducing maintenance and management costs. Additionally, Sitecore XM Cloud includes flexible pricing options, which can help businesses tailor their costs to their specific needs and usage patterns.

Conclusion

There are many reasons why businesses may want to consider moving from Sitecore XP to Sitecore XM Cloud. By leveraging the scalability, performance, security, flexibility, collaboration, insights, innovation, customer experience, and simplicity of Sitecore XM Cloud, businesses can achieve their digital transformation goals and drive growth and success in the digital age.

Here is video for the same

8 ways to Find and Replace text in Sitecore

2023-04-03T07:27:00.004+05:30

The utilization of the find and replace technique is immensely valuable for both editors and developers who seek to modify individual or multiple pieces of content within a Sitecore instance.

To facilitate this process, here is my recorded Youtube video that shows 8 potential approaches to conducting find and replace operations in Sitecore.