![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I am trying to use attribute members grouping and getting an error. I have a natural hierarchy that looks like: Sector Industry Exposure Position The Position level has many members that I would like to place in buckets of equal size. However when I set the DiscretizationMethod of Position attribute to Automatic and try to deploy the database I get an error: "Error in the metadata manager. The 'Position' discretisized attribute cannot have related attributes". The error is only reported during deployment. It's a natural hierarchy with attribute relations defined so that Position attribute relates to Exposure attribute and so on. It's a 64-bit instance of MSAS 2005 with SP2 CTP applied. If discreditized attributes cannot have related attributes then how does one place them into a natural hierarchy? Or maybe I am doing something wrong? I hope someone can shed some light on this issue. Thanks in advance, Alex |
#3
| |||
| |||
|
|
I understand it's not logical to use the attribute hierarchy as a user hierarchy level when AS cannot determine which Exposure member a certain Position group belongs to. For example, two position members in the same group can have different Exposure members as a parent member. How about adding a dummy attribute to group Position members explicitly instead? Ohjoo "svega" <krichev (AT) bellatlantic (DOT) net> wrote in message news:O4u3AC7HHHA.1280 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Hi, I am trying to use attribute members grouping and getting an error. I have a natural hierarchy that looks like: Sector Industry Exposure Position The Position level has many members that I would like to place in buckets of equal size. However when I set the DiscretizationMethod of Position attribute to Automatic and try to deploy the database I get an error: "Error in the metadata manager. The 'Position' discretisized attribute cannot have related attributes". The error is only reported during deployment. It's a natural hierarchy with attribute relations defined so that Position attribute relates to Exposure attribute and so on. It's a 64-bit instance of MSAS 2005 with SP2 CTP applied. If discreditized attributes cannot have related attributes then how does one place them into a natural hierarchy? Or maybe I am doing something wrong? I hope someone can shed some light on this issue. Thanks in advance, Alex |
![]() |
| Thread Tools | |
| Display Modes | |
| |