CartVisualCreate account

Does Editing a Leonardo Dataset Update an Element—and Which Model Can Use It?

No. Leonardo explicitly states that dataset changes do not update existing Elements. Train a new Element and verify its base-model compatibility and current legacy availability.

Published · By CartVisual editorial team

Dataset edits do not update an existing Element

Leonardo's Elements FAQ directly states that adding or removing images from a Dataset does not change Elements already trained from it. Training a new Element is required for those dataset changes to affect the trained artifact. This is an explicit provider rule, not an inference from a hypothetical failed generation. A merchant who changes bottle packaging photos but continues selecting the old Element is still using the old training artifact.

Track four independent states

Consider a fictional skincare bottle whose cap changes from silver to matte black. The proposed version register distinguishes image evidence, training, completed artifacts and generation eligibility.

RecordHypothetical stateWhat changesWhat does not follow
Dataset D1Old silver-cap imagesSource collection existsNo new training implied
Element E1Trained from D1, completedReusable trained artifactEditing D1 later does not update E1
Dataset D2Revised approved matte-cap imagesTraining inputs changedE1 remains unchanged
Training job T2Planned or running from D2New training processNot a usable completed Element yet
Element E2Only after T2 completesNew trained artifact to selectDoes not guarantee correct cap or lettering
Generation G2Eligible model plus E2Candidate image produced if supportedNot an approved product photograph

These identifiers are fictional bookkeeping examples. No training job was started.

Check whether training is currently an option

The provider places this documentation under advanced legacy features and describes Elements as usable with certain older models. Its default Element training base is Flux Dev; an Element trained on Flux Dev is not compatible with Flux Schnell. Other bases have their own compatibility restrictions. Before allocating work, confirm that the account still exposes the legacy training interface, that the intended generation model accepts custom Elements, and that a reusable trained appearance is necessary. Do not assume a newer Omni image-reference workflow accepts the same Element.

SymptomLikely decision boundaryNext action
Updated dataset, unchanged outputStill using E1Plan new training if justified
Training job still runningNo completed E2Wait for actual job completion before selecting it
E2 absent in selected generation modelModel compatibility or availabilityInspect training base and current model support
E2 selectable, cap still wrongImage fidelity, not version identityCompare with real SKU evidence; reject unsuitable output

Choose a proportionate repair

If only one campaign image needs a new cap, an approved photograph and manual composite may be more appropriate than training a reusable Element. If many concept images require the revised product appearance, assess a fresh dataset and compatible training route. The vendor training-policy guide addresses permissions and data use, not this version rule; model identity versus output differences explains another reason results may diverge. Record dataset snapshot, Element identity, training base, job completion, runtime model and physical-reference review before releasing any image.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Provider features and account access may change; all worked examples are hypothetical, with no actual generation, training, permission changes or publishing. Product identity and rights require independent verification.

Related decisions

Explore the AI product photography workflow