I have a lot of item type data that is going to be project (workset) specific. Instead of manually entering in the data in the properties dialogue of Microstation, I would like to enter that information in excel, then have each of those item types lookup that data from the excel file based on the first column manual input (similar to articles below). I know that I can use the ITEMTYPE_LOOKUP configuration variable to accomplish this as shown in those articles below, but those articles talk about putting the excel lookup file in the same spot as the DGNLIB file, and adding the ITEMTYPE_LOOKUP variable to the Organization Standards configuration file. However, since the data I want to lookup is going to be project specific (vary from project to project) I need to put it at the project level. So a few questions I have about this:
Item Types - Populating Items using Lookup Tables
Expression to Derive Data from Lookup Tables
Please mention the CE version you are using. The first three points are possible till U15. Point 4 will be possible in U16.
I am using U16. The thing I am unsure about is is the configuration setup. This is from the link in my first post:
To make lookup table(s) available to Item Types the configuration variable ITEMTYPE_LOOKUP must be defined and set to include the path and file names of any Excel files containing lookup tables:
ITEMTYPE_LOOKUP = $(_USTN_ORGANIZATION)Dgnlib/DEC_ItemTypesLookup.xlsx
This should be added to the organization Standards configuration file, in this example: D:\DEC_Configuration\Organization\01_DEC_Standards.cfg
I am unsure where to put the ITEMTYPE_LOOKUP variable in the workset cfg file (maybe it doesn't matter?), and am also not sure what the bold filepath would be in order to map to the workset folder. It would need to be something relative since we would put it in the workset template we use to create our worksets.
OpenBridge Modeler - 10.10.00.85Microstation - 10.16.02.34
Comprehensive 3 Day OpenBridge Modeler Training
Steven Tissier said:I am unsure where to put the ITEMTYPE_LOOKUP variable in the workset cfg file (maybe it doesn't matter?)
It does not matter, typically custom modifications are added to the end of the configuration files, after standard content generated by MicroStation.
Moreover, this definition overwrite existing one (because = is used), which makes sense, because there should be only one xlsx file.
Steven Tissier said:and am also not sure what the bold filepath would be in order to map to the workset folder.
It probably should be something like
Be aware the variables beginning with _ are hidden in MicroStation GUI by default, but any variable value can be checked using expand echo key-in, e.g.
expand echo $(_USTN_WORKSETROOT)
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Thanks for explaining Jan. I gave what you suggested a shot and unfortunately did not have success. I tried adding that variable line to the end of the workset cfg file, no success. I then tried adding it to the end of my organization cfg file as those articles suggested, no success. See info below. In my case, my workset name is "delete1" for testing purposes.
Variable I am adding to the cfg files
ITEMTYPE_LOOKUP = $(_USTN_WORKSETROOT)$(_USTN_WORKSETSTANDARDSDIRNAME)StructuresTables/StandardStructuresTables.xlsx
File path of my lookup table file
Item Type Definition
Steven Tissier said:and unfortunately did not have success.
What your "no success" means?
Steven Tissier said:See info below.
What MicroStation tells about ITEMTYPE_LOOKUP variable (in variables list or when "expand echo $(ITEMTYPE_LOOKUP)" is used)?
BTW What MicroStation version do you use? Your footnote tells it's U14, but Mangesh mentioned the functionality is supported from U15.