Actually, I think this bug is a bit misleading. I believe actually the values in the report table are coerced to 1 decimal place. I beleive that the extension of an integer to one decimal place is actually of little consequence, however, there can be indicator values, expressed as a ratio, which become mangled by the coercion to a single decimal point. I believe there should at least be an option in the report table generation to allow the definer of the report table to determine how many decimal places should appear in the table. it is always easier to format the individual columns in Excel later on, if you need less decimal places. However, by coercing everything to one decimal point, the precision and accuracy of certain indicator values (whose values may be between 0 and 1) is severely compromised.
-- Report table exports/views should not have decimals for data element values https://bugs.launchpad.net/bugs/494415 You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. Status in DHIS 2 - District Health Information Software: Confirmed Bug description: Data element report table exports have decimal values although the database tables have not. _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
