CODEWITHSUNDEEP
autodesk-forgerevitforgeautodesk-model-derivative
Thomas Van Driessche
Thomas Van Driessche

Reputation: 85

Custom property (Identity Data) in Revit model got translated wrong

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

Upvotes: 4

Views: 504

Answers (3)

Nah
Nah

Reputation: 1

@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

Upvotes: 0

Alan Smith
Alan Smith

Reputation: 11

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

Upvotes: 0

Eason Kang
Eason Kang

Reputation: 7070

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.

Upvotes: 1

Related Questions