--- title: How Does AVAIL Handle Changes in RVT Container Files? description: What to expect when re-harvesting content after Revit container file changes --- [Skip to content](https://helpcenter.getavail.com/how-avail-harvest-handles-changes-in-rvt-container-files#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 for Revit](https://helpcenter.getavail.com/avail-for-revit?hsLang=en) 3. [AVAIL for Revit: Frequently Asked Questions](https://helpcenter.getavail.com/avail-for-revit?hsLang=en#avail-for-revit-frequently-asked-questions) # How Does AVAIL Handle Changes in RVT Container Files? ## What to expect when re-harvesting content after Revit container file changes **AVAIL for Revit**, AVAIL's add-in for Revit, has functionality called **Harvest** that makes Revit container file elements accessible through AVAIL, for easy search and re-use. But what should you expect to happen when re-harvesting edited Revit content from container files, after you make changes to the container file itself, like doing a ***save-as*** with a new name, or upgrading the container file? **Answers are here!**  ### **New Harvest** (AVAIL for Revit 5.5.2 and newer): 1. When Revit **content name** is changed in the Revit container file and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** (element ID is unchanged) 2. When the **Revit project name** is changed in the Revit container file and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** - The distribution location network path is changed *(because the project name is part of Harvest's distribution path),* but the harvested content in AVAIL channels is automatically re-pathed. More about this is [here](https://helpcenter.getavail.com/understanding-how-avail-handles-content-re-pathing-in-3-different-scenarios?hsLang=en). 3. When an **RVT container file name** **is changed via "save as"** and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** - A workshared cloud model in ACC Docs or BIM 360 will be seen by Harvest as a different file if the user makes a local copy using "Save As" or opens it as detached. **However:** - If you choose the **same output location** as the original container file, **the harvested output will update the existing content in that location.** - If you choose a new location, you will get 2 sets of harvested content: the original set, and the set from the new container model. 4. **Revit RVT file version upgrade**: when the Revit container file is upgraded to a new version and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** - If harvested to a different network folder, new content is created, and the original content remains. This allows for new versions. **Note:** The table below is another way of presenting this information, **with some additional detail.** ![Harvest Container File Changes](https://helpcenter.getavail.com/hs-fs/hubfs/Harvest%20Container%20File%20Changes.png?width=670&height=647&name=Harvest%20Container%20File%20Changes.png) ### **Old Harvest:** (Harvest 2.4.5 and earlier) 1. When **Revit content name** is changed in the Revit container file and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** (element ID is unchanged) 2. When the Revit project name is changed in the Revit container file and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** - The distribution location network path is changed (because the project name is part of Harvest's distribution path), but the harvested content in AVAIL channels is automatically re-pathed. More about this is here. 3. When an **RVT container file name is changed via "save as"** and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.** - If the distribution location is different, then the harvested content is different, because In the old Harvest, the new RVT with a new name would have to be re-indexed to AVAIL to Harvest again, creating a new container file. 4. When an **RVT container file is upgraded to a new Revit version** and content is re-Harvested: - **Content is maintained as the same content if harvested to the same network folder.**   Please see additional important information about Harvest workflow here: - [How to Run Harvest in Revit](https://helpcenter.getavail.com/avail-for-revit-harvest?hsLang=en) - [How AVAIL handles content re-pathing in 3 different scenarios](https://helpcenter.getavail.com/understanding-how-avail-handles-content-re-pathing-in-3-different-scenarios?hsLang=en)   [![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=)