{"section":"known-issues","requestedLocale":"en","requestedSlug":"rounding-of-totalvalue-in-listorders","locale":"en","slug":"rounding-of-totalvalue-in-listorders","path":"docs/en/known-issues/Order Management/rounding-of-totalvalue-in-listorders.md","branch":"main","content":"## Summary\n\nWhen we query the `totalValue` of some orders using the GET ListOrders route, we may come across discrepant values to the values returned in Get Order. This is because the listOrder route queries the Solr database which has the `totalValue` field defined as float, which can generate inaccurate numbers due to its approximation/rounding nature.\n\nOn the other hand, in the GET Order route, the queried database is set to integer, so the return does not behave in the same way as the List Order route.\n\nThe consequence of this is that the list API can return values with different decimals when the value is too high.\nAnother side effect of this scenario is the display of `totalValue `with “.0” in the list orders.\n\n## Simulation\n\nThere is no way to simulate the scenario, but it can occur in orders with a very high value or scenarios with coins with many zeros;\n\n## Workaround\n\nWe don't have a WA yet."}