david.harding · Senior Principal Product Manager · 
Reactions
-
Re: Announcing: Statement of Direction for Anaplan calculation engines
Hi @luke_e - a good resource on this topic is a webinar done with Nvidia on their adoption of Polaris: The first thing to say is that if Classic models are doing everything that you require, then the…1 -
Re: Announcing: Statement of Direction for Anaplan calculation engines
@andrewtye - From our analysis, even with all the workarounds for limited dimensionality in Classic models - almost all classic models are very Sparse. Yes, theoretically a model could be very dense …2 -
Re: PREVIOUSITEM() formula which is like PREVIOUS() but references a list item instead of time
Unlikely I'm afraid. The way in NEXT/PREVIOUS/OFFSET etc are implemented for the Classic engine are very specific to how Time is handled in the Classic engine. In Polaris, Time is implemented more ge…1 -
Re: Implementing Polaris: Lessons learned
Hi @gheiler - let me take that one as I think it is more of a question for Anaplan. There are some known issues at the moment with Model to Model import performance in Polaris. This is because Model …1 -
Re: Implementing Polaris: Lessons learned
Thank you @PhilippErkinger for all your efforts with that project and using Polaris. It is also thrilling for those of us involved in delivering Polaris to market to read this kind of post from an ex…2
