Skip to Content

In EPM Add-in ver 26/27 for .NET 4.0+, can we get the old find / search member result back?

It's driving us crazy. The new EPM Add-in versions, SP26 & SP27 (all patches of both in the .NET 4.0+ world) for Win10 and Office 2013/2016 have devolved in the member search department.

Scenario: You're in EPM Add-in in Excel. You open up any dimension to search for a member, then you find the result, and it's all alone - completely out of its surrounding context (and I don't mean EPM Context). Sure, you can look at its properties to find its parent, but you can't see its siblings or the hierarchical flow with any antecedents; you can't see its milieu and heritage.

Then, when you close out of the search results, you're back to seeing the entire hierarchy or wherever you may have last been! It doesn't leave you at the location of the member you searched for, which would be a helpful solution to the above problem.

It's REALLY annoying, and we'd very much like it back to being able to search for a member and then see the result in its surroundings -- or if that's not possible to be taken to its surroundings after you close the search result window.

Does anyone else relate to this or are we in a vacuum? I couldn't find any other comments or discussion on this anywhere. Is there a setting to tweak or a workaround we can do (you know, beyond downgrading several SP versions and possibly even an OS, that is -- downgrading when upgrades continuously occur isn't a solution)? Gah!

capture1.jpg (73.2 kB)
capture2.jpg (97.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 11, 2017 at 07:56 AM

    Hi Susan,

    You are not alone, but looks like it was a decision in EPM development team... You can try to create an idea in the idea place but not sure it will help.

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 28, 2018 at 10:39 PM

    As an aside, this issue was noticed by others and posted on Idea Place/Customer Influence (. SAP implemented a workaround as listed in Note 2383435. I haven't tried it, yet, but it looks cumbersome to implement for 350+ EPM Add-in end users, and it also eliminates some functionality in the newer add-ins (and unknown if it will work ongoing with future releases). Better option would be if SAP would just fix it.

    Add comment
    10|10000 characters needed characters exceeded

    • Now the note is available!

      Extract:

      1. Ensure that the EPM Add-in is closed.
      2. Go to the FPMXLClient.dll.config file.
      3. Edit this file and Add the following line in the middle of the file:
        <add key="UseWpfMemberSelector" value="false"/>

  • Jan 30 at 06:10 PM

    Yes, that workaround is the only solution. Still - can't really get it installed on our 350+ clients. Oh well. Also, I found another note, note 2425718 ,that describes the issue now - the fact that when using Find in member selector with the newer EPM add-in versions, the results are not returned in the the hierarchy view. This fix of adding in that row in the config file gets back that ability to see find results in the hierarchy view - and it does work just fine.

    But, I mean, if SAP wanted conformity between MS and NW versions in this behavior, really, they should have endeavored to make the NW versions show search results in the hierarchy view- it's much more valuable than not - the poor NW users have been missing out! Sometimes I want to see the siblings and parent - the entire area where the member is that I've searched for.

    Ahywhoo, just wanted to drop that additional note in here. Best!

    Add comment
    10|10000 characters needed characters exceeded