Microstation noob here again,
I have been trying for months to attach references using batch process and saving it with a relative path. I have only been able to get the reference attach keyin, RF, to work if I put in the full path to the drawings. This is not ideal since it takes more work and we really need the files to be saved relative for when we have to email the client the DGN files. I was able to follow an example where they were referencing a file only a folder up. But in my case the references can be buried in the same general folder but be inside a sub folder(s) within that one.
Like I said, I am very much an amateur and any help would be really appreciated. Even if its a link to help me better understand how Microstation Finds a relative file.
I am thinking you might find the following Wiki article of assistance in understanding reference file locations and attachments.
Understanding File Locations And Reference Attachments In MicroStation
RegardsAndrew BellTechnical SupportBentley Systems
could you possibly give us a few more details ? why is a batch process needed ? is there a reason you are looking to use the relative path option ? etc...
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Michael Drew said:This is not ideal since it takes more work and we really need the files to be saved relative for when we have to email the client the DGN files. I was able to follow an example where they were referencing a file only a folder up. But in my case the references can be buried in the same general folder but be inside a sub folder(s) within that one
when I send dgns to client I use the msnt utility Packager which harvests all ref files attached to selected dgns if you tell it to so you don't have to go find all the refs your self. packager puts all of the dgns and other harvested data including jpgs , imagery and a manifest of all the data etc into a .PZIP file ( which you can rename to plain zip later if you wish)
Also I adopted an acad user practice to have -XR- in the ref file name to denote it is an External Reference or Xref.. My clients appreciate this.. and don't bother to separate the drg files from the xrefs.... but I do here at our work we put all the ref files in there own sub folder but they still have -XR- in there file names...
FYI packager is a batch process in it self as all you do is tell it what files your dgns are and if you want the xrefs and imagery etc too... I use it a lot especially before revisioning so I have a full backup . pzip of everything including xrefs before I changed anything .. as all my xrefs are live in my drgs...
I don't worry about relative path much as the project configs and workspace configs set the paths to xrefs... but if you really have to have it I think its a variable... somebody else here will chime in on this... but if your just wanting it so you can share the data with clients then packager will do what ever you need...
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me
So we have a repeat client that comes to us for every remodel they do. We use almost all of the same sheets every single project. So to make us more efficient, I used batch process to setup the sheets since they never change. So it loads in the title block, existing and new plans and turns the correct levels on and off. The only variable is the project number. The reason for relative path is that our client requires us to have it setup like that. So when we send them the files at the end of the project, they don't have to reattach anything.
That sounds convenient for large projects, but our client is a little hard headed and doesn't like to change things up. They want all the files to just be relative so they don't have to worry about anything.