Is it possible to edit multiple item types at once?
I have multiple .cel files with multiple models within each that all have a common item type "manufacturer". I would like to edit some of the "manufacturer" for some .cel files, without changing all of them by changing it in the dgnlib file. Is there an easier way to do this rather than going into each model in each .cel file and clicking on each item to then edit its item type info?
Which version (e.g. v10.x.y.z) of MicroStation are you using?
It's not exactly clear what you want to do with your Item Type. An Item Type is defined to have one or more properties. It's each property that is assigned user data...
manufacturer
Rachel Dubriwny said:I have multiple .cel files with multiple models within each that all have a common item type "manufacturer". I would like to edit some of the "manufacturer" for some .cel files, without changing all of them by changing it in the dgnlib file. Is there an easier way
Either MicroStation's batch processor tool or a custom app. It rather depends on your answer to my questions above.
Regards, Jon Summers LA Solutions
Thanks for the reply, I am using CE U13.1.
What I'm looking for is the ability to open a cel file and edit an item type property that is attached to multiple models within that cel file.
Rachel Dubriwny said:What I'm looking for is the ability to open a cel file and edit an item type property that is attached to multiple models
Is it the DGN model that's tagged with the Item Type or one or more DGN elements within that model that are tagged with the Item Type?
Probably a task for VBA. Do you have anyone available who is familiar with MicroStation VBA?
The DGN elements that are tagged with the item type. We do have somebody familiar with VBA, but too bad this isn't already an option in MicroStation. Maybe we can request Bentley add tools to better handle editing/updating/changing item type data with an interface similar to the reporting tools.
Rachel Dubriwny said:too bad this isn't already an option in MicroStation
Item Types are new with MicroStation CONNECT. More people should start to use them: so congratulations on being amongst the vanguard! I think Item Types are terrific: they provide much of the functionality of MicroStation tags but with a number of improvements. Tags provides an 'update' tool, similar to that which you propose but limited to the active model. MicroStation Reports and Tables are a consequence of Item Types.
Your proposal is to have an Item Type update tool that updates Item Type properties in the active model, or in all models in the active DGN file. Post that as an Idea.
Hi Rachel,
Rachel Dubriwny said:The DGN elements that are tagged with the item type.
There is a contradiction in your information. Because it's important to distinguish whether bulk edit is possible or not, can you please clarify how ItemType is attached to a cell?
Alternatively, you can share a cell lbirary example (e.g. a copy of it with 3 or 4 cells inside).
Rachel Dubriwny said:but too bad this isn't already an option in MicroStation
If ItemType(s) is attached correctly (to model, not to element), the bulk edit of more models together is possible. But to edit ItemTypes attached to elements existing in different models is not possible and it woul break how MicroStation works.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan,
Thanks for the reply. I wasn't entirely sure of the difference there, so I attached an example of some bearings we tagged with item type information called "OP Items" which consists of "Manufacturer", "Part Number", and "Description".
Dodge_Bearing_Example.dgn
Rachel Dubriwny said:I attached an example of some bearings
The design file looks a bit weird. I do not quite understand wheather it's your cell library or some output where cells were used.
The file is not .cel (which is just naming, so not mandatory requirement), but every model, which I expected is a cell definition, contains only the cell, which makes no sense. After placing such model (as a cell) into model, double nested cell will be created.
Rachel Dubriwny said:I wasn't entirely sure of the difference there
The difference is whether ItemType is attached to an element (wrong in this case) or to the cell model itself using "Attach ItemType to model" (preferred).
Rachel Dubriwny said:we tagged with item type information
I recommend to use "tagged with ItemTypes", despite of it would make sense, but it creates a mental link to "tags", which is another element type ;-)
Because of the cells nested one into another (every model contains another cell) and ItemType is attached to the cell, not to model, you have to open every model and find ItemType instance to edit them.
That was supposed to be a .cel file, I made a copy of it so I could keep only 3 or 4 cells and forgot to change it back to a cel file.
We attached an ItemType to the element so that if the model and cell were dropped we wouldn't lose the ItemType, but to be honest we weren't aware that you could attach an ItemType to a model.
Rachel Dubriwny said:That was supposed to be a .cel file
If it's cell library, just with .dgn extension, it's created incorrectly in my opinion, because model (which represents individual cell) is not expected to contain one element only, which is again cell. It makes no sense and creates the problem of "cell inside cell" when placed to design file.
Rachel Dubriwny said:We attached an ItemType to the element so that if the model and cell were dropped we wouldn't lose the ItemType
Whereas I understand such requirement in general, I disagree with it.
When ItemType is relevant to a cell as a representation of some object, when the cell is dropped, it's not the object anymore. So to what element the ItemType should be attached to?
Another situation is when ItemTyp contains information to a specific part of the cell, e.g. when there will be an engine cell (with ItemType attached to model with information about manufacturer, engine type etc.) and there will be another ItemType attached to let's say engine axis with specific information about this part. But it's not the discussed case I guess.
Regards,