'AutoDesk Forge Viewer dbId / externalId change without interaction
We're having an intermittent issue that just started two weeks ago, where the externalId and dbId are being reassigned over the weekend to different objects without any user interaction (no new file upload or translation job occurred between Friday and Monday, but the objects were essentially given new dbIds and externalIds between viewing on Friday and Monday).
This first happened between 4/1/2022 and 4/4/2022. I thought it was our users that didn't follow the guidelines we implemented.
It happened again between 4/8/2022 and 4/11/2022 to a different autocad.
I'm wondering what causes the dbId & externalId to be assigned to specific objects when viewed in the autodesk viewer? I assumed that the only thing that would cause different dbIds or externalIds is the translation job. Is this an inaccurate understanding? Also, is there any type of audit history to see all occurrences of when an autocad file was uploaded/translated?
*Reference my original issue (still unresolved, I just implemented the workaround suggested): Autodesk Forge - Do any IDs persist when translating a new source file with minor changes?
Solution 1:[1]
Once an SVF (or an SVF2) output is generated, its dbIDs and externalIDs are baked and cannot change. If you're seeing the dbIDs changing, this could be happening because:
- The model is being re-translated (perhaps accidentally?)
- You are switching between SVF1 and SVF2 outputs of the same model
If you could share the URN of one of the models where you noticed this change, and a rough timeframe where this change occurred, we could check our logs to see whether the model has been re-translated.
Also, do you know whether you're loading SVF1 or SVF2 models?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Petr Broz |