Bakkone wrote: ↑Mon Aug 26, 2019 12:54 pm
Sounds interesting. Personally I think they should find something that actually CAN replace the TI part. Otherwise we will have three different "languages".
I'm not sure that would be possible or even desirable. Hubert said that his intention was to provide an alternative to what people are currently doing on the Prolog and Epilog tabs.
However the present TI language is
internal to the server. In data and metadata it's not just a scripting language reading a file line by line and writing it up, but it's also (for example) doing things like optimising the locking within the model and handling contention and, if necessary, rollback.
Bakkone wrote: ↑Mon Aug 26, 2019 12:54 pm
But I always tend to think about things like Canvas and all these other things beeing developed on top of the api. As much as I love it. I always wonder about customers using other frontends lowers the threshold to just move onto a different platform altogether. Im sure there are peoplpe at cubewise putting together the final pieces to make Canvas its own planning product with a javascript/MongoDB backend instead of TM1.
I'd be less certain about that. The server is one of two things that has always been at the heart of TM1; its performance, power and flexibility, its ability to handle ragged
hierarchies (AAAARGH! Don't say "Hierarchies"!) ragged
consolidation trees with ease compared to many other solutions, the writeback ability and so on. It's not possible to just whack another DB on the back end and get all of that.
The other thing is of course Excel integration; the ability to quickly and flexibly create ad hoc reports that draw from multiple cubes and multiple servers. The ability to create upload sheets where you just create a block of formulas, point them to the values that you've dumped into Excel from elsewhere and hit F9, etc.
I'm not disparaging Canvas at all; I think it's an impressive product. (The very thought of PAW and how it has been implemented, on the other hand, has me reaching for the Imodium.) But regardless, not everything lends itself to a web based front end anyway. That's why I think that the reintegration of the TM1 and Cognos front end teams is a net negative for us out here in customer-land. The Cognos team seems to be only capable of thinking in terms of "Pretty! Dashboards! Ooooooh, Preeeeeety! Reports!" and that
isn't where the heart of the power (or appeal) of TM1 has ever been. It's a sideshow, not the main event.
But they seem to be incapable of seeing that which is why
{exasperated sigh} two years down the track we still,
STILL don't have hierarchy-aware DBRW formulas and are still not seeing them on the horizon.