About Aaron82

I'm experiencing the same obstacle with a new model we are developing for Operating Expense forecasting and planning. Our corporate functions plan at the Cost Center level (not always) and if we go the balanced route our hierarchy will go down 9 levels. It creates a lot of dummy clicks for our users and something we really don't want to do.  ... View more

This would be an awesome feature for model development.  ... View more

Hi Nicole. It'd be great to connect with other Anaplanner's in the area. We are based in Wilsonville. Our model is FP&A/corporate finance user based. ... View more

Awesome updates. But hoping for more robust additions to formatting capabilities to make the new UX a one stop shop for our corporate reporting. Grid formatting in particular for adding fill colors, bold values, add/edit borders, fix alignment, make things easier and more pleasing to read, etc. We don't keep everything white when delivering it to end users.  ... View more

This would save a good amount of time building out dashboards that are long. ... View more

Very helpful for learning how to build out using existing views and developing best practices for the new UX.  ... View more

Hi Davrae, It looks like the logic may need adjustment. Try this. IF Dept Code >= 0000 AND Dept Code <= 5999 OR Dept Code = 6500 OR >= 7000 AND Dept Code <=7199 THEN UPG Admin FB Rates.Fringe Rate[LOOKUP: Staff Types (UPG)] ELSE IF Dept Code >= 6000 AND Dept Code <= 6999 THEN UPG CPG Fringe Rates.Fringe Rates[LOOKUP: Staff Types (UPG)] ELSE IF Dept Code >= 8700 AND Dept Code <= 8799 THEN UPG RPCN Fringe Rates.Fringe Rate[LOOKUP: Staff Types (UPG)] ELSE IF Dept Code >= 8000 AND Dept Code <= 8600 THEN UPG RPCS Fringe Rates.Fringe Rate[LOOKUP: Staff Types(UPG)] ELSE 0 ... View more

Must read for beginner and intermediate model builders. This will build good habits and save you headaches later on.  Can't stress the importance of naming conventions, blank list/module separators, and contents bar management. When you get building full speed, things get unorganized quickly. If importing from databases or using number lists, always use a code or unique identifier. If you are building out a model from the ground up, I highly recommend using a boolean time reference module to manage time filters. Happy model building. ... View more