9 votes
Accepted

Error invalid_grant when trying to serialize items with Sitecore cli

You just need to login into your Sitecore instance by running the following command from your project root folder. dotnet sitecore login --authority "https://your.id.host" --cm "https://...
André Andrade's user avatar
7 votes
Accepted

Can Sitecore 10 Content Serialization serialize users and roles?

No, this is not yet supported but is in the roadmap. (I am the Product Manager for the Sitecore CLI.) The documentation for the CLI and Sitecore Content Serialization is found here: https://doc....
nickwesselman's user avatar
3 votes
Accepted

Pull items by language

It is not. Serializing an item that has no versions should still be possible however, you should bring this to Sitecore Support. All current options available to you can be found in the Sitecore ...
Mark Cassidy's user avatar
  • 25.2k
3 votes

Can not install Sitecore.CLI for Sitecore 10

I found the fix to this. In Visual Studio 2017 or 2019: Navigate to Tools > NuGet Package Manager > Package Manager Settings > Package Sources and remove the reference to Sitecore NuGet. This ...
Nikola Kramaric's user avatar
2 votes

How to ignore specific fields from being serialized?

The excluded fields feature is available from CLI 4.0 or later. You can add "excludedFields" in sitecore.json configuration file like that: "excludedFields": [ { "...
Marek Musielak's user avatar
  • 23.8k
2 votes

Can Sitecore 10 Content Serialization serialize users and roles?

Based on Sitecore 10 documentation, yes - https://doc.sitecore.com/developers/100/sitecore-experience-manager/en/serialize-an-item-or-a-tree-of-items-484805.html. You can serialize security entities. ...
Tamás Tárnok's user avatar
2 votes
Accepted

Sitecore CLI 4.1.1 - You are not authorized to perform the task you are attempting

The Sitecore CLI command that was failing was: dotnet sitecore ser pkg install -n dev -f "C:\deploy\content.itempackage" When I attempted to install the package from my local Sitecore CLI, I ...
Chet Cheeto's user avatar
2 votes

Why did SCS change branch template $name item paths to start with "_" instead of "#"?

This conversion from Dollar('$') to ('#') is occuring from the below code snippet inside Sitecore.DevEx.Serialization.Client.dll, which converts all the invalid file characters to '#' symbol. I ...
ckhanna's user avatar
  • 376
2 votes

(***GUID***) attempted to be cached, but the cache already contained /sitecore/content/****

As per my knowledge, there is no cache setting that can help with this kind of error. As this is looking like a duplicate content issue. Before pushing the item, you should validate your content using ...
Sumit Bhatia's user avatar
  • 5,035
1 vote

(***GUID***) attempted to be cached, but the cache already contained /sitecore/content/****

This error is usually caused by duplicated items in sitecore. I would check your preprod env. Most likely you'll find duplicates (in terms of items with the same name). You can delete the one which ...
benihamalu's user avatar
1 vote
Accepted

Getting error while deploying SCS $name item via AzDo pipeline: "Unable to find item data for $name"

This problem can occur when you have different versions of the CLI involved in the process. Older versions serialize "$name" as "_name". Newer versions serialize "$name" ...
shivers999's user avatar
1 vote
Accepted

Sitecore CLI Scope & AllowedPushOperations property equalents in TDS

Here you can find the Sitecore CLI option equivalents for TDS. TDS - ItemDeployment CLI - allowedPushOperations NeverDeploy Ignored DeployOnce CreateOnly No Equivalent Option Available ...
Sudheer Suggu's user avatar
1 vote

Sitecore CLI Scope & AllowedPushOperations property equalents in TDS

Sukesh, I have not used TDS much. So I will be answering SCS part of your question. TDS - ItemDeployment > NeverDeploy If you want to ignore a specific node in SCS, you can make use of rules ...
Vikrant Punwatkar's user avatar
1 vote

DevOps build pipeline failing on SCS serialize/package step

I agree with Marcel that upgrading CLI is the recommended way in most cases. But if for some reason you cannot upgrade, you can still install .Net Core 3.1 on build agent with the following task: - ...
Marek Musielak's user avatar
  • 23.8k
1 vote
Accepted

DevOps build pipeline failing on SCS serialize/package step

Sitecore CLI 4.2.1 does in fact depend on .NET Core 3.1. .NET Core 3.1 reached end of life at the end of 2022: https://devblogs.microsoft.com/dotnet/net-core-3-1-will-reach-end-of-support-on-december-...
Marcel Gruber's user avatar
1 vote
Accepted

Serialize parent as CreateAndUpdate but descendants as CreateOnly

Replace DescendantsOnly with ItemAndDescendants inside rules like that: { "name": "dictonary", "path": "/sitecore/content/Dictionary", "scope":...
Marek Musielak's user avatar
  • 23.8k
1 vote
Accepted

NU1101: Unable to find package SVS.Build.No packages exist with this id in source(s)

Please add the following source in the NuGet.config file with the developer collection feed and it would resolve the error. <add key="SVSComponents" value="https://sitecore.myget....
Gayathri Sriram's user avatar
1 vote
Accepted

Sitecore Content Serialization to include parent item as create only

Adding in an answer as I can't add json properly in the comments, can you try with the following? { "name": "SiteContent", "path": "/sitecore/content/ABCGroup/...
Cristi Vulturar's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible