Adding some more context - If users can delete items from the list, they can unwillingly delete data from other versions and prior years. This creates a data integrity issue and makes it very difficult to utilize the worksheet and this valuable capability in a production system.
... View more
Something I had to do a client was create a "Cascading" sign flip that worked Tops down the composite hierarchy and allowed the Admin to selectively override the the "Flip" of the parent. So a user could work down the hierarchy, but maintain branches where the exceptions occur to effectively create custom rules with the least amount of maintenance possible. The Parent "Flip" is brought down to the Child list as a calc line item with a lookup which is contained in an algorithm that also refers to a floor level line item that lets the user override the "Flip". So the "Calc Flip" line item formula follows as: "IF Sign Flip = Sign Flip.Flip THEN Sign Flip.Flip ELSE IF Sign Flip = Sign Flip.'Un-Flip' THEN BLANK ELSE 'Acct L1 Sign Flip'.Sign Flip[LOOKUP: 'Acct L2 Properties'.'Acct L1']" The "Sign Flip" line item is used at floor level for the override and so on down the composite hierarchy. I created a dashboard with all the floor level sign flip modules so users can navigate the hierarchy and only effect the nodes where necessary. For this client I built this module in the Hub, and cascading flip logic was pulled into the Account level Transaction data before it was imported into the Spoke FP&A model.
... View more