Improved Scripting SDK Entity Copying in Sitecore: A Smarter Way to Manage Content Hub Entities

Improved Scripting SDK Entity Copying in Sitecore: A Smarter Way to Manage Content Hub Entities

In today’s fast-moving digital environment, developers are constantly looking for ways to simplify content management, reduce repetitive tasks, and build more efficient workflows. When working with Sitecore Content Hub, copying entities is a common requirement, especially when creating new projects, managing content templates, or reusing existing entity data.

To make this process more flexible and developer-friendly, Sitecore has introduced an improvement to Scripting SDK Entity Copying.

Announced on October 30, 2026, this enhancement brings better control over entity-copy operations by allowing developers to combine direct copy options with existing copy profiles. It also introduces improved relation-overwriting capabilities, making it easier to create new entities from templates directly through the Scripting SDK.

Let’s explore what has changed, how it works, and why this improvement matters for Sitecore developers.

What Is Scripting SDK Entity Copying in Sitecore?

The Sitecore Scripting SDK provides developers with the ability to automate operations and customize workflows within Sitecore Content Hub.

One important capability is entity copying. It allows developers to create a new entity using an existing entity as the source. Instead of manually recreating properties, metadata, and relationships, developers can reuse existing information and customize the copied entity according to their requirements.

For example, imagine a marketing team regularly creates campaigns using a standard campaign structure. Rather than creating every campaign from scratch, developers can configure an existing campaign as a template and use entity copying to generate new campaigns with the required information.

This approach helps reduce repetitive work and maintain consistency across Content Hub.

What’s New in Improved Scripting SDK Entity Copying?

The latest improvement focuses on making entity-copy operations more flexible and predictable.

Previously, developers typically relied on copy profiles to define how entity properties and relations should be copied. With the new enhancement, developers can combine copy profiles with direct copy settings.

Here are the key improvements:

1. Combine Direct Copy Options with Existing Copy Profiles

One of the most useful changes is the ability to use direct copy options alongside an existing copy profile.

A copy profile provides predefined rules for copying entity properties and relations. However, not every copying scenario follows the same requirements.

With the improved functionality, developers can reuse an existing copy profile while specifying additional settings directly in their scripts.

For example, consider a project template containing:

• Project name
• Description
• Project owner
• Related assets
• Other metadata

A developer can use the existing copy profile to reuse the standard project configuration while directly changing the project name and assigning a different owner.

This makes the copying process more adaptable without requiring developers to create a separate copy profile for every small variation.

2. Direct Copy Settings Take Priority Over Profile Defaults

Another important enhancement is the priority given to direct copy settings.

When developers combine direct settings with a copy profile, the explicitly configured options take precedence over the corresponding profile defaults.

In simple terms, the copy profile provides the default configuration, while direct copy options allow developers to customize specific values when needed.

For example:

Configuration	Expected behavior
Copy profile	Defines the default entity-copy rules
Direct property option	Overrides the corresponding profile setting
Direct relation option	Overrides the corresponding profile relation setting

This gives developers greater control over the final copied entity.

It also reduces the need to maintain multiple similar copy profiles for different business requirements.

3. Improved Relation Overwriting Using New Links

Entity relationships are an important part of Sitecore Content Hub.

An entity may be connected to users, assets, projects, campaigns, or other related entities. When copying an entity, managing these relationships correctly is just as important as copying its properties.

The latest improvement adds support for overwriting relations using new links.

This provides developers with more precise control over relationships during the copying process.

For example, when creating a new project from a template, developers may want to retain the template’s general configuration but assign a different project owner.

Instead of simply carrying forward the original relationship, the script can configure the new relationship explicitly.

This helps ensure that the copied entity is connected to the correct users or related records.

4. Create Blocks Directly from Templates Using the SDK

One of the practical benefits of these improvements is the ability to create blocks from templates directly through the Scripting SDK.

Previously, developers could rely on the legacy copy.block command for this type of operation.

With the improved SDK entity-copying capabilities, developers can handle these scenarios directly through the SDK.

This makes the implementation more consistent and provides greater flexibility when building custom automation and template-based workflows.

The legacy copy.block command is therefore no longer necessary for this particular use case.

How Does the Improved Entity Copying Process Work?

Let’s understand the updated approach through a simple example.

Suppose a company maintains a standard project template in Sitecore Content Hub. Whenever a new project is required, the development team wants to:

1. Copy the existing project template.
2. Reuse the default properties and relations configured in the copy profile.
3. Set a new project name.
4. Assign a different project owner.
5. Create the new project with the customized values.

The improved Scripting SDK entity-copying functionality makes this workflow easier to manage.

The general implementation approach is:

• Retrieve the source template entity.
• Prepare the entity-copy options.
• Configure the required copy profile.
• Add direct property and relation overrides.
• Execute the SDK copy operation.
• Validate the newly created entity and its relationships.

Sitecore’s documented project-from-template example demonstrates this pattern using an action script and the CopyAsync operation.

Why Does This Improvement Matter for Sitecore Developers?

Although entity copying may appear to be a small development task, it can have a significant impact on content management workflows.

Here are some practical benefits of the enhancement.

Less repetitive development: Developers can reuse existing copy profiles instead of maintaining multiple configurations for similar copying requirements.

Greater customization: Direct copy settings make it easier to modify individual properties and relations without changing the underlying profile.

Better relationship management: Explicit relation overrides help ensure that copied entities reference the intended users and related records.

Simpler template-based automation: Creating projects and blocks from existing templates becomes more straightforward through SDK-based workflows.

Improved maintainability: A combination of reusable defaults and targeted overrides can make entity-copying logic easier to understand and maintain.

Things Developers Should Consider Before Implementation

To get the most out of improved Scripting SDK Entity Copying, developers should consider a few important points.

• Review existing copy profiles: Understand which properties and relations are already configured before introducing direct overrides.
• Check relation requirements: Verify that new entity relationships point to the intended target entities.
• Validate copied metadata: Confirm that the resulting entity contains the expected property values.
• Test template-based workflows: Test different copying scenarios, including cases where only a few properties or relations need to change.
• Review existing scripts: Identify workflows that still depend on the legacy copy.block command and evaluate whether they can benefit from the updated SDK approach.

Proper testing is important to ensure that the updated copying behavior matches the requirements of your Content Hub implementation.

Final Thoughts

The improved Scripting SDK Entity Copying capability is a useful enhancement for developers working with Sitecore Content Hub.

By supporting the combination of copy profiles and direct copy options, prioritizing explicit settings, and allowing more precise relation overwriting, Sitecore makes entity-copying workflows more flexible and easier to customize.

For development teams building automated project creation, template-based workflows, and custom Content Hub functionality, this improvement offers a cleaner approach to managing entity data.

At Skybridge Infotech, we believe that staying updated with the latest Sitecore enhancements is essential for building scalable, maintainable, and efficient digital solutions.

Whether you’re optimizing existing Content Hub workflows or developing new Sitecore customizations, understanding these SDK improvements can help you make better technical decisions.

Looking to improve your Sitecore Content Hub implementation? Connect with Skybridge Infotech to explore smarter development approaches and customized Sitecore solutions.

Improved Scripting SDK Entity Copying in Sitecore: A Smarter Way to Manage Content Hub Entities