יום שלישי 05 יוני 2012 01:05
I'm on my first serious implementation of MDS - going well so far.
I've created a new Explicit Hiearchy from scratch (in the Web UI). I'm now trying to populate the structure, so I created a few Consolidated Members - all good so far. Now I'm trying to search the Leaf Members under Unused to find the ones I want among the 4,000 odd entries. I got the tip (from another post in this forum) that wildcard searches need to follow the SQL LIKE syntax e.g. %Australia%.
But it seems the Hierarchy Search button does not search the "Unused" Leaf Members? I'm only getting results from the Members I've manually Cut and Pasted into my Hierarchy.
BTW I would prefer to use the richer Filter functionality from the central pane, but there doesnt seem any way to select and Cut the results to edit the Hierarchy?
יום שלישי 05 יוני 2012 13:35
It appears you are correct on all accounts. I tried the searching of unused in my 2012 environment and verified that unused members did not show up. Also, there is not much you can do from the central pane in terms of assigning members to parents. However, this probably explains why I did something specifically at my last client. I made the explicity hierarchies mandatory. I then created my own 'Unused' bucket where I would put members by default when they were created. this enabled the members to be found during search.
- סומן כתשובה על-ידי Mike Honey - Manga Solutions יום שלישי 05 יוני 2012 13:49
יום שלישי 05 יוני 2012 13:51
Thanks for confirming that. Its a bit disappointing - I might try raising something on Connect.
When you said "put members by default when they were created", do you mean created via the Staging process?
יום שלישי 05 יוני 2012 16:23
I do mean using the staging process. Essentially query the views for members who do not have a parent. stuff them in an 'Unused bucket' using the staging tables. If you are using 2012, its much easier given the introduction of entity based staging.
יום שלישי 05 יוני 2012 23:38
Thanks for confirming that. I've raised a Connect Bug for this because it seems to me a UI bug. Can anyone who reads this please vote:
In the meantime I guess I'll have to go down the staging workaround route. I imagine I'll then have to filter when using the output views to drop the members that remain "Unused"...