TM1 Forum

If you're only writing the data out to a file so you can read it back in again, won't SetOutputEscapeDoubleQuote cover it? No need to use anything other than the standard double quote, although you can still choose something else if you want, it will double up whatever character you have as the ASCI...

The ConsolidatedXXX functions have been available from as far back as at least 9.5.2.

They weren't added to the documentation until much later, but is anyone surprised by that?

This post got me to thinking about private views. Since as far as I know private objects are ignored at startup and only read into memory when the user logs on then if deleting a public subset will the server throw an error if the subset is only referenced in a private view belonging to a user who ...

If using a built-in feature of Notepad++ or a simple one line command is too much like hard work, and you are feeling new school and fancy a REST: You can use javascript to loop over a list of cubes and return a list of those that use the dimension you are checking (which is only really necessary if...

Normally I would have expected the response to this to be along the lines of change the Placement property to 1 on the Active Form (I did notice Chewza said Active Report and not Active Form). So my question is, what am I missing here? Which given the responses above from the experts is clearly som...

You haven't said what you think it is that is causing the Preview to fail, but one example of where a Preview isn't going to work is if you have any TM1 generated values embedded in the SQL statement. When the data is retrieved for the Preview, TM1 doesn't execute the Prolog, so can't perform the su...

Nope. First guess at the search terms, fifth item on the list..!

EvgenyT wrote:Interesting info. Haven't been able to locate any documentation on that however.

Try this for size.

...even when they are being applied to different areas of the cube (N: and C: Level)... From a TM1 terminology point of view, your rules are not applied to different areas. The definition of a rule is: [Area] = [Qualifier] [Formula]; The [Area] part of a rule is everything to the left hand side of ...

...even when they are being applied to different areas of the cube (N: and C: Level)... From a TM1 terminology point of view, your rules are not applied to different areas. The definition of a rule is: [Area] = [Qualifier] [Formula]; The [Area] part of a rule is everything to the left hand side of ...

Product Compatibility Report looks fine to me.

This being an IBM website, to find the Excel 2016 compatibility you need to look at Note 4 in the Office section rather than look at all the other Excel versions listed under the Excel section.

We still can't use temporary views as data source. Are you saying that you have tried them in FP6 and they don't work? Using temporary views as a datasource was fixed in one of the early FP4 IFs, so even if you didn't get that particular IF, it should have been an early enough fix to have been incl...

Creating a view extract using ViewConstruct was already possible before FP6. Indeed it was, and that was what I was describing. If you still need to go this way after FP6, than this new feature does not bring much new in my opinion. [...] but the nice thing of the Skip Consolidations feature is tha...

Regarding the MTQ usage I'm wondering how much benefit this bring if you have to include consolidated values in the view extract... If you set the view up so that you don't have any consolidations in the view definition to start with (why have them there if you are only going to skip them anyway?) ...

That looks to be a similar issue, but we found it in 10.2.2 FP4 rather than 10.1 as that link shows, and the setting of PersistentFeeders didn't make any difference for us. I don't have the precise APAR number to hand, so it is possible that it is just a mis-identification on that ticket. If it is c...

Be aware that there is an open issue with IBM where RulesOverwriteCellsOnLoad=F can cause feeders to not fire properly.

You may find that your faster startup and smaller memory footprint is because your model is not completely calculated.

How these values will get exported will depend on your setting for RulesOverwriteCellsOnLoad in the config file.

Give this one a go:

http://www.ibm.com/web/portal/analytics ... -analytics

The thing that you are overlooking is: The string passed to the NUMBR function must use. (period) as the decimal separator and , (comma) as the thousand separator. Any other decimal/thousand separators will cause incorrect results. Give this a go instead: StringToNumberEx(String, DecimalSep, Thousan...