TM1 Forum

Elessar,

Have not looked at your link yet, but I do have an update. This also happens when a bad alias is handed to StrToMember. That should not have happened in our case, but we had a bad alias stored in a cube and, Whoa Nellie! it crashed the server while building a subset off that measure.

Yes, the server crash is unacceptably cruel. But you can use the workaround using the union of two members and take only one upper one, then if the first one is empty, you can take the default one. But this is terrible in terms of finding bugs. I am responding to this to make sure anyone who sees d...

you tried to put more curly braces??? {GENERATE( {FILTER( TM1SUBSETALL( [Account] ), LEN([mycube].([Version].[Active1], [Measure].[myMeasure])) > 0)} , {StrToMember("[Account].[" + [mycube].([Version].[Active1], [Measure].[RollupAccount]) + "]")})} Those are not necessary with functions that return...

You might look at PublishView TI Function. As a TI runs as Admin, it should publish a private view for public consumption.

We have isolated a problem where StrToMember will cause a server crash. This may be a well known problem, but a cursory Google search did not reveal anything on it. The code is building a subset of accounts based on values in a cube: GENERATE( FILTER( TM1SUBSETALL( [Account] ), LEN([mycube].([Versio...

Fantastic, thanks lotsaram.

Hi PavoGa, If you can I would raise with IBM, seems like a defect? May not help you in the short term unless its already been fixed.... Wondering if that is the case that it has been fixed. There are several reported MDX performance issues with the version we are on (TOPCOUNT, etc) that are fixed i...

Running a query against a cube with six dimensions. The cube does not have any rules against it. The cube has had its dimensions reordered to optimize. The query's target dimension has one consolidation with approximately 450K children. The query: FILTER(TM1FILTERBYLEVEL( TM1SUBSETALL( [AcctOrg Sour...

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...