If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Difference between Tuple() and completeTuple()

Started by cognos05, 19 Jun 2014 07:43:33 AM

Previous topic - Next topic

cognos05

Hi All,

I wanted to know the difference between Tuple() and completeTuple() expression.

filter(members([Item Numbers].[Item Numbers].[Level 3]),(completeTuple(parent(currentMember([Item Numbers].[Item Numbers])))) is missing)

The above statement gives me one result

filter(members([Item Numbers].[Item Numbers].[Level 3]),(Tuple(parent(currentMember([Item Numbers].[Item Numbers])))) is missing)

And the above statement gives different result.

Thanks,
Nithya


raj_aries81

CompleteTuple will use the default measure rather than the currentMeasure for the current iteration

Regards
raj

Lynn

#2
The attached document provides some additional explanation plus examples.




*Attachment removed, please use link below* - MDXpressor

Michael75

#3
Lynn's attached document is copyrighted 2009. I noticed that I have a more recent version, copyrighted 2011 (attached).

I can't believe that much, if anything at all, changed in those two years, and I certainly haven't done a line by line comparison of the two documents myself.

I'll leave that as an exercise for the attentive reader :)



*Attachment removed, please use the link below * - MDXpressor

Lynn

Oh great!! It looks the same but I'm very happy to have the latest!! Thank you!

bdbits

Make that two of us. I had the older one and have used it a lot. I did not know there was an updated one available.

Thank you, Michael75!  8)


MDXpressor

#6
Given that it's copyrighted material, it should really be accessed through the IBM website.  Can I get one of you to post the links to the document, and remove the attachments, please?

For those of you trying to crack the MDX language, there is a very good book written by Mark Whitehorn call Fastrack To MDX.  While the language covered in it is the Microsoft version of MDX, and you can't write that syntax directly in Report Studio, the functions will line up perfectly with the OLAP functions document published by the Best Practices folks.  The book gives a very nice way to understand the language as a whole, and it also offers additional insight into each of the functions that the Cognos document just doesn't spell out for you.

For instance:  children()
This function requires that you pass a member as a variable, but returns a set when completed.

whereas:   item()
This function requires a set and an index, and returns a member.

Knowing what you need and what you'll get is a great output of every chapter in the MDX book I referenced above.
No, a proof is a proof. What kind of a proof? It's a proof. A proof is a proof, and when you have a good proof, it's because it's proven.

-Jean Chretien

Cognos.Developer

Hi Friends,

I like so much MDX Language,

In My Experience i gathered few details.I would like to share the some links which are useful to get awareness o n MDX.

1) http://www.mdxpert.com/
2) MDX Functions explanation with Pictorial Information:
     http://demoserver.entsoftsol.com/Help/MdxHelp.htm

3) http://www.documbase.com/mdx-queries.pdf

4) http://mdxquery.com/
5) http://www.bidn.com/blogs/sirfnet/ssas/1430/mdx-functions-mdx-examples-mdx-queries

5) http://www.cubeslice.com/support.htm



Thanks
Kumar

Michael75

@ MDXpressor

Here's the link for the 2011 version: http://www.ibm.com/developerworks/data/library/cognos/page82.html

I did briefly have second thoughts about uploading this attachment - I think it was when I typed the word "copyrighted" - but then I decided that if uploading an IBM Cognos document to Cognoise is good enough for the hallowed Lynn, then it's good enough for me :)

MDXpressor

Hallowed is an excellent description of Lynn's contribution.  I'll save the lecture for someone who'd need one.  We just want to make sure that
a) credit is given where credit is due, and that's what a link does by nature
b) make sure we give future Cognoise readers the best opportunity to read current content

Great contributions.  This thread is now in my bookmarks, great links from Kumar.  I'd never seen most of those.
No, a proof is a proof. What kind of a proof? It's a proof. A proof is a proof, and when you have a good proof, it's because it's proven.

-Jean Chretien

Lynn

Hallowed? I think Hollow might be more apt :)

I've posted lots of IBM documents here over the years and also quoted specific passages from time to time. I attribute them as appropriate and they are all materials that are freely available from IBM without requiring any special login credentials so I didn't see any issue with sharing them. I will, however, cease doing so in the future.

MDXpressor

I took an 8 year hiatus.  lol

Seriously though, it's about providing links to fresh information as much (maybe even moreso) as it is about copyrighting...
No, a proof is a proof. What kind of a proof? It's a proof. A proof is a proof, and when you have a good proof, it's because it's proven.

-Jean Chretien