TM1 Forum

Actually if the batch file is in the data directory then all that is required is as the default directory path that TI assumes is the database directory.

If there's to be any artillery barrage it will be offline. We have done large scale stress testing (200 - 300 concurrent write users) with load scripts. It's not in the public domain as it has been done with client data as part of projects. No argument that 9.1 loses out in raw speed compared with 9...

I'm glad we're so obviously making progress then. En contraire Monsieur Obson, ... admittedly the backend engine may have lost some pure raw speed (in a single user environment) but what of the gains in multi-user performance, x64, granular object locks, user interface (action buttons, active forms...

Processing cube views in 913 and 914 is extremely sensitive to cube optimisation (dimension ordering), much more so than 912 or 90x. The processing time can probably be improved greatly by optimising the dimension order (but still won't be as fast as 9.0)

Locations: Australia: Sydney and Melbourne, Europe: London UK and Brussels BE Coverage: (where we are implementing TM1 in the next couple of months) UK, Switzerland, Belgium, Middle East, Asia, Australia, ... Type: Certified IBM Premier Partner. Certified Cognos Platinum Partner as software reselle...

is there such an example? ... Has this one stumped you all? I would say not, perhaps many consultants, myself included, might usually feel a worked MDX example would be giving too much away. However, in the spirit of Christmas giving, ... Note that using MDX in Excel uses a separate connection to t...

If building a report is your aim then pulling filtered views into a flattened cube doesn't seem necessary. First question are the views permanent or transitory? (by that I mean constructed and destroyed by TI and not accessible to users). If the views are permanent and you don't mind these objects c...

Unless the specific cube properties are set to "LoadOnDemand" then all cube data is loaded into memory when the database loads. Consolidations are calculated on demand. Once a view is loaded into memory the view is cached on the server and will be much faster for subsequent users to access...

Solution varies depending on the TM1 version. Some TM1 versions will unlock an account that has been locked due to maximum login attempts with wrong password being exceeded with a password reset. However, most versions of TM1 will only unlock an account that has been locked for this reason following...

I see Paul has just beaten me to it! My suggestion is basically the same as Paul's first suggestion. Have a uniform "Reading No." dimension with elements "Reading 0001, Reading 0002, ..." The actual reading date would be best stored in a second lookup cube or as a string measure ...

Depending on the size of the cubes and complexity of the rules option 2 will definitely be more CPU and time intensive as it involves reprocessing all rules and feeders for the cubes. Rather than deleting all consolidations in the account dimension I would suggest unwinding all consolidations. (brea...

Hmmm I've always used the approach of having some kind of standard naming prefix, followed by user name, TI process name, datestamp, whatever, to make sure the subset name is unique for those instances where you can't create and destroy a subset in the same process, that is the returned subset needs...

The reason you don't get any values in the destination cube for consolidated values with the rule as N: (even with suppress zeros off) is that the leaf cells are not fed. I think you are most likely correct in your assumption about customer dimensions. My french is rusty to non-existent but I think ...

Simple answer, if the rule works but you see nothing with a zero suppressed view then the feeder in the source cube is incorrect. In the destination cube right click a value (consolidated or leaf) and select "check feeders" (or whatever the equivalent French translation is) in the source c...

Hi Jennifer, Assuming the consolidation "All Issue Dates" is a flat consolidation of all issue dates ever then as your rule currently stands you shouldn't need a feeder if some of the children of the consolidation contain real input values then consolidation is triggered and no feeder flag...

Hi,

TM1 will take the values in the source file as given, not truncate them. If your TI input values are rounded off to 2 dp then this will be due to a setting in the saving of the source data. To fix this you need to fix the problem at the source.

Never heard of "Clarity", do you mean MS ProClarity?

If the performance monitor is on then make sure to turn logging off for the }Stats cubes. If the performance monitor runs for any length of time then the log files will get very very large if cube logging is left on.

Hi SADELMA What you are asking for is not within the functionality of a slice direct from the cube viewer. However if you use insert an in spreadsheet browser object and reference it to your view then it will stay dynamic in the way that you want. However with ISB you have very limited options as fa...

I think you just need to use the SubsetAliasSet function. zB. SubsetCreatebyMDX( 'Füllstellen', '{FILTER( {TM1SUBSETALL( [Kostenstellen] )}, [Kostenstellen].[Bezeichnung] = "*Fst*")}'); SubsetAliasSet( 'Kostenstellen', 'Füllstellen', 'Bezeichnung' ); Problem erledigt! Except that I just ...