MDX - enumerating members

Need to convert @LIST functionality to MDX - need to provide a list of members from different levels in an IIF statement:IFF(member1, member2 ...),do this,do that)MDX docs say to use "explicit enumeration" of members, but I can't find examples of the syntax for that.

iif ( IsMember (dim.currentmember, member1) OR IsMember (dim.currentmember, member2) OR IsMember (dim.currentmember, member3), do this, do that)

Similar Messages

Enumerating members of a Group object

Is there anything specific you must do to enumerate the �member� attribute of a group Object via JNDI.
I am using an instance of ADAM as a test Directory. I can search for Group objects with no problem, but when I process the results/object attributes I find that the member attribute is always null ?

The problem was with my Test Directory not my JNDI code - installed and populated a new instance of my ADAM test Directory and Group member enumeration is working fine now.

MDX - Filter members using AND operator in Query designer or otherwise

Hi,
I have the following table:
ID
Column A
1
ValA
1
ValA
1
Special
2
ValA
3
ValA
I need to return only IDs which has a Special value in Column A. So the output would be:
ID
Column A
1
ValA
1
ValA
1
Special
I thought that one way would be to use the MDX operator but there is very little documentation on it. I am a real beginner of MDX.
Thanks in Advance.

Hi RiddlerInPlay,
After testing the issue in my environment, we can add a group grouped on ID, then use an expression to control the row visibility to achieve your requirement. For more details, please see:
In the Row Groups pane, right-click the Details1 group to add a group grouped by ID field.
Delete the first column with “Delete columns only” option.
Right-click the details row to open the Row Visibility dialog box.
Use the expression below in the “Show or hide based on an expression” text box:
=iif(Fields!Column_A.Value="Special",false,true)
The following screenshot is for your reference:
If there are any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

ASO MDX & Shared Members

If I am evaluating a member using isUDA([Organization].CurrentMember,"Rework") on a shared member that is the current member, will the isUDA function return a true value if the base member is tagged with UDA value of "Rework"?<BR><BR>

If you use the IsUda function within an IIF statement then you would have to specify a true part and a false part.IIF (Search condition,true part,false part)

ASO members with formula not rolling up

Hi Gurus,
In our ASO cube we have a members which caluclate % are not rolling up to parent . Its rolling up for MTD but they are not rolling for QTD . Members are in Account dimension .Please let me know if you require more info to get the excat idea .

These are MDX formula members, right? Is the problem that the results are recalculated at the QTD level rather than the MTD level summing up the Period dimension?
Is Period a stored dimension? The members / formulae in dynamic dimensions or hierarchies will always be calculated after roll-up of stored dimensions / hierarchies.
See the section on 'Calculation Order' here: http://docs.oracle.com/cd/E26232_01/doc.11122/esb_dbag/alocare.html#alocare1058144
If that is the problem you're seeing, the only options are a) to use an ASO calculation to derive the percentages as stored values, which can then roll up in stored hierarchies, or b) calculate the percentages outside of Essbase - in a relational staging area, for example.

Calculated members as subset of subset

Hello,
I have defined a calculated members with some filter conditions. Now, I want to create another calculated members based on this calculated members just created. What I mean is, I want to created a calculated members as a subset of a subset. Like
A= real measure
B=subset of A
C=subset of B.
Is this possible in MDX calculated members calculation. I am getting null values when I tried that.

I have this formula for one Outer_patient=
AGGREGATE((EXCEPT([PT AD].[PT Group].MEMBERS,[PT AD].[PT Group].&[H]),
[REV].[REV CD].&[E])
,[Measures].[TOT])
Outer_patient_subset=
AGGREGATE((EXCEPT([PT AD].[PT Group].MEMBERS,[PT AD].[PT Group].&[H]),
[REV].[REV CD].&[E],
[CT].[NDICATOR].&[CN])---subset piece
,[Measures].[TOT])
I want to create a measure like this:
Outer_patient_subset=
AGGREGATE([CT].[NDICATOR].&[CN] ,[Measures].Outer_patient)
Is this possible?
Sorry, If I was not clear before.

LDAP Dynamic Groups

Hi,
I have been trying to do some coding around - fetching members of dynamic ldap groups. In both these code snippets.. I get the same exception:
java.lang.ClassCastException: com.sun.jndi.ldap.LdapCtx
no matter whatever i tried. Can anyone please - let me know what could be causing this exception.
Regards.
String filter = LDAPRealm.DYNAMIC_GROUP_FILTER;
          String[] targets = new String[] { target, "memberUrl" };
          try {
               SearchControls ctls = new SearchControls();
               ctls.setReturningAttributes(targets);
               ctls.setSearchScope(SearchControls.SUBTREE_SCOPE);
               ctls.setReturningObjFlag(true);
               NamingEnumeration e = context.search(baseDN, filter, ctls);
               while(e.hasMore()) {
                    SearchResult res = (SearchResult)e.next();
                    Object searchedObject = res.getObject();
                    //if(searchedObject instanceof com.sun.jndi.ldap.obj.GroupOfURLs){ // dynamic group
                         com.sun.jndi.ldap.obj.GroupOfURLs gurls = (com.sun.jndi.ldap.obj.GroupOfURLs) searchedObject;
                         Principal x500principal = new X500Principal(userDN);
                         if (gurls.isMember(x500principal)) {
and
java.security.acl.Group obj = (java.security.acl.Group)ctx.lookup(groupDN);
               Enumeration members = obj.members();
               Principal member = null;
               while (members.hasMoreElements()) {
                    member = (Principal)members.nextElement();
                    memberDNs.add(member.getName());
               }

How is this different from [your previous question|http://forums.sun.com/thread.jspa?threadID=5434523&messageID=10965220#10965220]? If it is the same queston, then please stay in the same thread.

BPC75NW - Periodic Amount Not Calculating for records with blank YTD value

We are on BPC75NW SP6 and have a YTD consolidation application. Data is loaded on a monthly basis uising a process of importing data files from supplying systems and then loading them into BPC using the data manager append function with a transformation file. YTD amounts are as expected and 'most' periodic amounts are also calculated correctly via MDX mesures in reporting. However, in situations where we have a P&L YTD balance in one month (say January) and then in the next month (February) there is no longer a YTD balance in that P&L account, no record is loaded for February YTD and the system is not calculating any February periodic amount. Example:
January - Load $100 to a P&L Account which is the YTD amount
The January YTD amount = $100.
The January Periodic amount = $100.
February - Load no record to the same P&L account as above (as the YTD amount is now 0)
The February YTD amount in the system is blank
The February Periodic amount in the system is blank (This should be a NEGATIVE $100)
As a possible work around we have also tried to load a 0 to February. The data manager package shows the record as loaded successfully but since it is a 0 it really does not put it into the database.
Surely someone out there has already hit this situation and is willing to share the solution.
Thank you,
Vicki S.

This problem was resolved by installing SAP Note 1405993 - MDX: Error: Invalid MDX command with
CURRENTMEMBER. The current text on the note does not describe our error but SAP will not extend the text to cover this issue.
Prior to installing this note, the following other notes were also installed but they did not fix the periodic calculation issue. Under SAP's advisement we are going to leave them however as 'they should not have any side effects':
1529720 MDX: No data for calculated member and metadata reference
1590976 MDX: Incorrect data for IIF
1584196 MDX: Calculated members and different dimensions
1528374 MDX: System error GET_PRPTY_VALUE-02-
I will now close this message.
Vicki Shrontz

ASO Error - Recursion Limit reached

Hi,
I'm getting Recurrsion limit error in ASO while trying to access the data in Excel Addin. I set CALCLIMITFORMULARECURSION FALSE in essbase.cfg but still facing the same error. Any help would be appreciated...
Essbase Version 11.1.13
"Error executing formula for [MemeberName] (line 0): Recursion Limit [31] Reached"
Thanks
Edited by: MoFa on Jul 26, 2012 4:48 PM

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

Adding payment through DI API referring to Correction Invoice/Down Payment

Dear All,
In SBO 2004C (PL 72) I have to add incoming payment referring to correction invoices and down payment invoices.
In Payments_Invoices Object there is and InvoiceType Property which should be set to the object type of the referred document. Having set this to it_Invoice, it_CredItnote and it_JournalEntry it works fine, but I cannot find a working value for Correction invoices and Downpayments.
In BoRcptInvTypes Enumeration there is a it_CorrectionInvoice member, but it does not work. DownPayment member does not exist at all.
Instead of Enumerations members DI API acepts numeric object type values 13, 14, 30 which works just as the above it_Invoice etc. does, but Correction invoice's object type 165 just does not work
Has anyone experience with this?
Is is really not possible to add invoice type payments referring to these documents through DI?
Any ideas are welcome.
Thanks a lot.
Regards.
Bálint

Hi
It is possible in 2005 Clusters But i am not sure in 2004 C.
In 2005 DI API accepts Enumerations members ,In Which Both it_CorrectionInvoice,DownPayment Exists and i hope these works fine 2005.

CUBEVALUE - How it works for filters in EXCEL?

Hello All,
I am using CUBEVALUE fucntion in Excel with many dimension as filter.
For the below condition, CUBEVALUE function failed to return values based on filter, it returns all value.
Case 1:
Dimension1 - COLUMN1 ( All Value )
Dimension1 -COLUMN2 ( Single Value )
--> CUBEVALUE returns proper value.
Case 2:
Dimension1 - COLUMN1 ( All Value )
Dimension1 -COLUMN2 ( Mutiple Value )
--> CUBEVALUE returns ALL values and it does not consider Dimension1 -COLUMN2 filter.
Case 3:
Dimension1 - COLUMN1 ( Multiple Value )
Dimension1 -COLUMN2 ( Mutiple Value )
--> CUBEVALUE returns proper value.
Could you please help me to understand how CUBEVALUE function works based on filter value? Is there any way to profile the value based on filter?
Thanks,
Ravi M N

Hi Ravi,
According to your description, you are using CUBEVALUE function in EXCEL, and cannot get the expected results when using FILTER function, right? CUBEVALUE function only allows calling a measure which is then filtered using member expressions. What this means
is that you cannot create MDX calculated members on the fly using the CUBEVALUE function. Here are some links that might helps.
http://www.msbicentral.com/Resources/Articles/tabid/88/articleType/ArticleView/articleId/144/DAX-and-the-CUBEVALUE-function.aspx
http://office.microsoft.com/en-in/excel-help/cubevalue-function-HA010083018.aspx
Regards,
Charlie Liao
TechNet Community Support

JSP Error: Include limit reached

Hi All,
I am developing on iAS 6.0 SP1 on WinNT. I have my initial index.jsp
which uses
<%@ include file=xx.jsp %> to layout the main page depending on a set of
session values.
At the moment I have about 31 such includes. But I get the following
error with that jsp.
I remember there was a limitation of 20 includes in NAS 4.0.
I feel that same limitation is with iAS.
If so is there a way to overcome this limitation?
TIA
Dhaninda Weerasinghe
plate: /cat/index.jsp, JSP Error: Include limit reached
Exception Stack Trace:
java.lang.Exception: JSP Error: Include limit reached
at com.netscape.jsp.JSP.parseAt(Unknown Source)
at com.netscape.jsp.JSP.parseNext(Unknown Source)
at com.netscape.jsp.JSP.parseBlock(Unknown Source) . . .

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

How get data from WebPartStorage?

Hi, Im creating custom ToolPart. I want save and get data in WebPartStorage. Now i have problem with get data...This is what I create:
How get data form WebPartStorage?
public partial class ExchangeRateWebPart : Microsoft.SharePoint.WebPartPages.WebPart
[Browsable(true), Category("Miscellaneous"),
DefaultValue("Site Names"),
WebPartStorage(Storage.Shared),
FriendlyName("URLs"), Description("Text Property")]
public List<string> ListCurrentNames
get;
set;
protected override void Render(HtmlTextWriter writer)
base.Render(writer);
writer.Write(ListCurrentNames);
class ExchangeRateCustomToolPart : ToolPart
public override void ApplyChanges()
ExchangeRateWebPart webpart = (ExchangeRateWebPart)this.ParentToolPane.SelectedWebPart;
webpart.ListCurrentNames = _listCurrentNames;

Hi,
According to your post, my understanding is that you wanted to create custom toolpart.
WebPartStorageAttribute class specifies how a property should be stored.
If a WebPartStorageAttribute attribute is not specified for a property, Personal is used by default.
If a WebPartStorageAttribute attribute is specified for a property but the ControlledExport property is not
set, the value is presumed to be set to false.
You might have noticed that the Web Part custom property has some attributes. Each of them are described below.
Property
Description
Browsable
If false, the property is not displayed on the web part property pane
DefaultValue
Default Value for the property
WebPartStorage
Shared, Personal and None are the enumeration members
FriendlyName
The name for the property for display purposes
Description
The tooltip about the property
http://www.c-sharpcorner.com/UploadFile/40e97e/sharepoint-2010-web-parts-programming/
there are some articles about custom the toolpart, you can have a look at them.
http://www.wictorwilen.se/Post/Web-Part-Properties-part-1-introduction.aspx
https://www.nothingbutsharepoint.com/sites/devwiki/articles/Pages/SharePoint-Creating-a-Custom-ToolPart-for-a-Custom-Web-Part.aspx
http://microsoftsharepointdevelopment2010.blogspot.com/2012/03/creating-webpart-with-custom-toolpart.html
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

CalcLimitFormulaRecursion

Based upon member/formula changes, this message is now appearing in the application log:"Formula calculator recursion limit [31] crossed. If server crashes due to excessive recursion, set CalcLimitFormulaRecursion to TRUE in essbase.cfg."The server has not YET crashed, but need some guidance as how to proceed.I know that there is an entry that can be made to the Essbase.cfg file. CALCLIMITFORMULARECURSION TRUE or FALSE(default). If set to FALSE or missing I assume that the server, not just the application will crash. Is this considered an abnormal shutdown whereas it will restart itself? Can anyone confirm this?If set to TRUE, I assume that the server will not crash, but the results will not be calculated correctly, and an entry will be made in the application log. Is there any Warning or Error message displayed on the screen informing the user of the problem?What have other done when presented with this issue?Thanks.Regards,Tom [email protected] 6.5.4

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

Error "Members, tuples or sets must use the same hierarchies in the function" in MDX

the following MDX returns error: "Members, tuples or sets must use the same hierarchies in the function"
WITH
MEMBER [Measures].[Prev Year] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Year].Levels('Year'),
1,
[Exec Date].[Year].CURRENTMEMBER
MEMBER [Measures].[Prev Month] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Month Num].Levels('Month Num'),
1,
[Exec Date].[Month Num].CURRENTMEMBER
MEMBER [Measures].[Prev Day] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Day].Levels('Day'),
1,
[Exec Date].[Day].CURRENTMEMBER
SELECT NON EMPTY { StrToMember("@ExecDateLevel"), [Measures].[returns] } ON COLUMNS, NON EMPTY { ([Employees].[Company].[Company].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM (
SELECT (
STRTOSET(@ExecDateHierarchy, CONSTRAINED)
) ON COLUMNS FROM [cbSales]) WHERE ( IIF( STRTOSET(@ExecDateHierarchy, CONSTRAINED).Count = 1, STRTOSET(@ExecDateHierarchy, CONSTRAINED), [Exec Date].[Hierarchy].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
and when I replace "StrToMember(@ExecDateLevel)" with
StrToMember("[Measures].[Prev Month]") the MDX is compiled correctly.
what is the problem?
How can I solve that?

Hi Breceive,
In your scenario, the issue is caused by that you select dimension members and measures on the same axis without a crossjoin.
SELECT NON EMPTY { StrToMember("@ExecDateLevel"), [Measures].[returns] } ON COLUMNS
To avoid this issue, you can use the query below.
WITH
MEMBER [Measures].[Prev Year] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Year].Levels('Year'),
1,
[Exec Date].[Year].CURRENTMEMBER
MEMBER [Measures].[Prev Month] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Month Num].Levels('Month Num'),
1,
[Exec Date].[Month Num].CURRENTMEMBER
MEMBER [Measures].[Prev Day] AS
[Measures].[returns],
PARALLELPERIOD
[Exec Date].[Day].Levels('Day'),
1,
[Exec Date].[Day].CURRENTMEMBER
SELECT NON EMPTY { StrToMember("@ExecDateLevel")*[Measures].[returns] } ON COLUMNS, NON EMPTY { ([Employees].[Company].[Company].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM (
SELECT (
STRTOSET(@ExecDateHierarchy, CONSTRAINED)
) ON COLUMNS FROM [cbSales]) WHERE ( IIF( STRTOSET(@ExecDateHierarchy, CONSTRAINED).Count = 1, STRTOSET(@ExecDateHierarchy, CONSTRAINED), [Exec Date].[Hierarchy].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
Here is a similar thread for you reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3c21d9a8-640d-4dde-bc76-08d1fcbb3a31/multiple-dimension-query?forum=sqlanalysisservices
Regards,
Charlie Liao
TechNet Community Support

MDX - enumerating members

Similar Messages

Maybe you are looking for