Search found 6 matches

by schmrob
Fri Mar 11, 2022 5:17 am
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: Time formats in cube views
Replies: 7
Views: 1650

Re: Time formats in cube views

The main issue here is that you are not dealing with a serial number that can be formatted. If you divide your 1234.75 by 24 and apply a format of hh:mm to the result you end up with something like 10:45 but miss the other 19 days as the formatting would now want to convert the serial number to a p...
by schmrob
Tue Mar 08, 2022 5:31 am
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: Time formats in cube views
Replies: 7
Views: 1650

Re: Time formats in cube views

Thanks for the suggestions Maren + Wim,

Unfortunately I think you're right in that it can't be done with native number formats :(

Rob
by schmrob
Mon Mar 07, 2022 2:02 am
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: Time formats in cube views
Replies: 7
Views: 1650

Re: Time formats in cube views

Hi Wim,

In general, all of them, but specifically PAW and/or TM1Web.
by schmrob
Fri Mar 04, 2022 4:04 am
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: Time formats in cube views
Replies: 7
Views: 1650

Time formats in cube views

Hi All, I have some decimal hour values that I want to be able to display in hh:mm format. This works ok for values < 24 hours, but I'd like the aggregated numbers to display the same as Excel's [hh]:mm number format e.g. 1,234.75 hours in decimal hours should display as 1234:45 in hh:mm. Is this po...
by schmrob
Fri Oct 23, 2020 12:58 pm
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: OptimusPy - Ideal dimension order finder
Replies: 15
Views: 6657

Re: OptimusPy - Ideal dimension order finder

duh, of course - thanks for the reminder of why!
by schmrob
Fri Oct 23, 2020 3:30 am
Forum: IBM TM1, Planning Analytics, PAx and PAW
Topic: OptimusPy - Ideal dimension order finder
Replies: 15
Views: 6657

Re: OptimusPy - Ideal dimension order finder

this might be a bit of a newb question but are there any issues caused by OptimusPy when it moves the measures dimension to a position other than the last?

Regards,

Rob