Hi all,
I am noticing that DGNs I am synchronizing in the iTwin Synchronizer portal for iModels are processing all Nested Referencing although all our files do not have Nesting enabled for all their references.
Since we are synchronizing container files that have live design models referenced in, nested references including IFCs and DWGs get included in processing as well as the mass of all files referenced in downstream, meaning 500+ files are included, eg.
Is this WAD? If so, this may cause issues for those of us wanting to use iTwin Services for progress reviews and team sharing.
Regards,
Mark
Hi Mark, not sure it is the situation here. However, yes normally references are being processed. However, if you want to EXCLUDE a reference you can turn off the display.As you are using the online portal, I will assume you are using the latest connector which is configured this way.Note if you have IFC's and DWG's referenced and running this through the InstantOn Portal you should ask for affinity to be enabled so you can ensure IFC / DWG are handled by the most appropriate conenctors. ie MS will handle IFC if you do not specific they should be handled by the IFC connector
I agree with Mark, it can be frustrating when the connection is defined using a container with multiple references and not always active. And if there is in addition a large .pod linked but not nested... :)
I appreciate, Glen that we can turn on & off display in Model, but maybe more convenient would be that option is available during setting up the connection.
Thanks
Doesn't work like that.
Turning off a reference does not exclude it. Especially when you have references that are not even visible within the reference list due to reference nesting levels...
2 years on and still having the same issues.