Hello,

BrowsePaths in TranslateBrowsePathsToNodeIds Service calls can start from any Node, not just the Root Node. That being said, the function for copying the BrowsePath of the selected Node to clipboard was not added to Browser with TranslateBrowsePathsToNodeIds Service in mind. Instead it is there to provide an alternative to copying BrowseName or NodeId in Attributes and References view to clipboard as BrowseNames don’t always uniquely identify Nodes and NodeIds can sometimes be rather undescriptive.

If we’re being pedantic, the correct form for a BrowsePath is the NodeId of the starting Node and a RelativePath consisting of an array of RelativePathElements which consist of information on the followed References (referenceTypeId, isInverse and includeSubtypes) and QualifiedName the target Node. For more information on RelativePaths, see https://reference.opcfoundation.org/v105/Core/docs/Part4/7.31/

This means that the BrowsePaths copied by Browser to clipboard are similar to BrowsePaths but not quite BrowsePaths as information on the References is omitted. In fact, the OPC UA Specification doesn’t define a String representation for BrowsePaths. So if the OPC Foundation’s .NET reference stack supports BrowsePaths in some String form, that form has been chosen for the implementation and is not defined in the OPC UA Specification.