Shortcuts = time savers. Sometimes the easy way is just as efficient as the hard way. Raw values are not just something that is checked in the content editor menu ribbon by accident. Utilizing them can save valuable time and also help you fix things that are not so easy to fix. I will take you through some examples when I have used them.
Turning on Raw Values
First though let’s turn them on. You can find them on the top ribbon under View. Just check Raw values. Keep in mind if you don’t want to see them, just uncheck them to go back to normal. There is always a case when someone forgets to uncheck them or accidentally checks them.
Rich Text
This is one is pretty straightforward. I have come across issues with an RTE field having HTML that just does not want to display right. Even when you select Edit HTML it still doesn’t work. With raw values turned on you can see what exactly is in that field and edit it. Especially handy for the expert front-end developers.
Not Raw:
Raw:
Multilists
Multilists visually look like a simple selection. Sometimes though you want the same values in a similar item and don’t feel like clicking the same selections. Or you are searching for a template that is inherited and you don’t feel like clicking through the tree. Raw values to the rescue.
Typical Multilist – Not Raw:
Raw:
As you can see above the values that are selected show as a GUID separated with a Pipe | symbol. If you want to have the same values in another item, just copy the values. Then, paste them into the same field in the other item. Or copy the GUID you want. Add a | and the GUID to the item field you are copying to. This also comes in handy for template inheritance. It is often easier to use the template GUID being inherited to search and find it.
Presentation Layer
This is one of my favorite ways to use raw values. This has saved time many times. Using raw values in presentation layers can fix some of the following issues by copying, pasting, removing values.
- Different layout between language versions.
- Accidentally removed rendering.
- Remove rendering that has been deleted based on GUID.
Not Raw:
Raw:
PowerShell
Now you have an idea of how values are stored in Sitecore. When writing PowerShell scripts basically updating something can be simple as setting the GUID list.
$_.Editing.BeginEdit()
$_.Fields["SpeakerList"].Value = "{0D17BE5B-EC2A-4296-8D3F-930EB60DFE7C}|{1930BBEB-7805-471A-A3BE-4858AC7CF696}|{6DB09CEF-64A8-52A3-A980-38408109C4D7}|{47151711-26CA-434E-8132-D3E0B7D26683}|{6650FB34-7EA1-4245-A919-5CC0F002A6D7}";
$_.Editing.EndEdit()
Your Turn
So how do you use Raw Values? I know there is more uses for them.
Sitecore Runner | Rob Reilley | Sitecore MVP 