Line Item format periods model builder able to limit rather than the model's maximum options
Problem: Formatting a line item to a time period, and selecting "Month" as the period results in all available Months in the model. This makes it so that if you have a multiple year model, the end user can select a period that extends beyond the time they are able to show impact (past), or in other instances attempt to make changes to a future state that is outlandishly far out (10 year forecast number direct adjustment at year 10)
- End users are complaining about seeing Prior Year months when they are forecasting was the catalyst for the post, but I obviously was able to come up with an additional scenario that could be applicable to the change.
Temporary solution(s): 1) Tough, deal with it, and select reasonable time slots. 2) Build a 'fake' drop down list, and hide values on the back end that correlate to the field to limit users ability to manipulate - downside, it is not very sustainable/easy to overlook during model roll over. 3) Build a numbered list like 2, but have the display name built around the current time - downside is it is somewhat complex to set up/not intuitive - not audit-able
Ideal solution: When selecting time period as a line item format, you also have a drop down that allows selection of Time Ranges built into the model, which would filter out all other options that don't fit inside the available option OR have the ability to reference another line item formatted as a boolean that has a time element which allows for more flexibility of the builder to create a formula to limit the displayed periods.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.