I am trying to link data such as manufacturer, part number, description, and notes to a cell. I assigned properties to the cell within the .cel file, then in the dgnlib file referenced those properties to give the same output. Then in a test file I placed the cell and tried to create a report on the properties from the dgnlib file. I can only get 2 of the 4 properties to show when reporting. The 2 that will not show are expressions that are dependent on a true/false property that can be changed by the user in the test file. Does this create limitations for reporting those properties?
1 of the properties that does show also is an expression, but is just a GetItemDifferentLibrary() command. Ive found that the other property will show if I insert a value in the default value, but if I use an expression, like 2+"2" it will not show in the report. However, it will still show a value in the properties window.
I included screenshots of one of the properties that will not show in the report, but will show the correct values in the properties window. I also attached the test file.
Which version (e.g. v10.x.y.z) of MicroStation are you using? This stuff (use of an Expression in an Item Type property value) is new to CONNECT Update 12. Not many people have tried this technology. But I can repeat what you see: the properties that are defined with an Expression show the correct value when inspected using the right-click Edit Item tool, but those values are not visible in a Report.
Regards, Jon Summers LA Solutions
Thank you for the quick response. I am technically using OBD U5, but I understand this includes MicroStation U12. Given this is likely a MicroStation or power platform issue, I chose to put it in the MicroStation forum.
I have gone through your "test.dgn" file and I observed that in *SYE Bearing* item type, PartNumber expression is not using *this.Bore* and thus not executed correctly at report side.I have adjusted your dgn with correct expression. Hopefully, it works for you.
BTW, we are developing Expression builder which will help to give property suggestions while typing expression itself.
Answer Verified By: Rachel Dubriwny
Thank you for the help, everything is working as expected now. When can we expect to see the expression builder?
We are actively developing this area and expect several improvements over the next couple of Updates. So more in U13 and even more in U14. We will do a detailed blog on it soon!