CartVisual
Sign inCreate account

Product videos / PRACTICAL ANSWER

Why Does Editing an Essential Property Change Only One Product-Ad Version While Another Still Uses the Original Value?

After Effects Essential Properties can inherit values from a source composition or override them on an individual nested instance. When one version differs, inspect whether its property is still linked. Changing a source value does not necessarily replace a deliberate instance override.

01 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

Find the source property and the nested instances

Open the primary composition used by the advertisement template and identify the property exposed through Essential Graphics. It might control a headline, color, position, slider or another supported property.

Next inspect every nested instance of that composition in the parent advertisement. Adobe documents linked Essential Properties that follow the source and unlinked properties that override source values or keyframes for one instance.

The important distinction is not whether the layers share a name. It is whether the exposed property on a particular instance has been modified.

After Effects provides visual indicators for modified Essential Properties, including a bold property name and enabled Pull/Push controls. Record those indicators rather than assuming the instance is linked because it originated from the same source composition.

02 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

Distinguish Pull, Push and local editing

Adobe's documented Pull operation discards the local Essential Property modification and restores its link to the source. Push applies the modified value, keyframes or expression back to the source property. These actions have very different scopes.

Use Pull when an instance should once again follow the approved source. Use Push only when the instance's change is intended to become the shared source value. A Push can affect other linked instances.

For expressions, inspect the actual source expression and any instance-level override. Do not assume that changing an expression in one nested placement automatically rewrites the source expression.

Before applying either action, save a working project copy and list which advertisement variants should change. A color correction intended for one SKU must not silently become a shared template default.

03 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

Hypothetical two-bottle advertisement

Hypothetical illustration—not an executed After Effects project: a fictional template exposes a label-color property. Two nested instances display bottle advertisements A and B.

Instance A remains linked to the source's charcoal color. Instance B has a local amber override for a different approved campaign treatment.

The designer changes the source color to navy. Under Adobe's documented property model, A should follow the source update while B retains its local override until the relationship is changed.

The editor inspects B's modified-property indicator. If navy is required for both versions, Pull is the candidate action for B. If amber should become the source default, Push is a different, broader decision requiring review of the other linked instances.

These are hypothetical states, not observed software results or evidence that amber is an approved product color.

04 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

Review shared changes and intentional exceptions

Build a property map containing the source composition, exposed control, each nested instance, current value and intended inheritance state. Then test the change on a copy.

Inspect all variants after any Pull or Push. A template may contain several Essential Properties, and relinking a whole group can have a broader effect than relinking one selected property.

Check the rendered advertisement, not just the property panel. A correct numeric value can still produce an inappropriate product label or low-contrast title in a particular layout.

Keep deliberate local exceptions documented. Reusability does not require every product-ad version to share every value. It requires a predictable distinction between common template changes and approved per-instance differences.

The next action is to choose the intended scope, then apply the documented link operation only to the affected property or group.

05 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Hypothetical propertySource valueInstance stateExpected response to source updateDecision
Label color — ACharcoal changing to navyLinkedFollows navy sourceRetain linkage
Label color — BCharcoal changing to navyLocal amber overrideRetains amber overridePreserve or Pull after approval
Proposed amber shared defaultWould require source changePush from B consideredOther linked instances may changeReview scope before Push

Download the editable CSV worksheet

06 / WHY DOES EDITING AN ESSENTIAL PROPERTY CHANGE ONLY ONE PRODUCT-AD VERSION WHILE ANOTHER STILL USES THE ORIGINAL VALUE?

What the references establish

Published by CartVisualPublished Updated Evidence and editorial policy
SOURCES & SCOPE

Sources and further reading

Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.

QUESTIONS, ANSWERED

Frequently asked questions

Does editing the source always update every Essential Property instance?

No. A modified Essential Property can be unlinked from its source and retain a local override.

What is the difference between Pull and Push?

Pull discards the local override and restores source linkage. Push applies the instance's modified value or expression to the source, potentially affecting other linked instances.

PREPARE ASSETS FOR YOUR NEXT STEP

Create supporting product assets in CartVisual.

Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.

Create account and open this workspace Check pricing and credits

Start with free concept and copy planning after sign-in. Image and video generation require available credits; review the quote before starting.

Already have an account? Open the workspace.