Skip to main content

Overview

You don’t have to move a whole pipeline. Single-entity sync copies just one entity’s mapping configuration into another pipeline — useful when you want a surgical change and you know the entity isn’t entangled with others.
Single-entity sync uses the same target picker, the same required reason, and the same publish checkbox as a whole-pipeline sync. It’s the pipeline dialog narrowed to one entity.
Required permissions
  • Data Pipelines: Access
  • Manage Silver Entities or Manage Gold Entities, for the entity’s layer: Update
  • Manage Production Pipelines or Manage Dev Pipelines: Update on the target pipeline
On access-controlled entities, the entity row menu also needs Manage Access Control Entity Rules Update. See roles and permissions and permission dependencies.

Syncing an Entity

1

Open the Pipeline and Layer

Open the pipeline you’re syncing from, then open a layer — for example Silver.
2

Open the Entity Actions Menu

Click the three-dot menu (⋮) on the entity row.
3

Select Sync

Click Sync to open the dialog.
4

Pick the Target Pipeline

Choose where the entity is going. The source pipeline is never offered as its own target.
5

Read the Warning

Like a pipeline sync, an entity sync always overwrites. The dialog warns:
“Overwrite is destructive. Mappings on this entity in the target pipeline will be replaced with the source’s.”
6

Write a Reason

Reason for Sync is required. It’s saved to the entity’s change history in the target.
7

Decide About Publishing

The publish checkbox is off by default. Until the target is published, it keeps running the mappings it had before the sync — see Publishing After a Sync.
8

Apply the Sync

Click Sync. The result reports the outcome for this entity, and the target’s change history records a new version.

What Single-Entity Sync Can and Can’t Do

  • It never deletes the entity itself. It replaces that entity’s fields and sources. Other entities in the target are untouched.
  • Entities can depend on each other. If the entity you’re syncing is referenced by others through relationships, syncing it alone can leave those references pointing at something that changed. Sync does not check this at the entity scope.
  • Only the entity you picked moves. Nothing else in the target is added, updated, or removed, and metrics are not copied — use a pipeline sync for those.
When in Doubt, Sync the Whole PipelineWhole-pipeline sync moves related entities together, so relationships stay consistent. Reach for single-entity sync when you’re confident about the entity’s isolation.

After Syncing an Entity

  1. Check the entities that reference it. Open the target pipeline and review any entity with a relationship to the one you just synced.
  2. Publish the target if you didn’t tick the checkbox, otherwise the target keeps running its previous configuration.
  3. Review the change history on the entity in the target to confirm the new version landed with your reason attached.

Best Practices

Diff the Pipeline FirstA pipeline Diff is read-only and shows exactly what differs, entity by entity. Use it before syncing into production — see Comparing Pipelines.

Troubleshooting

Problem: After syncing one entity, entities that reference it behave unexpectedly. Solution:
  • Single-entity sync doesn’t check dependent entities. Open each entity that references the synced one and verify its relationships and sources.
  • If several entities are entangled, re-sync at the pipeline scope so they move together.

The Target Still Runs the Old Mappings

Problem: The sync succeeded but reports and scheduled runs still reflect the old configuration. Solution: The target hasn’t been published. See Publishing After a Sync.

Sync Overview

What Sync changes and where to find it

Syncing Pipelines

Move every entity at once

Comparing Pipelines

See the differences before syncing

Entity Lineage

See which source columns feed each entity field