As a best practice, rounding should not be done as stored values within the database.
Since every external report is required to foot, that could mean dozens, hundreds, thousands of members that hold data that is not of any real financial value. It requires rules to figure differences, they are not easy, and these rules impact performance. Additionally, the maintenance of applications that have this are cumbersome.
Another reason not to do this - think how this could make updating structures in OneStream when you have to consider how that impacts your rounding rules. You have taken away one of the real benefits of OneStream, being able to update your structures and made it a risk.
Reports are just a better place to handle this. They are better because you can determine what line to plug the rounding amount, and make reports that are easier to foot across and down.
Hey Eric, when you say that "reports are a better place to handle this" what exactly are you proposing? Is there a way to do a series of getdatacells on the reports themselves to make this work?
Appreciate the help!
