TM1 Forum

Here is another thread on this same topic from a few weeks ago:

https://www.tm1forum.com/viewtopic.php?f=3&t=14287

blackhawk wrote: ↑

Wed Apr 03, 2019 1:53 am

Good to see that you have it worked out; and thanks for the refresher on what NOT to forget about.

You have that right! Every now and then we need it.

The cube was created in PA (only the TI was migrated) and actually, years ago, the 10.2 cube had its dimensions reordered; I just did not check or consider that initially in PA. We kind of worked our way into by taking the DATA procedure code out and putting in back in one section at a time until we...

Almost embarrassed to say it. The problem was the cube needed the dimensions re-ordered. Took care of it. One of those things I just do not think about often enough. Thanks, @bgregs, for looking over my shoulder on this one...

Migrated a TI process from 10.2 that processed approximately 900,000 records in that system. It averages between 3:20 and 3:30 minutes run time. It reads from an Oracle database and loads a cube It processes the dataset through both the Metadata and Data tabs It clears the target cube CubeSetLogChan...

And select the alias either through the TI code to create the subset or in the subset editor.

Wim Gielis wrote: ↑

Sat Mar 30, 2019 7:13 am

What is the use of this exercise if I may ask ?

To attempt to massively confuse everyone who read the post.

Meant the CellValueS function as the error message I did manage to post correctly, obviously pointed out.

Have updated the original post.

Your statement is a little confusing. CellGetS is only for use in TurboIntegrator. It would simply return the value of a cell based on the supplied cube and dimensions. It shouldn't be able to be used in a rule. For rules you should be using DB(). If a TI is using CellGetS and you it says you have ...

Have used CellValueS in a few cubes and the rules work fine with the correct value returned, etc. However, when a TI reads a cell that is populated by a CellValueS rule, the server log has a WARN line with Too few arguments to CellValueS function a listing of the offending rule. Have not been able t...

Couple of things here 1. Im able to make it work with PAW 39. However you may want to add the extra set of [] to force the Hierarchy name just in case you use hierarchies. FILTER( TM1FILTERBYLEVEL(TM1SUBSETALL( [Organization]), 0), LEN([Organization].[Organization].currentMember.Name) > 18); 2. If ...

Wim Gielis wrote: ↑

Wed Mar 20, 2019 7:31 pm

Hello,

You could fill up an attribute with the length of the string, probably with TI but a rule is possible too. After that you can query on the attribute. I haven’t used it in Workspace until now.

Squat. Forgot about that, Wim, thanks! It'll do.

This code: FILTER( TM1FILTERBYLEVEL(TM1SUBSETALL( [Organization]), 0), LEN([Organization].currentmember.Name) > 18); works just fine in Architect and TIs. Returns "Invalid MDX expression" in PAW. The Reference Guide does not list LEN as being a supported function so there is that. Has anyone else ha...

Write a TI that uses WilcardFileSearch in the Data folder the instance. Create dimensions as needed to capture the returned objects you wish to catalog. Put this in a chore that runs regularly to keep those dimensions updated. There may be other methods, but that will do it. In Planning Analytics, t...

jim wood wrote: ↑

Mon Mar 11, 2019 11:30 am

Moved to the correct forum. I'll get my tin hat ready for when Tomok sees this!!

Had to laugh. As I was reading it, thought almost the same thing, "wait until Tomok sees this!"

It appears the leaf level "1478524789" is a unique identifier and assume the prefix is a categorization such as business unit/etc. If true, I would have actually used the "1478524789" as the primary element name with the prefix as an attribute and have a alias that combines the two into the desired ...

Hi Not sure I understand why you would not use easier functions that TM1TupleSize and Item. Straight from my MDX page: @Wim, ask a hard question. :) 1) Have visited your MDX page. Just did not recall those queries or would have referenced them. 2) Have to admit I'm not as up on all the various MDX ...

lotsaram wrote: ↑

Tue Mar 05, 2019 8:22 pm

Childless consolidations still evaluate as level 1 and not level 0.

Flat did not think about/realize that. Good tip, thanks.

Example Dimension has two consolidations without children: Test2 hierarchy.png This MDX code produces as set of the consolidations without children: FILTER(EXCEPT(TM1SUBSETALL( [test2] ), TM1FILTERBYLEVEL( TM1SUBSETALL( [test2]), 0)), TM1TUPLESIZE( ([test2].currentmember.children).ITEM(0)) = 0) Chil...

Tried that and the drill went back to the behavior of not returning the view name to the viewer and the same two dimensions without their associated subsets as well. However, an update on rebuilding the pre-existing view and calling it with ReturnViewHandle: it does return the view (sans the two sub...

Have run head-on into this with PA-2.0.05. Is it fixed in any of the subsequent releases? Did not have this problem in 10.2 using the technique of building custom cube views and by-passing the default Epilog ReturnViewHandle. UPDATE In 10.2, the method I used was building subsets and a view with a d...