Hi,
I am trying to get the 'Drillthrough' feature working in excel 2003 (I
have an action set against my 2005 cube for drillthrough).
I can drillthrough fine in the cube browser but cannot get it to work
in excel.
If I double-click the cell I get an error and have read that I may need
to use the excel addin to do this. However, when I have installed the
addin and the 'required components' I can setup a connection to the
cube but when I try to connect get an error saying I do not have
permissions or my cube does not exist - both of which are false.
Anyone come across this and have a solution?
Thanks,
DarrenHi Darren,
Just write an DRILLTHROUGH MDX Query in Managamnet studio and see your
getting the data.
Let me know if your still having any issue.
Balaji
darrenmr2@.gmail.com wrote:
>Hi,
>I am trying to get the 'Drillthrough' feature working in excel 2003 (I
>have an action set against my 2005 cube for drillthrough).
>I can drillthrough fine in the cube browser but cannot get it to work
>in excel.
>If I double-click the cell I get an error and have read that I may need
>to use the excel addin to do this. However, when I have installed the
>addin and the 'required components' I can setup a connection to the
>cube but when I try to connect get an error saying I do not have
>permissions or my cube does not exist - both of which are false.
>Anyone come across this and have a solution?
>Thanks,
>Darren
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200602/1
Showing posts with label as2005. Show all posts
Showing posts with label as2005. Show all posts
Friday, February 24, 2012
Sunday, February 19, 2012
Drillthrough action not working
Hello,
I have an AS2005 cube in which I created a drillthrough action. For some reason, it won't return any rows. Even the cube browser within BIDS won't show any results. I have the same setup for another project where it works fine. Can this be security related? I have a single role which has all possible permissions.
Thnx. Jeroen
I'm assuming you have a SQL Server database backend to this. Have you run Profiler against that database to see what query is being submitted or whether errors are being raised on the backend that for some reason are not bubbling up to you?
B.
|||Hello Bryan,
I captured the drillthrough query with Profiler like you suggested, and ran the following MDX in Management Studio:
Code Snippet
DRILLTHROUGH
SELECT
( [Measures].[Number of Visits]
, [Visit Status].[Visit Status].&[Done]
) ON 0
FROM
[Visits]
RETURN
[$Visit Status].[Visit Status]
, [$Account].[Account Code]
Now, the SELECT clause contains a lot more slicers, but for some reason, when I leave out all parts which select a specific value using the "&" sign, the query returns a result. So in the query here, when I leave out
, [Visit Status].[Visit Status].&[Done]
data is returned. When I leave out only ".&Done" then a result is returned as well, with in most cases the Visit Status being "Done".
Any clue?
Thnx, Jeroen
<some time passed, did some further research>
It seems to be related with the "IgnoreUnrelatedDimensions" property of the MeasureGroup. When this property is set to
TRUE - won't give any results
FALSE - works OK
However, in some cases I need it to be TRUE... Anyone knows a good bit of explanation of this property and of using MeasureGroups and Dimension Usage in general?
Thnx, Jeroen
|||I'm not 100% what all the IgnoreUnrelatedDimensions property does, but the one thing we use if for is to ensure that when a dimension that does not have a relationship to a measure group from which a measure is derived is used with that measure in a query, no values are returned. Wow! That was a long sentence! Let me try to explain this another way....
In a cube, I may have multiple measure groups, each containing one or more measures. Each measure group has relationships defined with the dimensions and some of these dimensions will have relationships with multiple measure groups. When I browse the cube in a traditional browser, e.g. SSMS or Proclarity, I don't see those relationships. So, it is possible for me to grab a dimension, put it on an axis (so to speak), and then grab an unrelated measure. Because the two are unrelated, there is no data at the intersection of these two sets. So, SSAS has to decide what to show you.
The internal logic of how SSAS thinks about cubes should return the top level aggregated value for that measure. In other words, the measure as it exists if you selected no dimensions to dice it by. (There are variations on this, but we're keeping the concept simple. Just imagine a single dimension on rows and the measure on columns.) If you've ever seen a repeated value all the way down a column in your cell-set, you're probably looking at this.
This isn;t the most intuitive way to display the data to a user. So, the IgnoreUnrelatedDimensions property can be set to True to adjust the behavior. With this property set to True, the values of the unrelated measure are just hidden.
So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
B.
|||Hi Bryan, thanks for your explanation -verbose!
I had noticed a bit of this behaviour as well. I have a few cubes and some of them have multiple measuregroups, like Order / OrderItems. I think hiding the measures is the most decent way to do it as well. So I guess that only leaves the question why the drillthrough option doesn't work when the option is set to TRUE...
Jeroen
|||So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
|||Hi, both relationships are present, since this is a cube with just a single MeasureGroup.
Jeroen
|||Sorry, but I'm kinda out of ideas with this one. If there is a suspicion this might be security related, you may want to get rid of that role to see if this changes anything.
B.
Drillthrough action not working
Hello,
I have an AS2005 cube in which I created a drillthrough action. For some reason, it won't return any rows. Even the cube browser within BIDS won't show any results. I have the same setup for another project where it works fine. Can this be security related? I have a single role which has all possible permissions.
Thnx. Jeroen
I'm assuming you have a SQL Server database backend to this. Have you run Profiler against that database to see what query is being submitted or whether errors are being raised on the backend that for some reason are not bubbling up to you?
B.
|||Hello Bryan,
I captured the drillthrough query with Profiler like you suggested, and ran the following MDX in Management Studio:
Code Snippet
DRILLTHROUGH
SELECT
( [Measures].[Number of Visits]
, [Visit Status].[Visit Status].&[Done]
) ON 0
FROM
[Visits]
RETURN
[$Visit Status].[Visit Status]
, [$Account].[Account Code]
Now, the SELECT clause contains a lot more slicers, but for some reason, when I leave out all parts which select a specific value using the "&" sign, the query returns a result. So in the query here, when I leave out
, [Visit Status].[Visit Status].&[Done]
data is returned. When I leave out only ".&Done" then a result is returned as well, with in most cases the Visit Status being "Done".
Any clue?
Thnx, Jeroen
<some time passed, did some further research>
It seems to be related with the "IgnoreUnrelatedDimensions" property of the MeasureGroup. When this property is set to
TRUE - won't give any results
FALSE - works OK
However, in some cases I need it to be TRUE... Anyone knows a good bit of explanation of this property and of using MeasureGroups and Dimension Usage in general?
Thnx, Jeroen
|||I'm not 100% what all the IgnoreUnrelatedDimensions property does, but the one thing we use if for is to ensure that when a dimension that does not have a relationship to a measure group from which a measure is derived is used with that measure in a query, no values are returned. Wow! That was a long sentence! Let me try to explain this another way....
In a cube, I may have multiple measure groups, each containing one or more measures. Each measure group has relationships defined with the dimensions and some of these dimensions will have relationships with multiple measure groups. When I browse the cube in a traditional browser, e.g. SSMS or Proclarity, I don't see those relationships. So, it is possible for me to grab a dimension, put it on an axis (so to speak), and then grab an unrelated measure. Because the two are unrelated, there is no data at the intersection of these two sets. So, SSAS has to decide what to show you.
The internal logic of how SSAS thinks about cubes should return the top level aggregated value for that measure. In other words, the measure as it exists if you selected no dimensions to dice it by. (There are variations on this, but we're keeping the concept simple. Just imagine a single dimension on rows and the measure on columns.) If you've ever seen a repeated value all the way down a column in your cell-set, you're probably looking at this.
This isn;t the most intuitive way to display the data to a user. So, the IgnoreUnrelatedDimensions property can be set to True to adjust the behavior. With this property set to True, the values of the unrelated measure are just hidden.
So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
B.
|||Hi Bryan, thanks for your explanation -verbose!
I had noticed a bit of this behaviour as well. I have a few cubes and some of them have multiple measuregroups, like Order / OrderItems. I think hiding the measures is the most decent way to do it as well. So I guess that only leaves the question why the drillthrough option doesn't work when the option is set to TRUE...
Jeroen
|||So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
|||Hi, both relationships are present, since this is a cube with just a single MeasureGroup.
Jeroen
|||Sorry, but I'm kinda out of ideas with this one. If there is a suspicion this might be security related, you may want to get rid of that role to see if this changes anything.
B.
Drillthrough action not working
Hello,
I have an AS2005 cube in which I created a drillthrough action. For some reason, it won't return any rows. Even the cube browser within BIDS won't show any results. I have the same setup for another project where it works fine. Can this be security related? I have a single role which has all possible permissions.
Thnx. Jeroen
I'm assuming you have a SQL Server database backend to this. Have you run Profiler against that database to see what query is being submitted or whether errors are being raised on the backend that for some reason are not bubbling up to you?
B.
|||Hello Bryan,
I captured the drillthrough query with Profiler like you suggested, and ran the following MDX in Management Studio:
Code Snippet
DRILLTHROUGH
SELECT
( [Measures].[Number of Visits]
, [Visit Status].[Visit Status].&[Done]
) ON 0
FROM
[Visits]
RETURN
[$Visit Status].[Visit Status]
, [$Account].[Account Code]
Now, the SELECT clause contains a lot more slicers, but for some reason, when I leave out all parts which select a specific value using the "&" sign, the query returns a result. So in the query here, when I leave out
, [Visit Status].[Visit Status].&[Done]
data is returned. When I leave out only ".&Done" then a result is returned as well, with in most cases the Visit Status being "Done".
Any clue?
Thnx, Jeroen
<some time passed, did some further research>
It seems to be related with the "IgnoreUnrelatedDimensions" property of the MeasureGroup. When this property is set to
TRUE - won't give any results
FALSE - works OK
However, in some cases I need it to be TRUE... Anyone knows a good bit of explanation of this property and of using MeasureGroups and Dimension Usage in general?
Thnx, Jeroen
|||I'm not 100% what all the IgnoreUnrelatedDimensions property does, but the one thing we use if for is to ensure that when a dimension that does not have a relationship to a measure group from which a measure is derived is used with that measure in a query, no values are returned. Wow! That was a long sentence! Let me try to explain this another way....
In a cube, I may have multiple measure groups, each containing one or more measures. Each measure group has relationships defined with the dimensions and some of these dimensions will have relationships with multiple measure groups. When I browse the cube in a traditional browser, e.g. SSMS or Proclarity, I don't see those relationships. So, it is possible for me to grab a dimension, put it on an axis (so to speak), and then grab an unrelated measure. Because the two are unrelated, there is no data at the intersection of these two sets. So, SSAS has to decide what to show you.
The internal logic of how SSAS thinks about cubes should return the top level aggregated value for that measure. In other words, the measure as it exists if you selected no dimensions to dice it by. (There are variations on this, but we're keeping the concept simple. Just imagine a single dimension on rows and the measure on columns.) If you've ever seen a repeated value all the way down a column in your cell-set, you're probably looking at this.
This isn;t the most intuitive way to display the data to a user. So, the IgnoreUnrelatedDimensions property can be set to True to adjust the behavior. With this property set to True, the values of the unrelated measure are just hidden.
So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
B.
|||Hi Bryan, thanks for your explanation -verbose!
I had noticed a bit of this behaviour as well. I have a few cubes and some of them have multiple measuregroups, like Order / OrderItems. I think hiding the measures is the most decent way to do it as well. So I guess that only leaves the question why the drillthrough option doesn't work when the option is set to TRUE...
Jeroen
|||So, if this property is affecting whether or not you get results, do you have a relationship established between the Visit Status dimension and the measure group holding Number of Visits? Also, do you have a relationship established between the Account dimension and that same measure group?
|||Hi, both relationships are present, since this is a cube with just a single MeasureGroup.
Jeroen
|||Sorry, but I'm kinda out of ideas with this one. If there is a suspicion this might be security related, you may want to get rid of that role to see if this changes anything.
B.
Friday, February 17, 2012
Drillthrough action
Hi,
Is there any way in AS2005, I can specify a cube action which will bring up an HTML page displaying the Drillthrough MDX for the cell that I just initiated the action on?
Also, will this MDX work across all cube partitions (no need for FIRSTROWSET clause)?
Thanks,
JGP
Drillthrough actions return a DRILLTHROUGH statement to client application (e.g. cube browser) which in turn executes the statement and displays the results. The results will contain data for all partitions (no need for FIRSTROWSET clause). See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5_anservdrill.asp for more info.
HTML actions are unsafe and BI Dev Studio does not let you create them. If you do want to expose the DRILLTHROUGH statement to the user, you have to plug in some code (depends on the client app) that retrieves the actions schema rowset, extracts the statement and displays it.
|||Any idea how I would go about retrieving the action schema rowset? Any samples would be greatly helpful.
I'm trying to get this working from the ProClarity clients (Standard and Professional).
Thanks,
JGP
Drillthrough action
Hi,
Is there any way in AS2005, I can specify a cube action which will bring up an HTML page displaying the Drillthrough MDX for the cell that I just initiated the action on?
Also, will this MDX work across all cube partitions (no need for FIRSTROWSET clause)?
Thanks,
JGP
Drillthrough actions return a DRILLTHROUGH statement to client application (e.g. cube browser) which in turn executes the statement and displays the results. The results will contain data for all partitions (no need for FIRSTROWSET clause). See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5_anservdrill.asp for more info.
HTML actions are unsafe and BI Dev Studio does not let you create them. If you do want to expose the DRILLTHROUGH statement to the user, you have to plug in some code (depends on the client app) that retrieves the actions schema rowset, extracts the statement and displays it.
|||Any idea how I would go about retrieving the action schema rowset? Any samples would be greatly helpful.
I'm trying to get this working from the ProClarity clients (Standard and Professional).
Thanks,
JGP
Subscribe to:
Posts (Atom)