11

As you know Rainbow is an open source advanced serialization and comparison system for Sitecore which is using a YAML format. In Sitecore 9.2 there is a new serialization implemented in a YAML format. So Rainbow and Sitecore 9.2 both using YAML format, but they are not the same. Sitecore is not using the Rainbow serialization format!


11

Unicorn 3 and above has an option to exclude child items under parent item. In your case you can use as below: <include database="master" name="WFFMSaveActions" path="/sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions"> <exclude path="/sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save ...


9

TDS Classic 5.7 (released after this question was initially posted) now has a 'Sync all projects with Sitecore' feature. This is a context menu option on the solution (under the Team Development for Sitecore group) when you have TDS 5.7 installed, and allows you to run a sync across all TDS projects in the solution. https://www.teamdevelopmentforsitecore.com/...


8

Here is a prototype for you to test with in your non-production instance. Sitecore PowerShell Extensions $items = @(Get-Item -Path "master:\content\home") + @(Get-ChildItem -Path "master:\content\home") $expression = "\d{8}[T]\d{6}" foreach($item in $items) { $item.BeginEdit() | Out-Null if($item.Fields["__Created"].HasValue -and ($item.Fields["...


7

One way to do this using Unicorn 3 is with <exclude> and <except> elements. This can be done like so: <include name="xxxxxx.Foundation.CustomWffmFieldTypes.SaveActions" database="master" path="/sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions"> <exclude children="true"> <except ...


7

TL;DR Some possible solutions to reduce build/deployment time:- Reduce the number of projects in your solution by 'compacting' projects. Reduce the number of projects in your solution by having a Tests-project-free sln file. Create an sln file with the explicit ProjectDependencies removed. This would only be for local builds. It doesn't help you for your ...


7

The previous answer is correct for default configuration on Sitecore 8 or 9. The serialization folder path can be set using next setting . <!-- SERIALIZATION FOLDER Points to the root of serialized databases tree (when using serialization functionality). Default value: $(dataFolder)/serialization --> <setting ...


6

Sitecore does not automatically do anything with serialization files from TDS out of the box. Now this doesn't rule out a custom schedule task that someone may have put into the system, but that doesn't seem likely. When TDS syncs, it can be configured to publish any items that it syncs, but that would be dependent upon how you have TDS setup in your CI ...


6

The issue is inherent with the way Sitecore handles checkbox fields and how it serializes items. Checkbox Field Checkbox fields in Sitecore can have 3 values: Blank (not set) 0 (unchecked) 1 (checked) Blank and 0 are interpreted as the same value of false value when reading the fields on an item through the Item API. Serialization During serialization (...


6

I asked a similar question a little while back, about the interop between Sitecore and Unicorn on disk files. If you have Transparent-Sync on or have your Unicorn.DataProvider.config file configured, then there is a direct relation between Sitecore and the Unicorn serialization files on disk. If you update an item, in a part of Sitecore that is tracked, the ...


6

Remove all data from your shared session database and the errors will go away. Your custom types have changed, but at the same time, old facet objects remain binary-serialized in your shared session database (as a part of Contact objects). And so your session store provider cannot deserialize them anymore. .NET binary serialization doesn't throw exceptions ...


5

You should set up a Global Config file as per the documentation. You can then set the URL and path as follows: <SitecoreWebUrl>http://your.url</SitecoreWebUrl> <SitecoreDeployFolder>C:\inetpub\wwwroot\your.path</SitecoreDeployFolder> You can then go through your TDS projects properties and make sure it is inheriting from the global ...


5

Security stored on items Access rights (security) are stored on the item itself, in the __Security field. You can see the contents of this field in a few ways: Security Details tab In the Content Editor, under the Security ribbon tab, click the Details button and you will see the following tab: Raw field values If you want to be able to copy the ...


5

The issue may be related to your other question where it appears that you have some invalid date formats. From the StackTrace it looks like the issue is related to one of the Media facets. I would try disabling the 'Date uploaded' facet under /sitecore/client/Applications/Dialogs/SelectMediaDialog/PageSettings/Facets from the Core database to see if that ...


5

This is hard to answer because it's really several questions at once. To start with, YES Unicorn 3 handles things much better because it has more control over its serialization system. Unicorn 2 is a bit hamstrung because it's using the built in APIs which have some fun bugs. Unicorn 2.x should, however, support most kinds of renaming without issue. If your ...


5

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.sitecore.com/developers/100/developer-tools/en/sitecore-content-serialization.html This documentation is for the "legacy" serialization functionality, which ...


5

You need to add the serialization plugins. dotnet sitecore plugin add -n Sitecore.DevEx.Extensibility.Serialization


4

Actually; Reserialize means "Delete local files and take whatever is in Sitecore and serialize that to local files". Sounds to me like you may have been getting the terms mixed up. If you want to set Sitecore back to where it was; checkout the branch at the commit you want to roll back to and issue a Sync (not Reserialize).


3

Sitecore PowerShell Extensions - Web API As pointed out by Richard, SPE comes with some ways to do this. You can find more details about the latest version of SPE Remoting here. For now we will stick the Web API option which will give you a url similar to that in your example. Here are some steps to get you going: Install SPE 4.3+. Enable the Web API ...


3

There isn't anything OOTB that will allow you to hit a rest service. You have a couple of options: Sitecore PowerShell Extensions You could use Sitecore PowerShell Extensions remoting to do that fairly easily. Syntax to serialize an item is: serialize-item -path "master:\content" If you want children included, then: get-childitem "master:\...


3

You can't do that in a single file. Once you exclude children of root item you cannot, later on, include it back. You separate files for this, e.g.: <?xml version="1.0" encoding="utf-8" ?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <unicorn> <configurations> ...


3

You can do this by using the NewItemsOnly evaluator in your configuration. You would need to setup multiple configurations for this tho as you can only use one evaluator per configuration. <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <unicorn> <configurations> <...


3

Security informations are stored on the item and stored in the __Security Field. This is a shared field and you should find it in SharedFields table. To get the value from database, you can trigger below SQL query SELECT Id, ItemId, FieldId, Value, Created, Updated FROM SharedFields WHERE ItemId = '{A57C19C2-8EE3-4DEC-AA39-0B8D522D59EB}' AND ...


3

This usually means that your .\sitecore\user.json file is not yet in your folder structure. I had this happen to me when I initially downloaded a project and tried to get things up and running from what is in source control. Typically, the user.json file is user-specific so is not in source control, therefore would be missing after your first download of a ...


2

I think you have a misunderstanding of how TDS and Source Control work. First, TDS does not have any integration or dependency on a Source Control system. You can use TDS with Git, SVN, TFVC, whatever you want to use. All TDS is doing is taking the items from the Sitecore database and persisting them to files on the disk. In Visual Studio, it creates a ...


2

You can choose any folder. Just not one that is being used for anything else. The reason being; the Unicorn default datastore expects YML files of Items. Roles and Users are not items - the two stores are not compatible.


2

First thing is never remove the "website" site definition. Just keep it after all of your custom site definition and don't remove it. It will/should be used as the fallback site definition in case any of the requests doesn't find any matching site definition in your custom sites. Another thing is, Sitecore content editor uses the "shell" site definition to ...


2

I would recommend not using gulp to perform the deployments. Or maybe you can modify the script, as it's currently calling MSBuild on every TDS project in your solution. If you setup the solution to have the appropriate build order, then a single call to deploy the solution would save time for a full solution deploy. You can set the ProjectDependencies on ...


2

PSE sounds like a goer, though if you're not comfortable with PowerShell and as it's a migration project which you're going to re-run then you could do something with the rules engine. On the 8.x instance when the content item from 6.x saves, have a rule which examine the date fields and change as appropriate. Can only find an old cookbook (https://sdn....


2

Cleanup databases triggers a cleanup of the SQL tables, not of content items' effective data. Serialized item state should be unaffected by a cleanup.


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