Forums Retired Products and Controls
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Snowden
130
InitXmlaMethod not fired on all Discover requests
posted

There is a similar topic about this on the forum in 2012 where this was happening and it was aparently fixed in a later SR. However I am still getting this on the latest 2013.1 and SR

The problem: We have a large dimension with 3 million members - when dragging on the name attribute on a filtered query (only 4 of these return in the query) and expanding the All member on the grid (not the filters at the top) the pivot grid excutes a nice MDX statement that NonEmpty()s the measures and other filters nicely and gets the four members and values - however after that a DISCOVER request via XMLA is fired which asks for all 3 million names that is sent back (Quite a huge payload - when we cut back to 150k members it was a 140mb response).

Any attempt to use the InitXmlaMethod event has been unsuccessful because the Discover command is called without firing the event - so we are unable to inject a RestrictionList.

Are there any work arounds for this? Can we use any options to prevent certain attributes from loading their members in the filters since they would be impractical to render and select from?

  • 138253
    Offline posted

    Hello,

     

    Thank you for your post. I have been looking into it and I am wondering what are your DataSource default settings and if you are using a Slicer. Also it would be great if you could send us your query from a Fiddler or whatever you use to run it, so we could be able to investigate this further for you.

     

    Looking forward for your reply.