Upload a revision
without a duplicate.
The fixed file was saved under a new name, so uploading it would leave two assets in the library: the old one with the feedback, and the fix with none.
By the end, the revision is the newest version of the asset it replaces, the old version keeps its comments, and the library has one card.
Before you start
- The asset the revision replaces is already in your workspace’s Assets.
- The revised file hasn’t been uploaded yet, or its upload hasn’t been used anywhere.
Watch the walkthrough
Here's how to upload a revised file as a new version of the asset it replaces, so your library keeps one asset with its history instead of a duplicate.
Jordan asked for lighter pink bands and a five hundred milliliter bottle on this spring label. The fix was saved as a new file, under a different name.
On the Upload page, select Choose files and pick the revised file. Then select Upload 1 file.
When processing finishes, an offer appears if the upload closely matches an asset in your library. Here it reads: Looks like a new version of Harbor and Pine spring label, and it shows how similar the two images are.
Add as new version puts the upload into that asset's history. Add as new variant keeps it next to the original as a separate variant. And Keep separate leaves both assets as they are, and hides the suggestion.
Select Add as new version. The matched variant, Original, is already chosen: the upload becomes its newest version and the current one. Confirm with Add as new version of Original.
The upload row now says the file was added as a new version, with a link to the asset.
Open the asset. In Files and versions, Original now has two versions, and V2, the revision, is current.
V1 is still here, with Jordan's comment on it. Select it to see the old label, so the feedback and the fix stay side by side.
Back in Assets, there is one card for the label, showing the fixed version, and no duplicate to clean up.
The offer appears only for a new upload nobody has used yet: no comments, shares, projects, or reviews, and a single version. Tags and field values on the upload are not kept. If there's no offer, add the version from the asset's Files and versions tab.
Upload the revision, wait for the offer, and choose Add as new version. You keep one asset, with every version and its comments.
Search across all videos and guides.
One asset with its history, not two cards.
Jordan asked for lighter pink bands and a 500 ml bottle on the Harbor & Pine spring label. The fix was saved as a new file under a different name, so a plain upload would leave the old label and the fix side by side in Assets.
You’ll upload the revised file and, from the upload results, add it to the asset it replaces as a new version. The old version and its comments stay on the asset. Sign in to YetOnePro and open your workspace to follow along.
- 01
Upload the revised file
Open Assets and select Upload at the top right. On the Upload page, select Choose files, pick the revised file, then select Upload 1 file.
- 02
Wait for the offer
When processing finishes, an offer appears in the upload results if the upload closely matches an asset in your library. Here it reads Looks like a new version of Harbor & Pine spring label.png, with both images and how similar they are, for example 90.6% similar · matches its Original.
- 03
Choose what to do with the upload
Add as new version puts the upload into that asset’s history. Add as new variant keeps it next to the original as a separate variant, under a variant name you give it. Keep separate leaves both assets as they are and hides the suggestion.
For a revision of the same file, choose Add as new version.
- 04
Add it as a new version
The Add as a new version dialog opens. Under Add to which variant, the variant the upload matched is already chosen and marked Matched, here Original. It becomes the newest version and the current one of that variant.
Select Add as new version of Original. The upload row now reads Added to Harbor & Pine spring label.png as a new version of Original., with a link to open the asset.
Tags and fields. Tags and field values set on the upload aren’t kept; the asset keeps its own. If the upload has any, the offer says which won’t be kept. - 05
Check Files & versions
Open the asset from the link and select the Files & versions tab. Original now has two versions, and V2, the revision, is Current.
- 06
The old version keeps its comments
Select V1 to see the old label. It’s still there with Jordan’s comment, so the feedback and the fix stay side by side.
- 07
One card in Assets
Back in Assets, there’s one card for the label, showing the fixed version, and no duplicate to clean up.
No offer? It appears only for an upload nobody has used yet: no comments, shares, projects or reviews, and a single version. Otherwise, open the asset and add the file from Files & versions › Add file; see version history.
Check the result
- The upload row says the file was added as a new version, with a link to the asset.
- Files & versions shows the revision as the current version, and the old version with its comments.
- Assets shows one card for the asset, and no separate card for the upload.
If it didn’t work
No offer appears after the upload.
The offer appears only when the upload closely matches an asset in your library and nobody has used the upload yet: no comments, shares, projects or reviews, and a single version. Otherwise, open the asset and add the file from Files & versions › Add file.
Will the tags and field values I set on the upload carry over?
No. Tags and field values on the upload are not kept; the asset keeps its own. When the upload has any, the offer says which won’t be kept.