Skip to content

Missing parent-child references when importing nodes #3068

@ArzerIFW

Description

@ArzerIFW

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

When importing nodes from a NodeSet2.xml nodeset and adding those nodes to the server using AddPredefinedNode(SystemContext, node) in the custom nodemanager, the parent-child references are missing. As a result methods such as node.GetChildren() are not working.

Right now I can use a workaround with currentNode?.GetReferences(nodeManager?.SystemContext, references) and filter for the expected children manually.

Expected Behavior

The parent-child references should be present when importing nodesets and adding predefined nodes.

Steps To Reproduce

No response

Environment

- OS: Windows 10, Windows 11
- Environment: Visual Studio Code 1.99.3
- Runtime: NET9.0
- Nuget Version: 1.5.375.457
- Component:
- Server: -
- Client: -

Anything else?

I use the CustomNodeManager2 class with:


nodeSet.Import(SystemContext, predefinedNodes);

foreach (var node in predefinedNodes)
  {
      AddPredefinedNode(SystemContext, node);
  }
AddReverseReferences(externalReferences);

Is this behavior expected?

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions