0

I configured our viewer to use SVF2 format yesterday as per these instructions: https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/notes/

I have observed that when selecting a node in the model, we get different Id's from SVF vs SVF2.

I usually pull the metadata and properties using the following GET calls:

https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-GET/ https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-properties-GET/

It has been mentioned here that the SVF2 Id's are computed differently, is there a way to get the Id's of a SVF2 model without loading it into the viewer first?

Phil
  • 1,609
  • 12
  • 24

1 Answers1

1

Apologizing for any inconvenience had caused. This is a known issue that our engineering team is evaluating, and we're hearing customers' voices. Could you consider providing your use case to SVF2 objectId with more details and the paint points you might have if the objectId between GET properties and viewer are inconsistent? Currently, there are two workflows that we're interested in as the below. Could you kindly point out which one your workflow is?

  • Normal workflow (GET properties -> Viewer), e.g., get dbIds(objectIds) by filtering properties with some conditions with GET properties, then partial load objects with LMV.
  • Reverse workflow (Viewer -> GET properties), e.g., select some objects in LMV, then post back to GET properties to get specific properties to store in DB.

Note. If the information you want to share cannot be posted publicly, please send it to forge[DOT]help[AT]autodesk[DOT]com instead. Meanwhile, please remove any confidential information and personal data from anything you want to share with us before sending it out.

Update 2021/07/21

Just to let future devs know that SVF2 is now GA, article is here.

Phil
  • 1,609
  • 12
  • 24
Eason Kang
  • 6,155
  • 1
  • 7
  • 24
  • Hi Eason, we upload the model and translate, I then use one of the metadata/property endpoints to map the nodeId's to rows in our database. In the model viewer, we can select a node by selecting a row in our own table OR we can click a node in the model to filter our data table. Does that answer your question? I email support yesterday :) – Phil Feb 26 '21 at 10:03
  • We have reverted back to using SVF format in the viewer for now. – Phil Feb 26 '21 at 10:04
  • Btw. here's a temporary workaround until the SVF1/SVF2 dbid mapping is provided by the Model Derivative service: https://forge.autodesk.com/blog/temporary-workaround-mapping-between-svf1-and-svf2-ids. – Petr Broz Jun 03 '21 at 06:34
  • @PetrBroz I missed this comment and haven't tried it, as SVF2 is now GA i'll give it a try again. – Phil Jul 21 '21 at 09:02