This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
I would strongly support making
MilliTime()an officially supported and documented TI function.Besides generating unique names for temporary objects such as views or subsets, I see another very practical use case: measuring the runtime of relatively short-running TI processes.
For processes that complete within a few seconds,
NOW()only provides second-level resolution. Millisecond precision would allow us to measure and compare such runtimes much more accurately, which can be especially useful when analysing and optimizing TI performance.There is also a practical issue with the current unofficial status of the function. I can confirm that using
MilliTime()in a TI process currently results in an error when the process is saved, because the function is not treated as an officially supported TI function.I am currently also checking whether this has an impact when such a process is executed as part of a scheduled Job. If the Job also reports an error simply because the process uses an otherwise working
MilliTime()function, this would be another strong argument for officially supporting it.If IBM prefers not to expose
MilliTime()as a separate function, supporting millisecond precision directly throughNOW()and the related time functions, as discussed above, would also be a clean solution.It is not an official function in TM1. It would be very good to have support for it in TM1, officially, and in PAW. When we type milli in a TI process, in the past (May 2025) the function name MilliTime appeared. But the function was underlined in red. In October 2025, in PAW 2.0.107 and TM1 2.0.9.23 when I started typing Milli then MilliTime was not offered anymore in the dropdown list for autocompletion.
MilliTime would be a very good way to make views and subsets unique in the name or to time the processing duration of records in the Metadata and Data tabs, or general durations alltogether.
An other approach is to have a function that return a GUID, would solve a lot of headaches with uniqueness
it is a good idea!
MilliTime is not real time, it's effectively the number of milliseconds since first called (first time it returns 0, or very near to 0). That said, it is what TM1 uses internally everywhere it needs to know how long something took.
Whilst not opposed to making this, currently internal, function public, wonder if, given the reference to Now() and granularity of time, it wouldn't be better if we included the thousands of a second into the time values we return AND extend any function that can return a string representation of [date-]time to be able to include the thousands of a second as well.