我正在努力创建一个基于Forge查看器的Web系统，该系统与客户的BIM360环境链接在一起。对于模型数据提取部分，我参考了下面的示例。
（1）
（2）
但是，我意识到Forge查看器和示例代码的dbids不同。这是因为SVF版本差异（即SVF1与SVF2）的原因吗？如果是，有什么建议解决吗？
此外，当我尝试使用第二个示例代码（即forgexls.js示例）提取模型数据时，某些模型未正确处理。调用“ PrepareSable”功能后未处理该代码。似乎有执行“ GetMetadata”，“ GethierArchy”和“ GetProperties”功能的问题。你能告诉我一些可能的原因吗？
I'm working on creating a forge viewer-based web system linking with my client's BIM360 environment. For the model data extraction part, I refered to the examples below.
(1) https://github.com/xiaodongliang/forgeviewer_embed_in_powerbi_report/tree/master/forge-model-properties-excel
(2) https://github.com/Autodesk-Forge/bim360appstore-model.derivative-nodejs-xls.exporter
However, I realized that the dbIds from the Forge Viewer and the sample codes are different. Is this the reason because of the SVF version discrepancies (i.e., SVF1 vs. SVF2)? If yes, any suggestion to resolve it?
Moreover, some models were not correctly processed when I tried to extract model data using the second example code (i.e., ForgeXLS.js example). The code was not processed after calling "prepareTables" function. It seems like it has issues to conduct "getMetadata", "getHierarchy", and "getProperties" functions. Could you let me know some possible reasons?
发布评论
评论（1）
SVF版本差异
是的，SVF的dbId在模型的所有版本中并不是一致的。 SVF2 dbId 在不同版本中可以相同，但理想的是利用对象的外部 id。即使用外部 id 从模型的第一个版本构建地图。当您想使用 dbId 时，请通过外部 id 搜索 dbId
使用第二个示例代码（即 ForgeXLS.js 示例）提取模型数据
我相信这只是因为型号版本太大。您可以尝试在获取属性时添加标头 forceget
https:// /forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-properties-GET/
SVF version discrepancies
yes, the dbId of SVF is not consistent in all versions of the model. SVF2 dbId can be same in different versions, but the ideal is to take advantage of external id of the object. i.e. build a map from the first version of the model with external id. When you want to use dbId, search the dbId by external id
extract model data using the second example code (i.e., ForgeXLS.js example)
I'd believe it is just because the metadata / properties of the model version sis too large. you may try to add the header forceget when fetching the properties
https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-properties-GET/