How to use templates created with newer versions

Tekla Structures
2021
Tekla Structures
2020
Tekla Structures
2019i
Tekla Structures
2019
Tekla Structures
2018i
Tekla Structures
2018
Tekla Structures
2022
Tekla Structures
2023
Tekla Structures
2024
Tekla Structures
edit templates
drawing template
modifying template
Environment
Not environment-specific

If you've created a template that you want to use in older versions as well, you may notice that the template is not appearing in the drawing. And if you try to open the template with older version's Template editor, you may get error messages such as below:

 

Image
TemplateEditor.png

    

Image
TemplateUnknownAttribute.png


To work around these errors, you can simply delete the properties that were added in newer Template editor versions, by opening the file in Notepad and erasing the lines containing the attributes. Obviously these settings are then not applied in the converted template.

In case of the second picture, the error message points out the lines that you need to remove in the file, but if not, here is a list of added features that are present in template files created with versions after Tekla Structures 2017:

Back to top

2017i

Organize data in columns

You can now organize data in columns that start from top left, top right, bottom left or bottom right. These settings can be modified in the Row Properties dialog box. To use columns, select the Use columns check box, and then define the order:

 

Image
GUID-88E3C03B-1592-4A88-996E-FAA1F754E6D7-publishing.png


This feature is written on template attribute fillstartfrom.

Support for multiple lines of values

You can now enter multiple lines of values in the Name field in the Value Field Properties dialog box. You also need to enter the number of lines. The lines will be reserved even if you do not enter multiple lines.

 

Image
GUID-F52F76C2-1CB5-410F-AE57-6B3396A62ED2-publishing.png


To get the end result to go to multiple lines press Enter at the end of the row.
"Profile:" + "\n"
+ GetValue("PROFILE")


If you do not press Enter , and if the value does not fit in one value field cell due to length limitations, the value continues to the next line if you have set the line count to more than 1 and the row height allows that.
This property is written in valuefield attribute maxnumoflines.

Back to top

2018

Use page headers/footers as column headers/footers

You can now use page headers as column headers in template output. To do this, select the new page header component option Use columns. Page footers can also be used as column footers.

 

Image
GUID-3B00D6DB-C0C2-440F-9096-7921CBB2D8E0-publishing.png


These properties are written in pageheader and pagefooter attribute usecolumns.

Back to top

2020

Template object colors can now be overridden in row rules by defining an override parameter for the Output() function. For more information, see “Overriding template object colors with row rules in Template” in Template Editor 4.0 User's Guide.

The following rule overrides the colors when the LENGTH attribute is longer than 1000. Value fields are orange, text objects are yellow and the drawing color is blue (i.e. lines are blue).

 

Image
GUID-5458228F-43BB-4F1E-8C3C-6906B89BC2F1-publishing.png


Choose from the 14 colors that you can use in Template Editor. Valid color names are black, white, red, green, blue, cyan, yellow, magenta, brown, darkgreen, navyblue, greenblue, orange and gray. The color names are case-insensitive.
For this feature, template attribute colors is added in the .tpl files.

Multiline value field should have its content attached to the top, so the data is filled from top to bottom. Default will remain from bottom so as not to break old behavior.
This property is written in valuefield attribute aligncontenttotop

Back to top

2021

In Graphical Field Properties, you can now select whether to always output a graphical field (Always visible) or output the field based on a rule defined for the field (Visible). The result of the rule needs to be either true or false.

Image
Graphical Field Properties


These properties are written in graphicalfield attributes isalwaysvisible and visibilityrule.

Back to top
Was this helpful?