There has been a lot of pollution on our server with ChangeRequest being shared back and forth between views and sometimes in fdirfferent folders of the same view.
I am trying to do a cleanup routine that will identify all the CR shares starting from the CRs in a given view.
Using the viewmembercollection of the view I can easily get all the CRs.
Then from each CR I can get the Parent and Child Shares.
However, I know that there are many more complex shares involved (ex: Root was shared to two other views, then a share was created in a target view back to the root view, etc...you get the picture).
Is there a way to get the entire Share Tree of a CR or do I have to run a complex traverse algorithm that will cover all possible directions?