You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have items with the same path in the system (it is not forbidden and sometime it happens). I've noticed that command get-childitem -recurse returns only only first item of those who have the same path.
I'm trying to use Powershell to repair such items so I would expect commands to return the additonal items in some way.
I'll find the items using object properties so there is no problem with it. But the queestion is: it this a feature of commands to treat the item path as unique? If yes and that will be left for better performance I would be happy if there would be some switch to turn that assumption off for example "-nonUniquePaths" param.
The text was updated successfully, but these errors were encountered:
I assume the Get-ChildItem does this when you use -Query param with Sitecore Query? otherwise it seemed to be working fine for me. Anyway Use -AmbiguousPaths parameter on Get-Item and Get-ChildItem for the provider to resolve such conflict and push all of the ambiguously named item to the pipeline
I have items with the same path in the system (it is not forbidden and sometime it happens). I've noticed that command get-childitem -recurse returns only only first item of those who have the same path.
I'm trying to use Powershell to repair such items so I would expect commands to return the additonal items in some way.
I'll find the items using object properties so there is no problem with it. But the queestion is: it this a feature of commands to treat the item path as unique? If yes and that will be left for better performance I would be happy if there would be some switch to turn that assumption off for example "-nonUniquePaths" param.
The text was updated successfully, but these errors were encountered: