TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
  
Question about decimal precision limits and work arounds
I’m running into a precision issue that’s causing some headaches with my real estate data. I’ve got GIS property area measurements that come in with 8 decimal places from the county (standard for this type of data), but TeamDesk seems to be truncating them down to 6 decimals.

The problem is that I’m doing analysis where every square foot counts for valuation calculations. When I’m calculating price per square foot or analyzing ROI across multiple properties, those missing decimal places are throwing off my numbers compared to what I get from the source data.

For example, a property might actually be 5665.53895912 sq ft, but TeamDesk shows it as 5665.538959. Doesn’t seem like much, but when you’re multiplying by market rates and doing portfolio analysis, the numbers start to drift.

Is there any way to get TeamDesk to handle more than 6 decimal places? Maybe a different field type or setting I’m missing? With the 6-decimal limit, I don’t really have a way to work around this without exporting everything to Excel for calculations, which defeats the purpose of having it in TeamDesk.

Any ideas would be awesome!
Thanks!
ID
2121
Category
TeamDesk
Author

L. C. Parker
Date Created
8/22/2025 8:03:03 PM
Date Updated
9/3/2025 5:57:32 AM
Comments
basenine 8/22/2025 8:37:25 PM
I’d try adding the full GIS values into a text field, then asking chatGPT to write a script that takes these values and converts them to the correct area (as a numeric) and then adds it to a dedicated sq foot field (innerHTML) or POST via the api
basenine 8/22/2025 10:05:17 PM
Sorry...misread your requirements...

I'd use the same idea but price x GIS value --> to Total Value
Nick Kemp 9/3/2025 5:57:32 AM
Hi there!

This is a common problem with currency. The approach I'd take is to store as Numeric and multiply by 100,000,000 - store that. So the number in your example would be 566553895912. Use a formula column to present it nicely to the user. I'm not sure what the max size is for the column, you'd have to check with support.

If you're constrained there, then you'd just have to break it out into seperate columns for each side of the point. Or this might be a good idea to make the UI not weird!

Hope that is helpful :)
Feedback
Back to Search Results