Frequently Asked Questions
      Back to home
      1. Help Center
      2. AVAIL Harvest
      3. Frequently Asked Questions

      How AVAIL Harvest handles 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.
      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.

      Container File Does Harvest see the container file as the same? If re-Harvesting to original distribution location on network If re-Harvesting to new distribution location on network If re-Harvesting to new distribution location on network and publishing to new channel
      Container file in original location YES Harvested content in Channel is updated Harvested content in Channel is updated and points to new location Harvested content in Channel is updated and points to new location. The content will also be added to the new channel.
      Container file copied to new location YES Harvested content in Channel is updated Harvested content in Channel is updated and points to new location Harvested content in Channel is updated and points to new location. The content will also be added to the new channel.
      Container file copied using "Save As" YES Harvested content in Channel is updated Harvested content in Channel is updated and points to new location Harvested content in Channel is updated and points to new location. The content will also be added to the new channel.
      Container file in ACC Docs opened as "Detached" or "Save As" NO Harvested content in Channel is updated New copy of harvested content is created in new location, the original content remains in the Channel in the original location. New copy of harvested content is created in new location and in new channel, the original content remains in the original location and original channel.
      Container file upgraded to new Revit version and saved NO* Harvested content in Channel is updated New copy of harvested content is created in new location, the original content remains in the Channel in the original location. New copy of harvested content is created in new location and in new channel, the original content remains in the original location and original channel.
      Content name changes in container file YES Harvested content in Channel is updated Harvested content in Channel is updated and points to new location Harvested content in Channel is updated and points to new location. The content will also be added to the new channel.
      Revit Project name changes in container file YES Harvested content in Channel is updated Harvested content in Channel is updated and points to new location Harvested content in Channel is updated and points to new location. The content will also be added to the new channel.
               
      *The file is seen as the same, but Harvest also uses Revit version to distinguish between container files.  Therefore, you can upgrade a container file, save it, and maintain multiple, separate Revit versions of Harvested content in different locations.

      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: