Thanks, I will add my thoughts on the other thread.

I am not sure what you mean by " The reference document for each object 
state if a field can be null or not (AdGroup.name 
<https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupService.AdGroup#name>
 for 
example)". This is not about API objects, this is about report fields. Most 
report fields do not have a counterpart in API objects. Just think of 
ClickType or Conversions. Can they be null? I can imagine Conversions being 
NULL in accounts where no conversions are defined. But it's hard to test, 
you have to create a new account with credit card info etc., then direct 
traffic to it. It's quite an effort.

What makes this issue worse is that reporting is updated more often than 
the regular AdWords API, and the time given to us developers is much 
smaller. (For instance, this breaking change 
<http://googleadsdeveloper.blogspot.nl/2016/10/changes-to-clicktype-field.html> 
gives developers just 40 days to develop the necessary changes. In those 40 
days the development efforts cannot be fully tested since the announced 
change cannot be tested in advance. So we have to depend on all available 
information.)

Summary: I want nullable documentation for every report field. Just like 
"Type", "Display Name", "Behavior" etc., another attribute "Can be NULL" 
which just says True or False - and maybe some information in which 
circumstances this field will be NULL.

Can you pass this request?



On Wednesday, October 26, 2016 at 6:30:46 PM UTC+2, Shwetha Vastrad 
(AdWords API Team) wrote:
>
> Hi Zweitze,
>
> We are working on making the reporting of null values for String fields 
> more consistent. The reference document for each object state if a field 
> can be null or not (AdGroup.name 
> <https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupService.AdGroup#name>
>  for 
> example). The Path1 and Path2 fields for an Expanded Text ads are optional 
> at the moment. So, null values for these fields would be returned as "--" 
> in reports which would be difficult to distinguish from Path fields with 
> "--" as the text. There is another thread 
> <https://groups.google.com/d/msg/adwords-api/oMp-wuyyINs/NiYyOVxOAgAJ> on 
> the forum where a similar discussion is going on. You could provide your 
> inputs on that thread as well. I'll pass this along to the team and keep 
> you updated. 
>
> Regards,
> Shwetha, 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/4e432baf-43e5-4d97-bf4b-24cdf5e6dd99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • How to deal wit... Zweitze
    • Re: How to... 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
      • Re: Ho... Zweitze
        • Re... 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum

Reply via email to