Is there a way to define an expression that would read the DGN name along with a specific TAG in the DGN file. We want to name the the PDF file as follows.
DGNfilename-Revision#.pdf
The revision # would be specified in a TAG within each DGN.
Thanks in a
There is not... we currently have an enhancement filed for this:
86263-User would like to create an output PDF file name containing a revision number from Print Organizer based off of a MicroStation tag and/or configuration variable. If you send me an private message with your contact information, I will open a SR and attach to this enhancement for tracking.
Answer Verified By: JuanCar02
Hi,
it's possible to create a new symbol provider with own expressions (of course it requires some .NET coding). I guess it should be possible to create expression working with a specific tag in a design file. What I am not sure about is if expressions used during the printing have the same level of access to the design file as when used directly from MicroStation GUI.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
The primary obstacle is the process problem. Print Organizer has a dual-process architecture: each DGN is loaded in a separate, non-graphics worker process, while the primary process runs the status window and orchestrates the overall print job. The primary process is also responsible for deriving the print output file names. The only information available to it is what's stored in the print definition, and whatever can be taken from the interactive session -- where not only is the active DGN not the same as the one being printed, but the user and project workspaces could be different.
Macros can be used to read custom data from tag elements when the DGN is loaded (in the worker process), and set variables that can be referenced in expressions, but without an easy way to get that data back to the primary process where the expression is evaluated, that approach is impossible (or at least very difficult).
In the next release, Print Organizer will evaluate the print output file name expression in the worker process, not the primary process, allowing custom data from tags or item types to be more easily used along with the existing print set and print definition properties.
.