Printing Scenario: Adding a file to print organizer that has multiple borders in one model of one file. (i.e. for this example, let's use 100 borders referenced into one model in one file.) When I add this file to Print Organizer, and select a Print Style, everything loads OK. It locates the borders, and adds one entry per border located in the file. When I print this file, it will print sheets 1 through 100, in order, with no duplicates.
The issue occurs if I make changes to any of the following settings in Print Organizer after the pset file is created: Bentley print driver, windows printer, or print style. This will result in Print Organizer printing sheet number 1, 100 times, instead of printing sheets 1 through 100. Depending on what has changed, Print Organizer may also override the scales and paper sizes.
This causes issues when multiple people are using the same pset file, and someone wishes to change the printer, etc. I do have a workaround (create a pset file for individual printers, PDF's, and styles, which isn't ideal because every pset will have to managed individually and opens the potential for someone to miss a sheet or two), however, I can't tell you how many calls I get about this problem and someone has just printed 100 of the same sheets to a printer!
I am running Microstation v8i SS2, this issue has been present in SS1 and v8i. I tried searching the message boards and didn't find anything, perhaps due to the weakness of the search engine... which is a topic for another day...
I'd greatly appreciate any input on this issue, thanks in advance!
Check out this thread
communities.bentley.com/.../140690.aspx
I've had the same issue and that is the only reason I would like some functionality of Batch Plot to stay in the new releases of USTN.
Microstation CONNECT 10.17.00.209
ORD CONNECT 2021 R1 10.10.1.3
Microstation v8i SS 10 08.11.09.919
Power InRoads v8i 08.11.09.615
ProjectWise 10.0.3.453
Thanks for the link to the thread. All of my styles are setup to locate my print border, they define a pltcfg driver, but do NOT define a printer. This allows the style to utilize the user's default printer. After reading the 140690 thread, I can now understand why changing the pltcfg would cause this, since my pltcfg's contain a print style definition. The explanation given makes sense, however it is not 100% accurate. In the scenario where a user wishes to print to a printer other than their default printer, they use the File/Printer Setup (as suggested in the 140690 thread), and change their printer. This alone is enough to cause the issue described in my original post. Personally, this is not how I would expect the application to respond (neither do any of my co-workers, and others on this forum). By changing the printer, you are not applying a new style. I believe the problem exists, because in the File/Printer Setup dialog, you are able to change the pltcfg and the printer. If you change one or the other, or both, it must reload both into the settings and cause the print settings and border definitions to be lost.
We need the flexibility to print to different printers without creating an entire new pset for every printer. Ideally we would have one pset file, and could EASILY switch to different printers or to a PDF file. There are many issues with maintaining multiple psets for one project.
I agree with you. That is one of my biggest gripes about the program. I like PO but I still like Batch Print because we utilize the method of 1 file with many borders. When a borders are added or deleted you need to delete all of the sheets in the set and re-add everything. The solution of switching to separate sheet models is painful at best and very cumbersome in my opinion.
Perhaps Bentley could help encourage the use of sheet models by adding a tool/option to PO. Maybe something that would create a sheet model for each print in your pset?
Rod WingSenior Systems Analyst
Maybe your pset file is just that, a DGN file full of sheet models. Either way, we need the ability to create a master print set file AND have control of where to send the plot, without a bunch of workarounds and creating multiple print sets.