Calculated Fields Rounding (Allow calculated properties to display a whole number)

The current behavior for calculated properties is to round to two (or more) decimal places. It would be helpful to instead allow results to be rounded to the nearest whole number (an integer) – instead of two decimal places. Even better would be to either round or adjust decimal places up or down like in Excel.

 

This would allow more flexibility when presenting data as a Report in a Dashboard. Usually in a chart or other visualization showing accuracy down to .01 is unnecessary.

 

Stated differently, please add the ability to adjust calculated properties to either display a whole number or precisely specify the number of decimal places.

HubSpot updates
Status updated to: Being Reviewed
Dec 2, 2020

Hi all, I'm Jeff from the HubSpot product team.

 

Thanks for this feedback. Improving calculation property functionality is under consideration for upcoming roadmap. No definite timetable or changes yet, but please keep the upvotes and use cases coming. It helps with designing a solution and prioritizing.

 

Thanks!

jeff

16 Replies
New Contributor

Much needed!

New Contributor

Was also looking for this.

Occasional Contributor

Very much needed. At present I have a calculated property sitting at 5 decimal places. I'd be happy with even two at this point. 

Capture2.PNG

New Contributor

please, please, please! add this in as a capability! 🙂 

New Contributor

does anyone have a work around for this, or suggestion for what to do instead?

 

we have caluclation properties that are currency fields, and some of the values are appearing as $208,916.668

 

that looks pretty funny as a $$ amount. 

 

please let me know if you've figured out a hacky way to fix this!

Advisor | Platinum Partner

Not having the ability to control the # of decimals makes the reporting or viewing the calculated property in the contact, company, or deal views look very funny. 

 

Please add this feature!

New Contributor

Yes please add this feature...

Top Contributor | Platinum Partner

Agreed that this is very important - both the number of decimal points and the number format of the decimal points are important as we work in a multi-language, multi-country portal where some countries view 1.2 as different numbers.

Occasional Contributor

Is there a status on this update? It's impossible to compare dollar figures when one is an input and another is a calculation that is 5 decimals long and not-rounded. 

Please add this feature! Salesforce has multiple options in this area. 

Regular Contributor

It would also be important to solve the problems with the decimals in the reports. When averages are calculated, the result is displayed with many decimal places.

New Contributor

yes much useful for effective reports

Regular Contributor

I'm thinking I'll have the calculated property, then have a workflow assign that calculated value to another property each time there's a re-calculation. When decimals appear, we can manually round the non-calculated property up or down. Should work when only a few deals have a qty.5.

 

Zapier should be able to do it automatically, though.

Status updated to: Being Reviewed
HubSpot Product Team

Hi all, I'm Jeff from the HubSpot product team.

 

Thanks for this feedback. Improving calculation property functionality is under consideration for upcoming roadmap. No definite timetable or changes yet, but please keep the upvotes and use cases coming. It helps with designing a solution and prioritizing.

 

Thanks!

jeff

New Contributor

Much needed - the ticket ID's are way to long to use a a reference and there is no way to create a Unique ID for the team to use for reference to the service tickets making it challenging to create greater than 5 or so tickets to an associated Object

 

The calculation field divideds the ticket ID by 100,000 making a 4 digit number if the abiltiy to round existed - I would also want to be able to set the format to not include the comma - similiar to how ticket tracking in Jira is done

Regular Contributor

Much needed but not just for calculated properties. Please implement this in the Reporting too (specifically Advanced Reporting). See below, it is silly to have 7 or 9 decimals in reports.

 

Screenshot 2021-01-08 at 13.03.13.png

New Contributor

much needed!