About Unresolved items

Help & Support
1

Suppose I have a folder in a collection, when I list the def value for an item object, obtained from a unresolved items collection, I get something like:

image
image1321×739 37.2 KB

(which assume is fine).

The issue seems to happen with nested items, which appear to strip all their parent names and just return:

image
image1342×720 37.5 KB

as if the item were sitting at the root of the path.

This happens with all items from an unresolved collection, and not only with virtual folders but also in regular filesystem ones.

So, my two questions are:

  • Is this behavior with all unresolved items is intentional or if something's going wrong here.

  • I assume that an item object from a non-virtual filesystem, retrieved from a regular Items collection, should be the same as its counterpart from the unresolved version. If that's correct, then why does the full path strip all its parent names?

2

Good day.
Any thoughts?

3

Fixed in the next beta.

(I suspect if you need one of the unresolved file lists, you may also need to call RemoveNested on it to get rid of the nested items, since they can't have collection paths due to not being in the collection. If so, that should already work and remove all the items with problems.)

1 Like