tag:blogger.com,1999:blog-2615703102299902978.post3589446334697204373..comments2024-02-03T00:03:10.178-08:00Comments on Glenn Schwartzberg's Essbase Blog: Studio Drill Through TipsGlennShttp://www.blogger.com/profile/08532634180859769798noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2615703102299902978.post-14370209612295599792016-05-04T06:17:05.292-07:002016-05-04T06:17:05.292-07:00Yes, it will be in part of an in clause. and while...Yes, it will be in part of an in clause. and while in older versions the sql would fail if you had over a certain number of members, the Studio team now will break up yourquery and make multiple in clauses to prevent failuresGlennShttps://www.blogger.com/profile/08532634180859769798noreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-2462127649496821802016-05-04T05:24:31.668-07:002016-05-04T05:24:31.668-07:00Hello,
In this post you said that for a recursive...Hello,<br /><br />In this post you said that for a recursive hierarchy: <br />< If you are at an upper level and have turned allowed drill trough from that level, you get a list of the level zero members under the member you selected. ><br />So for my Product dimension ( recursive hierarchy), if i select Generation2 in the Define Intersections Tab,and then in my drill-through report, if I select an upper level member, the parameter passed for the product dimension, to the Essbase Studio query,will be in fact a list of all Level 0 members under the selected one?Lunoreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-7806619150799496552014-09-08T06:17:02.161-07:002014-09-08T06:17:02.161-07:00I am not sure there is a solution other than limi...I am not sure there is a solution other than limiting the drill through level so you don't get that many members. I believe the problem only occurs if you are using a recursive hierarchy, If it is possible to change it to be generations or levels, then you would get the actual member name for the intersection and could do a join between tables to get the level 0 members but that would be a redesign of your implementation. GlennShttps://www.blogger.com/profile/08532634180859769798noreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-26657419090413572822014-09-08T05:50:48.370-07:002014-09-08T05:50:48.370-07:00Hi Glenn,
Could you please explain on how to hand...Hi Glenn,<br /><br />Could you please explain on how to handle variable with morethan 1000 members in Essbase studio sql IN Clauese?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-30893932705465926112013-01-04T16:18:17.154-08:002013-01-04T16:18:17.154-08:00While I have an idea of the problem , it is diffic...While I have an idea of the problem , it is difficult to say without seeing what you misischema, Amout member, and cube schema look like. Can you send me screen shots of those to gschwartzberg@interrel.com and I'll see if I can help youGlennShttps://www.blogger.com/profile/08532634180859769798noreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-73387556674692643572013-01-04T15:12:20.999-08:002013-01-04T15:12:20.999-08:00Hi Glenn,
I am following along the exercises in y...Hi Glenn,<br /><br />I am following along the exercises in your book Look Smarter..with Essbase Studio 11 and getting stuck on the deployment. Getting an error No Mapping found for class: \TBC_Sample\Members\Sales\Amount. I have no clue what this means. Any ideas on what steps I missed? This is the first deployment.Anonymousnoreply@blogger.com