Inconsistency between SOAP service and ad-hoc reporting

2013-06-28 Thread Dorian Kind
Hi all, I noticed that newly created ads containing a headline or a description line starting with whitespace will be trimmed automatically, e.g. when creating a TextAd like so: {'ad': { 'headline': ' My headline', 'description1': 'A description', 'description2': 'More description', 'd

Re: Inconsistency between SOAP service and ad-hoc reporting

2013-06-28 Thread Dorian Kind
Update: I fiddled around some more, and it turns out this has nothing to do with the trimming. The issue is that in CSV reports, fields that start with a hyphen are prepended with a space. For example: I created an ad in the Web UI, starting the text lines with different interpunctuation symbols

Re: Inconsistency between SOAP service and ad-hoc reporting

2013-07-02 Thread Anash P. Oommen (AdWords API Team)
Hi Dorian, I'll investigate this at my end. The CSV reports shouldn't be different from xml reports. Cheers, Anash P. Oommen AdWords API Advisor On Friday, June 28, 2013 5:38:29 PM UTC+5:30, Dorian Kind wrote: > > Update: I fiddled around some more, and it turns out this has nothing to > do wi

Re: Inconsistency between SOAP service and ad-hoc reporting

2013-07-17 Thread Dorian Kind
I just realized that this might be connected to the way that the "Total" row is formatted (which is not available in XML reports). There, values that cannot be aggregated are indicated with the string ' --', two hyphens preceded by a space. Maybe the logic that inserts the spaces in the "Total"

Re: Inconsistency between SOAP service and ad-hoc reporting

2013-08-29 Thread Dorian Kind
If anyone else stumbles upon this, the described behavior is still in effect. Any attributes that start with a hyphen are prepended with a space character in CSV reports. Workaround is to simply trim the values, as (to the best of my knowledge) attributes cannot start with a space. On Wednesda