First of all hello to everyone! I've been wondering if there is a possibility to group references? In my line of work I can have up to 50 different references attached to the design file and it could be quite useful for me to make a group for different types of references. (Have soilmaps be a group, infra and pipelines another, location maps another etc.) Do you have any tips on how to manage my references better? I'm using microstation v8i ss4 currently.
cheers,
KPA
Kalle Partinen said:I've been wondering if there is a possibility to group references?
Have you considered nested reference attachments? Create a blank DGN file having a model named soilmaps. Attach your soil maps DGN models to that model. Next, attach the soilmaps model to your main DGN model: you now have a 'group' of soil maps attachments.
Regards, Jon Summers LA Solutions
Thanks for the quick reply. I have and I do use nesting but many cases it would be easier to manage one file than have five different ones.. Also I feel if you use live nesting things can get lost quite easily. I'm looking for a quicker solution if there is one.
You can place each reference with a description, then you can order them by this, and they stay in order by your description, say: Structure, MEP, etc.
Some years ago I've place this idead to go even futher with colors to help us visualize a lot more quicker.
This should help us to change order in dialog and see a lot faster what we need:
https://communities.bentley.com/products/microstation/i/user_interface/references-by-subject-with-colors-in-reference-menu
José
Could you give a few more details on what you mean by "manage" the references ? How would grouping them help you in your workflow, etc... ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
It may be useful for you to provide an example design and reference file or even screen capture to explain what it is you are currently performing and how you would want to change this workflow. Nested references may be a method, as Jon Summers suggests, but it could just be how you have managed these files and the complexity of the levels in each particular file.
RegardsAndrew BellTechnical SupportBentley Systems