Marketo rounding figures? How to stop it? | Community
Skip to main content
A
Anonymous
May 1, 2018
Question

Marketo rounding figures? How to stop it?

  • May 1, 2018
  • 4 replies
  • 4885 views

Hi All,

Our Marketo instance is integrated with SFDC, which uses Data.com Clean for lead/data enhancement.

Recently some contacts were enhanced by adding their annual revenue, which triggered a bunch of API requests.  Turns out Marketo was rounding the annual revenue and syncing it.... SFDC was seeing the change and pulling it's preferred number from Clean... and on and on. 

Here's the actual text from our SFDC admin.   Is there any setting that toggles on/off this rounding function?  Or any other suggestions?  Thanks!

XXXXXX was a lead in the system over the weekend clean set the Annual revenue to $108,598,708.00. However yesterday Marketo decided to change this value to 108,599,000.00. It appears clean detected this as a change and has moved it back to $108,598,708.00. Any idea why Marketo would have changed that value in the system? They are going to just keep conflicting with each other and making changes back and forth to round the value out?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

Jim_Thao7
Jim_Thao7
Level 8
May 1, 2018

Have you tried to find out the source of the change in Marketo? Activity logs for CDV, etc.? Any details on the sync activity and what was actually pushed to SFDC? Is this the Annual Revenue field on the Company object?  Is this issue happening on a Lead or Contact? Do note that Account sync is 1 way, SFDC>Marketo if the record affected is a Contact.

A
Anonymous
May 1, 2018

Yes, Annual Revenue is a Company field and this particular example is a Lead.

Activity Log records the change:

But when you go to the Company Info tab:

No instance of rounding or any other change is noted in the Activity Log.

Jim_Thao7
Jim_Thao7
Level 8
May 1, 2018

I would strongly suggest to keep troubleshooting and find the root cause of why it was changed to that value in Marketo.  There definitely has to be a reason why that changed and Marketo should not be automatically changing string values for you that I'm aware of. 

BTW, is there a merge on this record? 

A
Anonymous
May 1, 2018

No merge.

Thanks.

Jim_Thao7
Jim_Thao7
Level 8
May 1, 2018

So I just ran a test, and it looks like SFDC is the culprit here.  I would strongly recommend reaching out to your SFDC admin to take a look at the Annual Revenue field and update it accordingly.

Sivaraman_Mani
Sivaraman_Mani
Level 2
May 9, 2018

It is an expected behavior and the issue is explained in the below document Currency type field is rounding off its value.

Annual revenue field is also of type "Currency"

SanfordWhiteman
SanfordWhiteman
Level 10
May 9, 2018

Dead/restricted link.

Also, this isn't "rounding" in the generally accepted meaning of the term. It's lossy fp math.

Like when

     .1 + .2 = 0.30000000000000004

we don't typically say that's "rounding" because for most people it appears to be a bizarrely failed attempt to gain accuracy, not a predictable loss of accuracy.

A
Anonymous
May 9, 2018

Hi all,

Here's the result of my support case submission:

Thank you for waiting patiently. I have checked with my Tier 3 and we have found out that it is an expected behavior. To sound more technical in detail, the "Annual Revenue" field is of type currency and in MySQL its considered to be a Float field. To be more simple, MySQL will automatically round the values in our current database structure.

You might ask us to tweak the structure to accept that value but its not feasible for us to do so as it would require a major overhaul of the database and it could cause a whole lot of implications that could even make the database to get crashed often. To be simple, database will become unstable and might cause a lot of issues.

We do have a work around for this. which is to change the field type to "string" . However, standard fields type cannot be changed. So, we suggest that you create a new custom field of type "String" and then have your desired value.

SanfordWhiteman
SanfordWhiteman
Level 10
May 9, 2018

and it could cause a whole lot of implications that could even make the database to get crashed often. To be simple, database will become unstable and might cause a lot of issues.

Laughing to keep from crying... I mean, just say "This is a legacy architectural decision and there are no plans to change it."   No need to throw any FUD into the discussion. Obviously if this were an exact Decimal  (or even Integer, even the IRS doesn't care about decimal points with annual revenue) it wouldn't be any less stable!

But what's still being obfuscated in the response is this isn't rounding as humans understand it.

When you use a (single precision) Float, 932,849,000 is stored in Marketo as 932,849,020.  Note the stored value has seemingly invented 20 more dollars out of nowhere. We don't call that rounding!

    Terms & ConditionsAccessibility statement

    Loading footer...