Hello Mark,

I have good news! With the release of v201607 
<https://developers.google.com/adwords/api/docs/reference/#v201607>, there 
was a change made to reporting outlined under the section Quoting of values 
in comma-separated output 
<https://developers.google.com/adwords/api/docs/reference/#reporting> where 
fields 
that begin with the special characters - (minus) or + (plus) will be 
double-quoted without a leading space in the CSV, CSVFOREXCEL, and TSV 
download formats. To get this new behavior, you would have to start using 
v201607. Versions v201605 and older still behave the same as it did 
previously as to not break people's current reports.

Cheers,
Nadine, AdWords API Team

On Thursday, June 23, 2016 at 12:36:34 PM UTC-4, Mark Rogoyski wrote:
>
> Hi Josh,
>
> Thanks for the update.
>
> Mark
>
> On Thursday, June 23, 2016 at 8:53:36 AM UTC-7, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Mark,
>>
>> We're still discussing whether to make this change. If we do change the 
>> behavior, it will most likely happen starting with a specific AdWords API 
>> version to avoid creating problems for anyone who is relying on the current 
>> behavior.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, June 22, 2016 at 5:00:38 AM UTC-4, Thanet Knack 
>> Praneenararat (AdWords API Team) wrote:
>>>
>>> Hello Mark,
>>>
>>> I would like to update that we're aware of the issue and discussing 
>>> about the feasibility/timing of the change.
>>> Could you please wait a bit more before we reach the conclusion?
>>>
>>> We'll update this thread as soon as possible.
>>>
>>> Cheers,
>>> Thanet, AdWords API Team
>>>
>>> On Wednesday, June 22, 2016 at 2:57:26 AM UTC+9, Mark Rogoyski wrote:
>>>>
>>>> Hi Josh,
>>>>
>>>> Thank you for the explanation.
>>>>
>>>> I could understand if this leading space was added to any CSV reports 
>>>> downloaded from the UI, but the API is meant for computers and automated 
>>>> systems to consume data, so it seems kind of unnecessary to implement 
>>>> workarounds for a human loading into Excel when this isn't the use case 
>>>> for 
>>>> the API.
>>>>
>>>> Could this behavior be removed from the API?
>>>>
>>>> Thanks.
>>>> Mark
>>>>
>>>> On Tuesday, June 21, 2016 at 10:11:08 AM UTC-7, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi Mark,
>>>>>
>>>>> I found a bit more background on this one. The reason reporting adds a 
>>>>> leading space for that particular *VideoId* in CSV format is if a 
>>>>> user imports the CSV into Excel and the value begins with a hyphen (-), 
>>>>> Excel will interpret the field as a formula unless it has a leading 
>>>>> space. 
>>>>> To avoid this problem, the reporting service adds a leading space to any 
>>>>> field value that would cause issues in Excel without the space.
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Tuesday, June 14, 2016 at 5:02:37 PM UTC-4, Josh Radcliff (AdWords 
>>>>> API Team) wrote:
>>>>>>
>>>>>> Hi Mark,
>>>>>>
>>>>>> I'm responding here just in case others encounter this issue. I'm 
>>>>>> following up with the reporting team and will get back to you as soon as 
>>>>>> I 
>>>>>> have more information.
>>>>>>
>>>>>> In the meantime, I suggest trimming leading and trailing spaces from 
>>>>>> *VideoId* field values as a workaround.
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Monday, June 13, 2016 at 8:29:04 PM UTC-4, Anthony Madrigal wrote:
>>>>>>>
>>>>>>> Hi Mark,
>>>>>>>
>>>>>>> I'll be glad to take a look at what is going on here. You can send 
>>>>>>> me the details privately via *reply privately to author. *Please 
>>>>>>> provide the report definition, clientCustomerId and some video Ids you 
>>>>>>> expect to see.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Anthony
>>>>>>> AdWords API Team
>>>>>>>
>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/bc67a8f2-5773-492e-9e25-c0b8c47810db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • YouT... Mark Rogoyski
    • ... 'Anthony Madrigal' via AdWords API Forum
      • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
        • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
          • ... Mark Rogoyski
            • ... 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum
              • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... Mark Rogoyski
                • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
                • ... Mark Rogoyski

Reply via email to