Upgrade notes

Changes that need your attention when upgrading. Unlike Release highlights, which lists new features, this page covers behaviour changes where doing nothing may leave you with a problem.

Each note says how to tell whether you are affected.

OPC UA browse paths during a mixed-version upgrade

Applies to: platform 2.0 and later, when browsing an OPC UA server.

What changed

The browse path that identifies a node in the OPC UA address space now encodes the / and % characters inside each node name. Before this, a node whose name contained a / was read as if it were two nested levels, so the browse tree showed a level that does not exist on the server.

For every node name that does not contain / or %, the path is unchanged. If no name in your address space uses those characters, nothing changes for you.

What needs action

The edge runtime and the IDE must be upgraded together. Both sides of this change shipped in platform 2.0.

If a device still runs a pre-2.0 runtime while your IDE is on 2.0 or later, a node name containing / still shows one extra tree level. The tree remains usable — the nodes are reachable and are not duplicated — but the extra level is a symptom of the version difference, not a new fault.

For support

A spurious tree level under a /-bearing node name is version skew. Check the runtime version on the device before investigating it as a defect.

What to do

Upgrade the device runtime to platform 2.0 or later. The extra level disappears once both sides match.

OPC UA tag names recorded before platform 2.0

Applies to: OPC UA client mappings created before platform 2.0.

Affected mappings must be recreated by hand

There is no automatic migration, and none is planned. Nothing in the product marks which projects are affected, so check them yourself using the test below.

What changed

Mappings created before platform 2.0 stored the tag names in an internal formatting rather than as the server reports them. Values already saved are left exactly as they are — upgrading does not rewrite them.

How to tell whether you are affected

Open the OPC UA client subscription and look at the Tag Browser and Tag Display columns of the mapping grid:

Column	A value recorded before 2.0 looks like	A correct value looks like
Tag Browser	2:Temperature — a number and a colon in front	Temperature
Tag Display	Temperature (en-US) — a language code in brackets	Temperature

If you see either pattern, that mapping was recorded before the fix.

What to do

Recreate the affected mappings: delete the affected rows and add them again by browsing to the same nodes, which records the names as the server reports them. Mappings added after the upgrade are correct from the start.