Created a dynamic subset. It works in TM1, not in DBRW!

[ChrisF79]

I created a dynamic subset on my server and it works. It has elements in it as it should. I can use it in a cube view within Architect or Perspectives. However, when I use it within a DBRW formula, I get a Key*Error. What's really interesting is that if I make a cube view and do a slice, recalculate, I get a key error in Excel. Any idea why that would be? I'm an admin on the server so it shouldn't be a security issue.

Thanks!

[declanr]

What do you mean by using a dynamic subset inside a dbrw?

Is it like dbrw (cube, subnm (dim, subset, 1)...) or something else? A dbrw accepts element names as its parameters not a whole subset.

Edit - realised what I've said is rubbish. Always forget you can reference subsets in db.. formulas .. might remember if they get round to documenting it

[ChrisF79]

Oddly enough, refreshing security worked. Perhaps it's because we're using rule based security but I'd figure as an admin it shouldn't matter. Another one of those great TM1 "features."

[Wim Gielis]

Hello Chris

Good that it works, but AFAIK this behaviour is not documented.
Also, if you have rules at C level, you might see something different in the cube than your usual sum of elements.
Is there any reason why a regular consolidation is not an option?

Use at your own risk.

[tgaluskapatterson]

Also keep in mind when you are using a dynamic subset in excel/websheet that you will need to have the dynamic subset calculate before the DBRW does. I received a Key*Error when creating a websheet in perspectives and the solution was the dynamic subset dimension needed to be represented as a DBR. DBR allows you to retrieve data from a cube before your DBRW's retrieved. For Example: Lets say you have a currency code attribute attached to the cost center dimension. The DBR would look something like this.
DBR("TM1_PROD:}ElementAttribute_CostCenter",B2,"CurrencyCide")
Where B2 is the cost center element on your websheet.