Hi Francesco, We will be doing additional testing on this specific behavior, but if you haven't already, please involve Synchro Support for this project-specific assistance. Going forward, I would advise not editing/creating additional 3D Objects User Fields, but use them for read-only purposes. It's ideal to use Resource User Fields to input or compute additional data, as Resource as an entity is local to SYNCHRO, whereas 3D Objects are imported. In iModel workflows, we may disable editing of 3D User Fields altogether. Hope this helps!
↧
