Databases
StackOverflow2013
Postsdbo
POMisleading cell security error message prevents drillthrough action on SSAS2008
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMisleading cell security error message prevents drillthrough action on SSAS2008
    primarykey
    data
    text
    <p>I have a cube with no cell security configured, and get an intermittent problem with a drillthrough action. The cube has two measure groups: One with accounting transactions from a financials application (Oracle Financials) and one with a set of FX rates. The FX conversions are done with a measure expression, and forced to leaf level by the cube script. This problem is taking place on SSAS2008 (R1).</p> <pre><code>scope ([functional currency].[functional currency].[all]); scope ([measures].[herp fx rate]); this = null; end scope; scope ([measures].[derp fx rate]); this = null; end scope; end scope; scope (leaves ([functional currency])); scope ([fx period].[period].members); scope ({[measures].[Herp GBP]}); this = [measures].[accounted] * [measures].[Herp fx rate]; //fore_color (this) = 4227327; end scope; scope ({[measures].[Derp GBP]}); this = [measures].[accounted] * [measures].[Derp fx rate]; //fore_color (this) = 32768; end scope; end scope; end scope; Calculate; </code></pre> <p>The cube has a drillthrough action on it. When I attempt a drill through action (via the SSMS cube browser, for example) the cube intermittently returns an error to the effect of</p> <blockquote> <p>The drillthrough operation cannot be performed because cell security does not allow access to the source data</p> </blockquote> <p>Various forum postings suggest that setting IgnoreUnrelatedDimension=False will fix this. However, I can't find any documentation that explains why this happens and the error message is somewhat unhelpful. Does anybody have a coherent explanation of what is causing this error?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USConcernedOfTunbridgeWells
    1. USConcernedOfTunbridgeWells
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POMisleading cell security error message prevents drillthrough action on SSAS2008
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMisleading cell security error message prevents drillthrough action on SSAS2008
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, have you found a solution for this problem?
      singulars
      1. POMisleading cell security error message prevents drillthrough action on SSAS2008
      1. USHrvoje Piasevoli
    2. COyah.. what's the solution?
      singulars
      1. POMisleading cell security error message prevents drillthrough action on SSAS2008
      1. USSonic Soul
    3. COIf I recall l correctly it was a data issue in the underlying cube data, and it went away by itself after an ETL run populated the underlying data mart correctly. I think it was more of a case of a misleading error message than anything substantial.
      singulars
      1. POMisleading cell security error message prevents drillthrough action on SSAS2008
      1. USConcernedOfTunbridgeWells
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload