You might have already seen this when you update metadata, the shared members won’t move like the regular members.
Let’s look at Vision Application in PBCS. You can see the shared hierarchy and the regular one.
Now I’m going to create a metadata load file which will move 110 under 100 to 403. Also what I want to do is to move the shared member 110 under Resources VP to Sales VP. Let’s see what happens.
Let’s import this file and see what happens
There it did move the regular member not the shared, what it did was to add another shared member. So how can be solve this, all you’ve to do is remind yourself that PBCS is Planning (atleast at heart), all the laws of physics apply here too. There are some things that you feel that everyone knows about it and when I received a call asking how can it be done and I decided to blog about it 🙂
You can create an extra column in the metadata file called Operation (aha, now you see that you can use all OutlineLine.cmd options) and delete the shared hierarchy.
Here is how my metadata file looks.
Here is the hierarchy after load.
Keep in mind that there is no option or there is no DeleteSharedDescendants.cmd available for PBCS, so if you’ve Stored members and you use Delete Descendants those will be deleted and you’ll lose data. So use it with caution