Add an ability to "Replace a file" from the asset's properties page

We would also like this behavior implemented in AEM Assets. Versioning is a routine activity for our content managers, and needed to retitle files for a new version to be created in Assets is unintuitive for them and also tedious 

@alext- hello! Do you have any news about this Idea?=)

@jasonwinn not yet, this Idea is under "Investigating" status.

Has this been implemented or how can I request this functionality on my instance? We require the same functionality to Replace or Create a New Version of an asset with out having to upload with the same name. 

@alext- hey! Sorry for the late response! Just in case, this idea is still actual for us 🙂

I provided with an example, that's why my second image has another name "new car". But it's totally fine, if the functionality will work with the same image's name only. For example, replace an image "car" to the another image with "car" name is ok for us.

The main thing, what we ask about - Content managers need an ability to "Replace a file" from the asset's properties.

Hi @polinaab can you clarify why the asset uses different name and whether you want to maintain the file with a new name? 

@polinaab thanks for explaining. It really seems to be something similar but different 🙂

@alexbethke hello!

Sorry, I didn't get your proposal. It sounds like a different behavior from what I described in the task's description.

We asked for a function that will allow Editor to replace the current asset's file to another file from the asset's properties.

Business case: 

There is a landing page on /en locale where the file is attached and available for the end-user to read (e.g. https://www.veeam.com/wp-ransomware-trends-executive-summary-europe.html ).

Editor needs to create a language copy of the Page and the related asset's file, so that the landing page is displayed on /de locale with the translated file to /de (e.g. https://www.veeam.com/de/wp-ransomware-trends-executive-summary-europe.html ).

In reality, we have the following Use-case how Content Managers work with assets:

> Content Manager creates an asset's language copy, then "Reveal in Asset" (Out of the box solution that leads to the Asset's editor), then goes to the asset's properties and need to Replace the "original" file by "translated version" of the file, having stored it on local computer with different name.

We have a finding here with this function and I'd like to know if this works as designed...

Following scenario:

• the editor uploads a file with the same name as an existing (published) file and then clicks on 'Replace'
• then moves the new file to have a new name
• then publishes the new file

In that moment both files are published and the editor has no possibility to get rid of the old published file as there is no connection between old file and new file.

@alext- hi! Sure.

In reality, we have the following Use-case how Content Managers work with assets:

> Content manager creates an asset's language copy, then "Reveal in Asset", then goes to the asset's properties and need to Replace the "original" file by "translated version" of the file, having stored it on local computer with different name.

So, whenever a Content Manager needs to replace an asset or create a version, he/she has a direct link to this asset.

But, currently, it's impossible to update the file from the asset's properties and they need to get back to the assets-listing, search their file though the omni-search and replace it from the listing (that's quite inconvenient).

As a result, we have 2 use-cases how a content manage needs to update the asset: from the omni-search and from the asset's properties.

@polinaab could you elaborate on why two distinct options for creating a version and replacing are needed?