---
title: "Best Practices: 3 Solutions to Rename a File without Breaking Filter Links"
description: Customer question about 'Display This', renaming and Tags associated with older versions.
---

[Skip to content](https://helpcenter.getavail.com/tags-renaming-moving-and-other-issues#main-content)

English

Show submenu for translations

[More support](https://helpcenter.getavail.com/kb-tickets/new?hsLang=en)

[![AVAIL](https://helpcenter.getavail.com/hs-fs/hubfs/AVAIL-logo_email-header_00a1a3.png?width=200&height=37&name=AVAIL-logo_email-header_00a1a3.png)](https://helpcenter.getavail.com/?hsLang=en)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [More support](https://helpcenter.getavail.com/kb-tickets/new)
- [GO TO GETAVAIL.COM](https://getavail.com/)

[GO TO GETAVAIL.COM](https://getavail.com/?hsLang=en)

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Help Center](https://helpcenter.getavail.com/?hsLang=en)
2. [AVAIL Publisher 101](https://helpcenter.getavail.com/avail-publisher-101?hsLang=en)
3. [Publisher Best Practices & FAQs](https://helpcenter.getavail.com/avail-publisher-101?hsLang=en#publisher-best-practices-faqs)

# Best Practices: 3 Solutions to Rename a File without Breaking Filter Links

## Customer question about 'Display This', renaming and Tags associated with older versions.

### Customer Story:

*"I made Revit Project a central file so that multiple BIM people could update it. I spent a lot of time adding dozens of filters (Display This) to the file. Then someone asked me to rename the container file.  To rename a central file in Revit, you have to open the file detached and save as. I figured this would break the filters associated with the channel, and it definitely did. This will cost me two hours of work.  Is there a way to associate or export/import filters from one file to the next? Or, is there a way to safely rename a file without breaking any links to filters?"*

---

### **SCENARIO 1:**  

If the **file name and/or path changes AND the hash stays the same**, then when you re-index, all the tags will remain (because the **hash** did not change) and a new UUID is created.

**CHANGES:**

FILENAME ~ Changed

LOCATION ~ Changed

HASH ID ~ Same

**RESULTS:**

UUID ~ New

METADATA ~ Retain current keys/tags

---

### **SCENARIO 2:  **

If the **file name and path remains the same AND the hash changes**, then when you re-index, any new tags will be added to the current tags and the UUID remains the same.

**CHANGES:**

FILENAME ~ Same

LOCATION ~ Same

HASH ID ~ Changed

**RESULTS:**

UUID ~ Same

METADATA ~ Adds any new tags and retains current keys/tags

---

### **SCENARIO 3:**  

If **either the path or file name changes AND the hash changes**, then when you re-index, a new UUID is created.     

**CHANGES:**

FILENAME ~Changed

LOCATION ~ Changed

HASH ID ~ Changed

**RESULTS:**

UUID ~ New

METADATA ~ Current Keys/Tags are not retained unless matches existing HASH

---

### Conclusion

The keywords here are **'rename the container file'**, which changes the HASH ID and denotes that the file name changed.  Therefore, AVAIL treats this as new content.  Here are three scenarios I drew up for this user.

I bet that **SCENARIO 3** matches this situation - AVAIL probably saw a new file name along with a new hash, therefore, it is considered a new piece of content. 

If the user had indexed this file with the new hash, **then** updated the file name, their filters would have been fine. If you are going to change the filename in the future, make sure the hash is updated in the system by re-indexing first **before** updating the filename.  

[![AVAIL](https://helpcenter.getavail.com/hs-fs/hubfs/AVAIL-logo_email-header_00a1a3.png?width=140&height=26&name=AVAIL-logo_email-header_00a1a3.png "AVAIL")](http://getavail.com?hsLang=en)

Help Center

Copyright © 2025, getavail.com

![](https://segment.prod.bidr.io/associate-segment?buzz_key=brandgen&segment_key=brandgen-364&value=)