Profile Swap

Purpose and description

This application changes the profile name to its metric or imperial equivalent as provided in the profile catalog.

System requirements

Environments: Default
Languages: English

Installing Profile Swap

To install the extension:

1. Make sure Tekla Structures is closed.
2. Install msi package downloaded from Tekla Warehouse.
3. Reopen Tekla Structures once installation is complete and you will see:

(v21.0) A new toolbar icon which will launch the tool should now be visible.

Image

(v21.1 and newer) A new thumbnail under Ungrouped items or US Extensions in the Applications & components side pane will appear.

Image

Using Profile Swap

When this application starts it spends a few seconds caching the currently loaded catalog and the options are disabled until it has finished. The user can use the Selection Filter option to restrict items changed from either a set of selected items or all items in the model. The Profile Conversion Direction controls the direction of the swap for instance using the To Imperial switch on a metric model changes the “selected” part profiles to the values stored in the IMPERIAL_EQ_NAME attribute of each profile.

Image

Pressing F1 (Help) opens this page. Feedback on this tool can be given in the Tekla Discussion Forum. Pressing F3 opens the application log which can assist in trouble-shooting.

Additional information

• Some versions of Tekla Structures will not allow you to change the Profile to a value not in the Profile Catalog which means you can only swap in one direction – from equivalent to defined profile.
• The US environment profile catalogs include duplicate equivalent value listings for EDI nomenclature which this application filters automatically by ignoring profiles that contain “SCH” or both “HSS” and “X.” during the caching of the profile catalog.
• The US environment profile catalogs also includes historical profiles that have equivalent value listings that duplicate non-historical profiles thus the HISTORICAL profile attribute is checked and the historical profile is excluded from the caching of the profile catalog.
• If duplicates beyond the two situations describe above are found then the first profile and equivalent encountered during caching is cached and the others are ignored.