TM1 Forum

With the API you can determine if a rule is attached to a cell but not in TI.

Is this a theoretical question or have you come up against this and have an actual need to do this in a process, what are you trying to do?

The "$" objects (.cub$, .dim$) represent temporary objects created during a save. During normal server operations and while the server is not running these files should not be there. If the server is down, delete them prior to restarting.

Probably because in TM1 Web there is a separate interface for processes which is the only area that processes can be run from in TM1 web.

In the Navigation Tree view pane, under "Administration" you will see "Processes"

Post your offending feeder so that others can have a chance to look at it to see what is wrong. Don't forget that feeders work only at leaf level. ['Total'] => means feed from each and every N level descendant of 'Total' that contains data => ['Total'] means feed each and every N level descendant of...

True.

Why did no one else think of that? Nice tip Peter

If you have enough views to make it worthwhile you could reassign subsets and elements via code in TI or with API code. If you are talking about manually editing the .vue files I don't see how this is any easier than manually recreating views. If you do want to do this then yes it should be possible...

What are you actually doing in your application? If you are using TM1 correctly then there should be no need to have worksheets referencing each other as each worksheet can be "independent" in an Excel sense and just reference the cube(s).

Just a thought ...

Hi Helen, Consider using code tags. For what you want to do I think your code is unnecessarily complex as there is no need to loop through workbooks and worksheets. Application.Run "TM1RECALC1" calculates the active worksheet only (same as user hitting SHIFT + F9, this is the macro that ru...

This is quite a straightforward requirement. Have you read the Date and Time Rules Functions section of the TM1 Reference manual?

I have seen that you have posted this question on numerous forums with not a great deal of takers. In terms of data volume TM1 certainly is scalable, certainly more so than any other MOLAP cubing architecture. For number of users it is not the user count that matters but the number of concurrent use...

Presently we're generating reports in the user-required layout in this mechanism - a) We decide which view of the required cube would give us the data for the report - by rearranging the dimensions according to the report. b) We take a slice of the report which has the raw data - on to an excel she...

additional manual work when upgrading is always going to be a pitfall of customising ...

Do you really need to do it?

As of 9.4 chores can be scheduled simultaneously and will run concurrently as opposed to queuing. (Provided of course that the chores contain independent processes updating independent cubes). You can also run multiple processes by calling externally via a 3rd party app such as TM1ProcessExecute.exe...

Likewise I have only ever seen ODBC connections stay open if a process aborts. If the process completes successfully or with minor errors then the connection should close. If a process aborting is causing your problem then adding ODBCClose to the Epilog won't do anything since the Epilog code won't ...

Depending on your delivery mechanism it is relatively easy with number formatting to make 0 appear as "-"

i undestand that this function exist onli in version 9.5? It appears so. There doesn't seem to be any reference to it in the release notes (what a surprise :roll: ), but doing a search through my document library shows it only in the 9.5 Reference .pdfs, not in those of any earlier version. You cou...

The bottleneck in saving is the disk subsystem, at least on my system, so adding compute capacity will not improve performance. Duh - Oh, Houston we have a problem. Poor old hard disk head can only do so many things, should have thought of that. Hmm maybe another take on things would be to enable a...

I second Alan's interpretation both in that chores do not do "catch ups" if an execution is missed due to server downtime then the next run time is the next scheduled time. Also property 530 is the first scheduled run of a chore, it is never updated (unless the chore is rescheduled in the ...

Yes multi-threaded server loading is for data only. Metadata is single threaded. But no I was also talking about data loading no just server loading. This is getting off topic of the enhancement to enable multi-threaded data saves but in 9.4 and 9.5 at least it is very easy to do multi-threaded data...

We have had multi-threaded server loading for some time now and can now also multi-thread data loads. Together with 64 bit servers this has facilitated a huge expansion with the volume of data TM1 can handle. However this all comes unstuck when a data save is executed following batch updates. As the...