The benefit of having formulas as field values is that you could enable the user to select a formula from a listbox. e.g. Field [FORMULAS] has the values SUM(SALES), AVG(SALES), COUNT(SALESORDER). So you could have one straight/pivot table with a dimension and one (dynamic) expression that calculates the formula that the user selects in a listbox next to the table object (or triggered by some conditions).
Actually, I dont see so much of a benefit in this (unless the business demands something like described above). I prefer to store formulas in Variables or (in my case) not even store them at all, as in 95% of my cases you would like to modify the formula anyway -if by Set Analysis or integration in Aggr() functions...I always prefer to see as much of the complete expression clearly in the editor....but I agree that in big/standardized projects it makes sense to work with centrally stored expression (=in variables)
The benefit of having formulas as field values is that you could enable the user to select a formula from a listbox. e.g. Field [FORMULAS] has the values SUM(SALES), AVG(SALES), COUNT(SALESORDER). So you could have one straight/pivot table with a dimension and one (dynamic) expression that calculates the formula that the user selects in a listbox next to the table object (or triggered by some conditions).
Actually, I dont see so much of a benefit in this (unless the business demands something like described above). I prefer to store formulas in Variables or (in my case) not even store them at all, as in 95% of my cases you would like to modify the formula anyway -if by Set Analysis or integration in Aggr() functions...I always prefer to see as much of the complete expression clearly in the editor....but I agree that in big/standardized projects it makes sense to work with centrally stored expression (=in variables)
