Aliya Walji wrote: > AccountingRules.RoundingRule=CEILING > AccountingRules.AmountToBeRoundedTo=1 > > It seems a bit confusing to have the default configuration file not > include all of the values you can modify. Is there any reason that > this can't be in the default file? It makes it much easier for a > user to just copy the file, rename it, and change the relevant values > they want to configure, without having to read a document about what > additional things they can add (and potentially making errors adding > these additional options into the file). > > Is it possible to have these added to the default file or will this > cause technical issues based on the way things are stored in the DB?
I agree that the current state of affairs is not ideal. Two possible options would be as follows: 1) add the 2 values mentioned above to the default configuration file. In this case, there would no longer be per currency defaults, but rather single global defaults. If that's ok functionally, then it could be done. If we took this course then we need to decide if it is worth putting time in to remove the default values from the database or leave them there unused. 2) add the 2 values mentioned above to the default configuration file, but commented out for documentation purposes. In this case everything stays as is (with per currency defaults) and the override values could just be copied and uncommented in the custom file if needed. --Van ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
