Best Practice for replacing Repository Items
Posted: Tue Jan 16, 2018 9:07 am
Hi,
i'd like to know the best/least disruptive way to solve the following scenario:
We have a repository, with many rooted folders, and many items to each root. One of the Items now _functionally_ stays the same (i.e. a buttonpress will have the exact same effect) while _programmatically_ (and therefore in terms of its XPath) completely changing.
Repository before:
RootA
-------RootFolder1
----------------------RootFolder2
-------------------------------------Item1
-------------------------------------Item 2
Repository after:
RootA
-------RootFolderA1
----------------------RootFolderA2
-------------------------------------Item1
-------------------------------------Item 2(now defunct)
RootB
-------RootFolderB1
----------------------RootFolderB2
-------------------------------------Item 2
Two actions need to be taken, and i'd like to know, as stated, the best practice on achieving them:
1) Group Items 1 and 2 in the presence of tens of other subroots and items on all roots that will not be grouped accordingly. As i understand it, logical folders can only exist as subfolders to roots, and therefore, because there are other items (not drawn) that belong into other groups, can not be used to to group Item2 and Item1 after the change.
2) Replace Item2(old) by Item2(new) in every instance in- and out-solution, including code-mentions of it.
Both i can solve, but the solutions are rather long-winded and painful, and as i suspect this occurence might be rather common, i hope that there is some smooth solution, maybe even catching bothb at once?
i'd like to know the best/least disruptive way to solve the following scenario:
We have a repository, with many rooted folders, and many items to each root. One of the Items now _functionally_ stays the same (i.e. a buttonpress will have the exact same effect) while _programmatically_ (and therefore in terms of its XPath) completely changing.
Repository before:
RootA
-------RootFolder1
----------------------RootFolder2
-------------------------------------Item1
-------------------------------------Item 2
Repository after:
RootA
-------RootFolderA1
----------------------RootFolderA2
-------------------------------------Item1
-------------------------------------Item 2(now defunct)
RootB
-------RootFolderB1
----------------------RootFolderB2
-------------------------------------Item 2
Two actions need to be taken, and i'd like to know, as stated, the best practice on achieving them:
1) Group Items 1 and 2 in the presence of tens of other subroots and items on all roots that will not be grouped accordingly. As i understand it, logical folders can only exist as subfolders to roots, and therefore, because there are other items (not drawn) that belong into other groups, can not be used to to group Item2 and Item1 after the change.
2) Replace Item2(old) by Item2(new) in every instance in- and out-solution, including code-mentions of it.
Both i can solve, but the solutions are rather long-winded and painful, and as i suspect this occurence might be rather common, i hope that there is some smooth solution, maybe even catching bothb at once?