Content Insights Tip #50 | Unveiling the Power of the Tokens in Sitecore Standard Values

 

Content Insights Logo

In the dynamic world of Sitecore, efficient content management often hinges on clever features that streamline processes. One such feature that plays a pivotal role in this context are the tokens. In this blog post, we'll explore the capabilities of the tokens, their applications in standard values, and some important considerations to keep in mind.

Understanding the Sitecore Token

At its core, the tokens in Sitecore serve as a placeholder that gets replaced with the name of the item during its creation. This substitution occurs exclusively at the time of item creation, shaping the field contents with the actual name of the item. This mechanism offers a level of automation that can significantly enhance the efficiency of your content creation workflows.

Out-of-the-Box Standard Values tokens

Sitecore comes equipped with a suite of predefined standard value tokens, each serving a distinct purpose. Here's a quick overview of the expanded standard values tokens provided out of the box:

  • $name: Represents the name of the item
  • $date: Reflects the current server date
  • $time: Represents the current server time
  • $now: Captures the current server date and time
  • $id: Denotes the unique Item ID
  • $parentid: Signifies the Item’s Parent ID
  • $parentname: Represents the Item’s Parent Name

Token replacement

It's important to note that the replacement of the tokens occurs exclusively during the initial creation of the item. Once the item has been created, the item name becomes the permanent content of the field, replacing the token in the standard values.

A Note of Caution

While the tokens bring a level of automation, it comes with a noteworthy caveat. If a user decides to rename an item, the token is not re-evaluated. Consequently, fields that were assigned a value using a token will persist with the original item name, even after the item has been renamed. To address this, users may need to reset the field value, causing it to display the literal value "$[token]." Subsequently, the user must manually set a more relevant field value.

This behaviour underscores the importance of careful consideration when leveraging a token. It's a powerful tool for initial item creation, but users must be aware of its behaviour post-renaming and take appropriate steps to ensure accurate and meaningful field values.

Conclusion

In conclusion, the tokens in Sitecore are a valuable asset for automating item naming during creation. When wielded with an understanding of its dynamics and limitations, it can greatly enhance the efficiency and consistency of content creation workflows in your Sitecore instance.

Think before you implement!