TM1 Forum

One additional consideration. Just in case that primary site attribute were to contain a bad element, it will still cause a failure of StrToMember. One way to avoid that is to add another attribute, using DIMIX, that holds the index value of the primary site within the parent dimension. You would wa...

This is what you need to reference the user id: StrToMember("[}Clients].["+USERNAME+"]") To figure out what part of the MDX is not working, take each section and parse it out to figure what is and what is not returning the expected result. For example, to determine if this is working as expected: St...

Assuming you want to save the coding on the Advance tabs: 1) save the TI off to another file. 2) delete the TI from within Architect. 3) open the copy with a text editor such as Notepad++ 4) rebuild your desired TI using the suggestions from above to set the data source, copy and paste the code sect...

macsir wrote: ↑

Thu Feb 14, 2019 8:25 pm

Yes, you are right. My query is not right. Anyway, learnt how to use TM1TupleSize functon.

Good deal! Glad I could help.

I thought you were trying to find the top or root level consolidations for a given leaf element. The MDX queries you state as simpler specifically reference a consolidation ('d') according to the example you provided while I thought you were interested in determining ancestors of a leaf element. I b...

This returns ALL the ancestors of 'e':

This will do it: FILTER( FILTER( TM1SUBSETALL([test_ANC]), [test_ANC].currentmember.parent.name = ''), TM1TupleSize(INTERSECT({[test_ANC].[e]}, DESCENDANTS({[test_ANC].currentmember})).item(0)) > 0) This assumes we are looking for all the top level consolidations of 'e'. And this: FILTER( FILTER( TM...

StrToMember(" [Site].[ "+[}ElementAttributes_Project].([}ElementAttributes_Project].[Primary Site])+"]") In your call to [}ElementAttributes_Project], the code is missing a reference to [Project] so it cannot find the desired intersection; it is just calling the measure [Primary Site]. I think you ...

If you can use subsets to control display, use a numeric attribute to control the display order.

Otherwise, as Tom states, you have to set dimensionsortorder to ByInput and then carefully control how objects are added.

Thank you, Steve. When I get a chance, I'll try it again.

Steve Rowe wrote: ↑

Thu Feb 07, 2019 4:50 pm

Hi PavoGa,

What's your version number please? Did you get this acknowledged by IBM?

Cheers,

Yes, we did. PA 2.0.05

Hi Ken, We had the same thing and were able to isolate at least one cause which was 100% repeatable. When loading data, if there is an element that does not exist in a dimension, we add that element to a consolidation called "Unregistered" to deal with later. If that consolidation is the first eleme...

This will get you the one level down including the target:
will return c and d only.

I never understood the use of a TM1FILTERBYPATTERN and then a pattern without wildcards. We can reference the element in a direct way, can't we ? Agree, that does not make a lot of sense to me, either. I never use TM1FILTERBYPATTERN as a general rule within the context of TM1DRILLDOWNMEMBER, but co...

Hi, after testing around, I think I can replicate the issue. Very simple, as long as the parent exists in multiple rollups and one of grandparent has "&" in between , then it won't show the children of the parent. No difference for using TM1DRILLDOWNMEMBER or DRILLDOWNMEMBER. To me, those two funct...

Steve Rowe wrote: ↑

Thu Jan 31, 2019 9:53 pm

Can you remember the creation sequence that led to this? In theory every N level should end up in the leaves hierarchy, if this is not reliable then this is a bit of an issue..

Not exactly, no. But the most common that I know of is cold migrations. A server startup does not fix anything.

Can you remember the creation sequence that led to this? In theory every N level should end up in the leaves hierarchy, if this is not reliable then this is a bit of an issue.. Absolutely agreed! ... This has me really scratching my head as there doesn't seem to be any "sync leaves hierarchy" funct...

Found the problem and just wanted to provide an update. In the ORG dimension, the leaf element the spread was being applied to did not exist in the Leaves hierarchy, just the ORG:ORG one. No problem with that, just add the element to the Leaves hierarchy and it spreads just fine. Except while correc...

I always use TM1DRILLDOWNMEMBER with the ALL and RECURSIVE arguments. Is there a reason for not using that function vs. DRILLDOWNMEMBER?

It may be "muscle memory," but Notepad++ seems to be much faster and offers some features I like over the PAW editors. If you take the time to say what these features are you never know who might be watching and find that these features make it into the product (eventually). I have found the produc...