To allow nuts and washers to be correctly combined in reports, nuts and washers can now be separated within a bolt assembly in Template Editor.

In Template Editor templates, nuts and washers within a bolt assembly are no longer combined into one row. Previously, when a bolt assembly had different nuts and/or washers, the quantity of them was combined, but it was not possible to distinguish the sizes and standards of the nuts and washers. The result was that in the bolt inquiry report, washers were not combined.

Now, if nuts and washers are not the same in a bolt assembly, Template Editor is able to separate them in templates. You no longer need to use NUMBER 1 - NUMBER 3 in the row property rules for nuts and washers. This allows nuts and washers from multiple bolt groups to be correctly combined or separated. In the image below, you can see that washers are combined although they have different sizes.

To see this change in your own templates, you need to update the templates. The bolt inquiry report (TS_Report_Inquire_Bolt.rpt) already contains the fix.

This improvement was already introduced in Tekla Structures 2024 SP1.

The Template Library has been updated for Tekla Structures version 2025. The following improvements have been made:

• In Template Editor, define both Meaning and Unit for value fields if you want to avoid using a default unit for the meaning. Previously, the unit was not always correct. For example, at least in some cases, the Length meaning uses meters as the default unit.

  

• When sorting is used in a value field (Order is set to Ascending or Descending) and the When rows are combined setting is set to Sum values across all rows or Sum values within one row, the sort now uses combined values. Previously, the sort used uncombined values.

• When GetFieldFormula referred to a value field that had a combine action When rows are combined selected, it would return an unsummed value. This issue has now been fixed.
• In graphical templates, the Sum() and Count() functions now calculate column values only when used in table footers. Previously, for example Count() would always return the numbers of cells (aka rows) in the whole table, so all table footers would have the same count. For example, a 3x4 table, 3 columns and 4 rows, with first 2 columns with 4 cells and the last column with 3 cells, would previously have counted as 11 in all table footers. Now the first two table footers would have 4 and the last one 3.
• A formatted value always overrides a value field value, even when the value field data type is Number (formatted value is always a string).
• In some cases, when imperial units were used, the 0 value was shown incorrectly as 0.0. This issue has now been fixed.
• GUIDs are now sorted correctly.
• Negative numbers represented as strings are now sorted correctly.
• In graphical templates, if a value field content will actually fit inside value field boundaries, it is not cut even if the content is longer than the defined field length.
• In graphical templates, value field font auto-size (Font size change in Free attributes) now works more precisely. Previously, a bit too large font size could be selected.
• Value field formula resolving order is now correct and not mixed with the drawing order.

  The drawing order is the same as the order of the value fields in the content browser. The resolving order is determined by the formulas in the value fields. So a value field that refers to another value field (for example, with GetFieldFormula or CopyField) is always resolved after the value field it refers to.

• For the fvf function, the fifth parameter is now available also in drawing templates and custom components. If it is set to TRUE, empty entries from the read line of the file will be considered when the function gets resolved. If it is missing or set to FALSE, empty entries are removed.

  

  Below are several hypothetical examples that illustrate how the syntax in the fvf formula produces different results, including the use of a fifth parameter in the formula to produce empty columns.

  This example specifies an input file called sample.dat, with the line:

  A; B;; C; D

  In this case, the formula

  

  will return an empty string: ""

  As each separator in the above example is considered meaningful, the third column is an empty column between the first ';' and the first ' ' separators. So the column values in this case are:

  1: "A"

  2: " B"

  3: ""

  4: " C"

  5: " D"

  and

  
  

  will return: "C"

  A subsequent example would be when multiple separators are used in the input file, i.e. a mix of spaces and commas.

  A, B, C, D

  In this case, the formula:

  
  

  will return: "B"

  and

  
  

  will return an empty string: ""

  and

  
  

  will output: "C"

  and finally

  
  

  will output: "D"

  That is, when the last parameter is FALSE, consecutive separators are interpreted as one separator.

  TRUE = allow empty columns, thus consecutive separators are treated as unique separators.

  For more information about the fvf function, see fvf.