The InitXmlaMethod is raised for all requests to SSAS with the exception of MDSCHEMA_MEMBERS, which is initiated when LoadMembersAsync is called.
What is odd is that LoadMembersAsyncImpl does contain code to invoke the event, but from debugging through the code it seems that the handler is not bound at this point in time even though it was bound for all earlier Discover requests and for the subsequent Execute request.
I am working with the Infragistics source code and would really appreciate guidance on a quick fix for this issue.
Regards,
Gary
Hello Gary,
Thank you for your feedback. I’m able to reproduce the behavior you have described. I’m afraid it’s too late to fix that issue with the upcoming SR but we are going to fix it with the next one. Until then you can use the XmlaDataSource class fixed methods I have attached.
Let me know if that works for you.
Many thanks.
Plamen.
Thank you, Plamen. I have confirmed that the code you provided does fix the problem.
As a follow up to this, I would like to suggest that the code in XmlDataProvider.LoadMembersAsynImpl be recognized a bit so that the restrictions are added BEFORE calling OnInitXmlMethod. The restrictions provide valuable context about the request that is useful when implementing the event handler.
Thanks,
Thank you for the suggestion, it really would be helpful to have that information at such point .
Thanks again.