0

I am using Forge's Webhook API to manage the files that are uploaded to our BIM360 Projects. Is there a way to look up the version of the RVT file (for example, if is a Revit 2022 file or a 2018)?

Yue Hua Zhou Ding
  • 3
  • 2
  • Also check the answer on how to [Reliably Determine Revit Version of BIM 360 Project](https://stackoverflow.com/questions/63135095/reliably-determine-revit-version-of-bim-360-project). – Jeremy Tammik Feb 02 '22 at 08:52

3 Answers3

0

As soon as you have downloaded the RVT project file, you can determine the Revit file version last used to save it using the various following methods in chronological order:

Jeremy Tammik
  • 7,333
  • 2
  • 12
  • 17
  • Sorry, but I think I wasn't clear on the question. I was looking for a way to get the version of the RVT file without having to download the file again (as it is not feasible due to the size of the files). For example, is there an endpoint of any Forge API to obtain that information from the RVT file once it is already uploaded in BIM360? – Yue Hua Zhou Ding Nov 24 '21 at 23:22
  • ... checking with the devteam for you... – Jeremy Tammik Nov 27 '21 at 09:46
  • A set of new endpoints that include this functionality is in the works. – Jeremy Tammik Nov 29 '21 at 18:40
0

You can check the Revit version used to save the file by downloading just a few bytes of it, not the whole RVT file: Check the version of a Revit file hosted on the cloud.

Jeremy Tammik
  • 7,333
  • 2
  • 12
  • 17
0

The development ticket RVTLMV-2277 is now in production.

You can view the version inside the manifest; I just did a quick test:

"Document Information": {
     "RVTVersion": "2017",

Addendum:

Some additional notes on the blog post:

  • The information is not always in the first 10kb of the file; it could be anywhere. You can dissect the file format and find it though through repeated downloading of different bytes from the file. The amount downloaded and therefore time to calculate the Revit version can vary a lot.
  • The encoding for the text information isn’t always UTF-16 BE (Big Endian). The bits in the file may line up so that you must use UTF-16 LE.
  • Sometimes the file offered by the Forge API is not the direct .rvt file but a zip file with the .rvt file in it. In these cases, you will need to dissect the zip format to get to the correct .rvt file underneath.
Jeremy Tammik
  • 7,333
  • 2
  • 12
  • 17