Overview
SpecLink Cloud received a list of important improvements and fixes on January 12, 2026.
Improvements
The following improvements were made to SpecLink Cloud:
- Import from Word: Add Ability to Import Only Legacy Coded Units of Measurement
- Import from Word: Some Reference Standards Articles and Paragraphs are Importing at Incorrect Level
- Import from Word: Text Coded for Global Terms Conversion Should Not Convert to Reference Standard on Import
Import from Word: Add Ability to Import Only Legacy Coded Units of Measurement
Previously, users needed to “pre-code” any recognized units of measure ("UOM") such as inch or foot, prior to importing into SpecLink Cloud. The import converted such UOM’s to the correct enhanced text type. In order to support legacy “pre-coding” in use by some customers, a new option labeled “Convert Only Legacy Coded UOM Types” has been added to the Import dialog.
When selecting this option:
- Any potential UOM types that exist outside of legacy coding will import as plain text
- Only legacy coded UOM types will be converted to enhanced text
- No auto-calculation is done on the UOM types
If a user selects the 1st or 2nd option for UOM import, and the document contains legacy coded UOMs, all recognized UOM types (whether legacy coded or not) will import as enhanced text and be subject to auto calculation of values.
Non-legacy vs. legacy coded sample:
- Non-legacy coded: 1 inch (25.4 mm)
- Legacy coded: {{1 inch (25 mm)}}
Import from Word: Some Reference Standards Articles and Paragraphs are Importing at Incorrect Level
On Import from Word, when users elect to have reference standards converted to the enhanced text type of Reference Standards (RS), the RS article and subparagraphs should import into the correct paragraph level in SpecLink. An improvement has been made to ensure that such paragraphs do not import at incorrect paragraph levels.
Import from Word: Text Coded for Global Terms Conversion Should Not Convert to Reference Standard on Import
On Import from Word, users can mark text (pre-coding) that should convert to the Global Term type of enhanced text. An improvement to the import process will now ensure that pre-coded Global Term types do not get mistaken for reference standards on import.
Fixes
There are several fixes addressed in SpecLink Cloud v2026.0.2:
- Sections Created with New Section from Template Cannot Be Imported Into Other Projects
- Users Are Unable to Edit Comments
- Import from Word: Some Word Docs that use the CMT Style for Project Notes Fail on Import
- Import from Word: Some Reference Standards Are Being Imported with Extra Symbols
- Various Code and Data Fixes Applied
Sections Created with New Section from Template Cannot Be Imported Into Other Projects
Users can import sections from one project to another. Some users experienced an issue where a user created a new section from the master template in SpecLink, but when attempting to import the section into another project it was not listed in the import dialog. This issue has been corrected.
Users Are Unable to Edit Comments
Some users with the proper access rights to edit comments found that they could not edit comments. This issue has been corrected.
Import from Word: Some Word Docs that use the CMT Style for Project Notes Fail on Import
When a Word document using the CMT style for notes is then on imported into SpecLink, the text should convert to a project note. In some cases the note was not converting correctly or the document import was failing. Both issues have been corrected.
Import from Word: Some Reference Standards Are Being Imported with Extra Symbols
Some users have reported that extra symbols such as parentheses have been added to text on Import from Word. The affected area was Reference Standards. This has been corrected.
Various Code and Data Fixes Applied
Various code and data fixes that are project- or customer-specific have been applied since the previous SpecLink Cloud release.
Comments
0 comments
Article is closed for comments.