About Darin_Seibel

The best way to hold a system time date is to have a time system module with time as a dimension and boolean lines to flag which dates are in the past and what the present date is. To do so, set the Current Day boolean up to have the current day marked using a formula reference to the dates in the past boolean - something like 'PREVIOUS(Day in Past) AND NOT Day in Past'. Create an action that imports a saved view of that module into itself, mapping the Current Day over to the Day in Past. If you can automate and schedule that process to occur daily you'll have a cross reference to a current date you can use in your process here.  ... View more

@DavidSmith Thank you! This up-ends a lot of our original notions of best planning practices. One other potential myth I've heard is that a hyphen-format for zero-value lines uses slightly less memory than a Zero. Is that true? ... View more

I agree. Especially for financial planning summary grids there's a need to display some comments as notes on the narrative behind the value, why it's changed since last time, what other assumptions are factored, etc. Just like the notes feature was added to the Settings end of Lists and Modules, a Notes functionality is needed on the user end. Perhaps function where a boolean is checked within the module to open up a new text field to become available for the intersection of the each of the module's line items and dimensions. The boolean would help control sparsity for where comments are not needed. ... View more