About Hugo

This has also been a real issue for us. Our contractors that have build our biggest model have use native Anaplan time dimension and configured it to match our calendar. We found out the hard way when 2020 did not have a Week 53. As a quick fix we moved our volume from Week 53 to Week 52 in the Datahub... but did not realized that the Anaplan Week 1 of 2021 would in fact be a Week 53 of 2020 on ISO Calendar, therefore all of our weeks are offset by 1... Contractor should have used Custom Time Dimension instead, and it will be a massive work to change/convert all modules without loosing data. ... View more

A technical way for Anaplan to build this would have been to have the ability to tie a LineItem_A (ie: Input Number) to another "Text" LineItem_B (Comment) providing they are of same Dimensions. Then on the UI, similar to Excel, have the ability to right-click on LineItem_A and select "notes" and type (or read) in the pop-up box the comment from LineItem_B associated to that LineItem_A cell.   But the idea to store the information outside the model is infinitely better from a sparsity standpoint... but will be more complex to implement.   This feature would be of tremendous use when documenting the Planning/Forecasting Inputs. I feel like right now, the lack of this ability is a show-stopper on many user-stories from our end-users' feedbacks. ... View more

Keep it up Anaplan Team... Adding .xlsx is Great news to our user (and super-user) base!! Hopefully, by adding this XML formatting export, it allowed you to also be able to bring in the backcolor of conditional formatting in the exported file as well 🙂 ... View more