Any chance you would consider having the process that "unwraps" the prefetch paths automatically recognize when part of a tree has been added twice and automatically resolve it?

Or throw a runtime error?

Is it even possible to detect this?

We run into it a lot.

It's hard to detect it. The added treenodes which are added multiple times are legit for the code which fetches the data. To detect if a node is already added, I've to compare the nodes but as these are created and filled with new instances, I'm not sure if that will work. I'll see if I can add some test for this.

In 1.0.2004.2 (next build of the beta), a check has been build in, which throws an exception in Add() if you add an element which defines a fetch for a property, start entity, end entity which is already added to that path object. (sub paths are different path objects).

Otis wrote:

In 1.0.2004.2 (next build of the beta), a check has been build in, which throws an exception in Add() if you add an element which defines a fetch for a property, start entity, end entity which is already added to that path object. (sub paths are different path objects).

Nice! Thanks Frans!