4

We are experiencing troubles when using the model derivative API to translate and extract properties from a Revit Model.

enter image description here enter image description here

As the screenshot implies, we have a custom property under Identity Data. But after translation its under Mark (the property on top of it). It's a model created in Revit 2018.

Is this a bug?

kind regards

Thomas Van Driessche
  • 85
  • 6

3 Answers3

1

This issue has been logged as RVTLMV-4 in our internal case system to our engineering team to allocate time to investigate what happened yesterday and they're working on it. We will get back to you A.S.A.P. once there is any update. Apologizing for any inconvenience had caused to you.

Eason Kang
  • 6,155
  • 1
  • 7
  • 24
  • Is there any news around resolving the bug? – Thomas Van Driessche Aug 16 '18 at 09:14
  • Unfortunately, no... Just hang on, let me check with them, will get back here A.S.A.P. – Eason Kang Aug 16 '18 at 09:30
  • Hi, a fresh update for you. Our engineering team has confirmed that it's a problem here, and planned to fix it. There is a great possibility that the fix would be available soon, but I cannot guarantee until it's available in the final release. – Eason Kang Aug 17 '18 at 17:06
  • @ThomasVanDriessche Please delete the old translation and submit a new job, I have confirmed that the fix of `RVTLMV-4` has been released now. – Eason Kang Sep 04 '18 at 04:11
0

I am seeing this issue too - custom properties appear to be coming through with "Cost" as the PropertyName. The ModelDerivative translation process seems to be the source of the bug. Happens on Revit 2018 or Revit 2019 model.

Is there any chance this issue can be escalated?

Our (live) Forge application relies on custom properties being correctly named and this current API release has broken our application when new models are uploaded.

Image of Model Derivative JSON

Image of Properties in Revit

Alan Smith
  • 11
  • 2
0

@Eason Kang: FYI I met this issue too. However, this issue happened when the translated field was not in the top of the Properties list. When this field was in the top, translation succeeded.

Hope this could give more information to your team.

I attached the image as below. First screenshot, it translated correctly. The 3 following screenshots, it translated wrong

Nah
  • 1
  • 3