Node Converter Skipping a Generation in Parent Assignments

Summary:

All parents assigned by a subscription are skipping one generation, and assigning the source node's GRANDparent as the target node's parent value.

Content (please ensure you mask any confidential information):

In EDM, the Master (Universal) application, and the PBCS (Planning Modules) application, are each set up with an Account dimension; a run-of-the-mill subscription connects the two, with the PBCS Account being refreshed from the Master Account. For the CoreStats.Parent property, the node converter for the PBCS node type has the standard expression,

{
return sourceNode.parent.name
}

Yet, when the subscription actually runs, instead of returning the sourceNode.parent.name, it's returning the sourceNode.parent's parent, i.e. the source node's