Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decimal place and Figure screw ups #29

Closed
GoogleCodeExporter opened this issue Aug 27, 2015 · 8 comments
Closed

Decimal place and Figure screw ups #29

GoogleCodeExporter opened this issue Aug 27, 2015 · 8 comments
Labels
auto-migrated Priority-Critical Type-Defect

Comments

@GoogleCodeExporter
Copy link
Contributor 

Please search through existing issues first to ensure that the bug has
not already been reported.

What steps will reproduce the problem?
1.Entering an amount with 4 decimal places screws up input
2.Entering a huge number beyond 2,100,000,000 does not register


What is the expected output? What do you see instead?
7.5569 -> 75,569.0000
Entering more than 2,100,000,000 gives and Invalid Amount Message

What version of the product are you using? On what operating system?
Online version of Bkper and on Windows 8.1 using Chrome 64 bits


Please provide any additional information below.

The above problem is annoying. Also, it would be good to include up to 8 
decimal places so that we can make accounting for bitcoin and other crypto 
currencies.

Crypto currencies often go beyond to tens of billion of units because of their 
small values.

Original issue reported on code.google.com by tre...@glocalex.com on 26 Apr 2015 at 6:33
@GoogleCodeExporter
Copy link
Contributor Author 

We prioritized this issue an fix it ASP.

Thanks for reporting.

Original comment by m...@nimbustecnologia.com.br on 26 Apr 2015 at 9:25

  • Changed state: Started

@GoogleCodeExporter
Copy link
Contributor Author

Original comment by m...@nimbustecnologia.com.br on 26 Apr 2015 at 9:26

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Contributor Author 

That was quick responsive. ;-)

It also gives me problem when importing from the google spreadsheet. It cuts it 
down to 2 decimal places. Basically figures all go haywire when it is set to 4 
decimal places. I have not tried 3 decimal places.

It would be good if you fix the above problem and increase it to 8 decimal 
places once you have fixed it.

Thanks.

Original comment by tre...@glocalex.com on 26 Apr 2015 at 10:24

@GoogleCodeExporter
Copy link
Contributor Author 

Allright!

We are going to increase to 8 decimal places and also review all Add-ons and 
API's to make sure it will work properly.

As soon as we have some update we keep you posted.

Cheers

Original comment by m...@nimbustecnologia.com.br on 26 Apr 2015 at 11:21

@GoogleCodeExporter
Copy link
Contributor Author 

Thank you very much. You guys are champions!

Don't forget the max input too, i.e.,  >>2.1 billion. ;-)

Original comment by tre...@glocalex.com on 26 Apr 2015 at 1:22

@GoogleCodeExporter
Copy link
Contributor Author 

Allright! :)

The max input is a  limitation of elastic index. We probably will be able to 
workround it and remove this validation. The only drawback is the big values 
not to be indexed, so, queries with values, for example, "val>3000000000" will 
not retrieve anything... but this is not such a big problem :)

Cheers!

Original comment by m...@nimbustecnologia.com.br on 26 Apr 2015 at 2:59

@GoogleCodeExporter
Copy link
Contributor Author

Original comment by m...@nimbustecnologia.com.br on 30 Apr 2015 at 7:09

@GoogleCodeExporter
Copy link
Contributor Author

Original comment by pe...@nimbustecnologia.com.br on 20 May 2015 at 8:01

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Critical Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter