Well, In the scripts you don't enter a monetary value but a floating point value. When Google multiplies that by 1,000,000 and rounds that to the nearest integer, information will get lost - and I'm not even speaking of the case where an overflow occurs because the multiplied value cannot be stored in an int64. I really hope that Google considers compatibility on their decision, it's been like this for over 7.5 years.
Now can you tell what kind of formatting issues you ran into? On Monday, December 10, 2012 8:47:57 AM UTC+1, MT wrote: > > I don't see any benefit in having one monetary value returned in a > different format than all the others, it's just illogical and makes it more > difficult to code. I develop a reporting tool used by hundreds of companies > around the world, I can't instruct them all to change their conversion > scripts to use micros, it has to be done by Google. > > On Sunday, 9 December 2012 14:09:51 UTC+2, Zweitze wrote: >> >> I hope that request will be rejected. As I understand totalConvValue is >> just the sum of the *exact* values that were posted by the conversion >> scripts. >> If you want micros in totalConvValue then your conversion scripts should >> set the values in micros instead of something else. >> >> BTW: >> *It's quite problematic working with this field, because the number >> formatting varies depending on the account currency and regional settings. >> * >> Can you elaborate on that? I work with many accounts from different >> countries, but the number formatting appears to be the same (EN-US) >> regardless the currency or region. Note that I retrieve all these numbers >> solely in reports, downloaded in XML format. >> >> >> Op dinsdag 27 november 2012 14:53:39 UTC+1 schreef Paul Matthews het >> volgende: >>> >>> Hi MT, >>> >>> I've re-introduced this feature request. As soon as we have any >>> information, we'll post it in this thread. >>> >>> Regards, >>> >>> Paul Matthews. >>> >>> On Tuesday, 27 November 2012 07:49:17 UTC, MT wrote: >>>> >>>> Two years and no change on this. It's quite problematic working with >>>> this field, because the number formatting varies depending on the account >>>> currency and regional settings. Will this be changed to micros at some >>>> point? >>>> >>>> On Monday, 15 November 2010 21:36:17 UTC+2, AdWords API Advisor wrote: >>>>> >>>>> Hi David, >>>>> >>>>> Thank you for reporting this issue. I think the root of the problem >>>>> is that getReportFields() returns the field TotalConvValue as the type >>>>> Long. The returnMoneyInMicros header only affects Bid and Money >>>>> fields, which is why TotalConvValue isn't affected currently. I'll >>>>> work with the core engineering team to change this to a Money type, >>>>> but I don't have an estimate as to when that change will be made. >>>>> >>>>> Best, >>>>> - Eric Koleda, AdWords API Team >>>>> >>>>> On Nov 12, 4:00 am, DaveOz <[email protected]> wrote: >>>>> > Hi, >>>>> > I've set returnMoneyInMicros: true in my http headers when >>>>> requesting >>>>> > report downloads (v201008 API) and modified my code to expect all >>>>> > monetary values to be returned in micros from the >>>>> > ReportDefinitionService. >>>>> > Most fields like maxCPC & avgCPC are indeed now returned in micros. >>>>> > >>>>> > However, I still get sent totalConvValue in currency units (pounds >>>>> in >>>>> > my case). >>>>> > >>>>> > Is this working as designed? If so, is it documented somewhere which >>>>> > monetary values will be switching to micros and which aren't? >>>>> > >>>>> > Thanks, >>>>> > David >>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
