Template Studio - Units per Page Limitations

Hi all, 

I am encountering some limitations for the units per page on Template Studio. In the template setup area, I understand that the plot area must be in a whole number of millimeters, however Template Studio also requires that scale be a whole number. Due to the conversion factors between millimeters and feet, it's more or less impossible to set a precise units per page. See screenshots below. 

Is there a way around this issue? If not, does Bentley intend to fix it? It's my understanding that this could easily be fixed by allowing decimal values for the scale. 

Thanks, 

Parents
  • Hi all, 

    This issue is unresolved. The official response is that the units per page is defined by the follow-on page, NOT the first page. Therefore in order to get perfect units per page on the first page, you would need to align the height (mm) ratio of your report body on the first page and follow-on page. 

    After experimenting with the numbers, I determined that 20 units for the first page with a 140 mm plot area, and 30 units for the follow-on page with a 210 mm plot area should work. Unfortunately it does not work because of an issue with the scale value that gets rounded when transferred between follow-on to first page.  

    On OpenGround Template Studio

    Set first page to 20 units per page, this is allowed because the scale is allowed to be a decimal here

     

    Follow-on page gets automatically set to 30.31 units per page because the scale is pulled from the first page settings THEN ROUNDED, then is used to determine the units per page on the follow on.

     

    I hit OK, then reopen template setup settings, now the first page units per page is no longer 20 because it uses the rounded scale value from the follow-on page. The follow on page settings did not change.

     

     

    On OpenGround Professional Quick Log Preview

    Attempted to change units per page on quick log to 30

     

     

    This also does not work because the scale is still transferred as a whole number to the first page, therefore the first page is still not 20 feet. I am unable to verify if the follow-on page is precisely 30-feet in this scenario because nowhere on the software does it tell me, and the scale is such a precise decimal that I can't measure it on bluebeam/PDF

    Out of curiosity, I made a spreadsheet that constrains scale to whole numbers and prints units per page in a table if and only if the units per page is also a whole number. This is what the table looks like.. so we're out of luck. 

  • We are unfortunately experiencing the same issue, and had opened a service ticket several months ago which still has not be resolved.  We had no issues (or at least we were not aware of any issues) using any template with the First Page - Follow-On button checked, until about three months ago.  After an update, every time we opened a template in Template Studio, the log became "squished" so that there was about 20 feet worth of log shown within 2 inches below the header, and the rest of the page was blank.  After another update, that issue was resolved but that is when we began noticing that the logs ended at the bottom of the page at uneven depths, such as 16.7 feet deep when the units-per-page was set to 20 feet.

    As you mentioned, we realized the depths shown on the logs were being controlled by settings for the Follow-On page.  Our solution was to turn off the Follow-on page, so that the depth of the log on a sheet could be controlled by the units-per-page setting.  This has been a very unpopular decision with our Project Managers as there is now a large header on top of every single page of the log.  A few of our Project Managers have requested that we export their project from OpenGround and import them into gINT so that they can produce logs for reports for upcoming submissions.

    Bentley:  This issue needs to be resolved ASAP, it is making those of us who have invested all of our time and energy into promoting OpenGround within our firm look foolish that we cannot output a log the way we used to.

  • Thanks for confirming mcotreu. Likewise I have had a support ticket up for this issue since 10/27/22, but regret submitting it as a low priority ticket. Bentley has replied to it with 'Open - Defect Filed'. 

  • Hi mcotreau & others,

    @Martyn Collis just confirmed that this issue is 'resolved' with the latest patch last week.

    I went through my templates and confirmed that it is resolved IF AND ONLY IF you set up your Depth Area for first page and follow-on pages to match the scale. For example,

    • if you want the first page to show 20-ft and the second page to show 30-ft, then
    • the first page Depth Area should be 140 mm, 150 mm, 160 mm, etc
    • the follow on page Depth Area should be 210 mm, 225 mm, 240 mm, etc, respectively

    In addition, this will only work if you use all of the space available. See example screenshots below. 

    This can be problematic as it locks you into specific header and footer heights in order to obtain the units per page you desire.

  •  

    FYI this bug still exists in quick logs even with a perfectly set up template units per page & depth area. 

    Quick Log

    Log Report

  • Hey, Bentley! Any chance you can change the units for reports to Imperial units, since that is what we use in the USA, which primarily functions in Imperial units? Metric is great, but the conversion from Imperial can get cumbersome when you are building a complex report.

Reply Children
No Data