Finding a situation where I reference a file from a far flung directory, select Save Relative Path and Live Nesting set to 1.
We have a directory structure, folder and file naming standard for the company. A lot of files are named TOPO or COMP, etc.
When the reference is attached with the nested reference files in tow, files with common names in the local directory are connected instead (again TOPO or COMP). Not the files attached and nested to the referenced file.
If there is no local file with the same name as a nested reference, e.g. UTILITY, that nested reference will show.
For every thing that gets fixed in the updates, like 4 things that work get broken. Where is the review in these releases?!
Stephen Kareiva said:I reference a file from a far flung directory
Stephen Kareiva said:When the reference is attached with the nested reference files in tow, files with common names in the local directory are displayed instead
You're saying that you have several files, albeit in different folders, with the same name?
Regards, Jon Summers LA Solutions
Jon Summers said:You're saying that you have several files, albeit in different folders, with the same name?
Yes.
As an example: I'm working in G:\Year\Job Number\SITE\SKETCH\BASE\COMP.dgn. In that \Base directory is a COMP and TOPO file.
I reference in a completed job sheet/file from someplace else: G:\Year\Job Number\SITE\SHEET\(02)SITE.dgn, with Save Relative Path checked and Live Nesting = 1
IF one of the reference files attached to G:\Year\Job Number\SITE\SHEET\(02)SITE.dgn is named TOPO or COMP, then the reference path in the tree points to the directory I'm in, not the directory the file should be coming from.
I'll attach some images here to try and illustrate. This is a confusing and frustrating thing to describe and deal with.
In a dgn file called COMP. Reference dialog with hierarchy and external reference file/path shown with full path saved. Selected reference #6, also called COMP.
When I select the settings of the nested reference comp, from a different directory, it shows me the local file/directory I'm working in. Because the files share the same name.
This is MicroStation not carrying the full path of the directory the nested reference is in, and is defaulting to the local directory.
Clear as mud?
The file you reference must have it's references attached with full path. If they are, you may want to file a Service Ticket. Could be JAB (just another bug) #92,648.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
I think I get what you're saying. If the references attached to the file I'm referencing and live nesting have save full path, that should carry over.
I will give that a test.
But I will say this was never a problem before having U16.2 installed. This is 'fixing' something that was never broken, IMHO.
Stephen Kareiva said:This is 'fixing' something that was never broken, IMHO.
Be prepared for Bentley to tell you that's an 'Enhancement'