- Currently using MicroStation Update 12....testing MicroStation Update 17....
My question: When is the MicroStation (Power Platform) development team ever going to address a problem that has been around for years?
Print Styles are a great feature. I also like the Print Organizer tool.
However when using them to print a file with reference attachments (with clip boundary/masks setup) the pre-defined print fence parameters are not followed and do not find the defined fence boundary elements.
I found a few posts dating back 8 years where this was a known issue, and yet it has NOT been addressed up to MicroStation Update 17 version, which I just tested.
Can someone from Bentley explain why?
Why hasn't this issue be prioritized for repair? Our company cannot be to only one encountering this issue.
The company whose drafters I support (and inherited this mess from) have hundreds of drawings that utilize clip boundary/masks on "Title Block / border" reference files and when trying to automate printing using print styles and Print Organizer, we cannot make it work.
The additional problem is that previous CAD drafters decided to put multiple "Title Blocks / borders" into a single file (different configurations, scales, etc.) so the only way to display the one you want is to use a clip boundary/mask.
There is not enough time and money in the budget to split all of the borders into individual files, and then reattach the correct file back in to fix every file.
Does anyone have a work-around to get clip boundary/masked borders to print with pre-defined fences in Print Styles used in Print Organizer?
Same Question here as well.So when a .PSET it built with particular settings, design scripts, .ptlcfg and Fence Settings the files print perfectly. But take those same settings, jam them into a Workspace Print Style.dgnlib, and apply that Print Style to the .PSET, the print timesout with an error after 120 seconds, saying it cannot find the fence/boundary to plot to. Super frustrating.
Hi Bert,Thanks for posting in our MicroStation Product Communities Forum.I'm sorry to hear you are experiencing continued issues with these printing workflows.I'd be happy to work with you over a screen share meeting - maybe if we can take a look at this problem first-hand, then we can make recommendations/suggestions that could potentially lead to resolution.If you can submit a Support Case with us here, then just mention this forum thread and I'll assign myself to the ticket.-Jayson P.