Hello Asaf,
1. I don't think it has changed. In v201109, the corresponding service to
ManagedCustomerService was ServicedAccountService.
And ServicedAccountSelector.setCustomerIds accepts only numeric values.
2. No. It refers to the same account with or without dashes.
Best,
- Takeshi, AdWords API Team
2012年10月25日木曜日 20時42分29秒 UTC+9 Edward Bells:
>
> Hi,
>
> We are now using the new API version V201206 that replaced the previous
> version that will be sunset tomorrow.
>
> We recently began to receive errors when trying to authenticate with SE
> Account ID that includes '-', for example 111-222-333.
>
> In the previous version the convention the included dashes worked fine but
> now we get the exception ‘SelectorError.INVALID_PREDICATE_VALUE @
> serviceSelector’ when calling to the service 'ManagedCustomerService'.
>
> We’ve managed to find out that if the ID is changed in a way of removing
> the dashes (111-222-333 à 111222333) the authentication works as should.
>
> Two questions at this point:
>
> 1. Was this change communicated and performed with intention?
>
> 2. Is there any difference between the same Account ID but with or
> without dashes?
>
> I’d appreciate your quick reply.
>
> Thanks,
>
> Asaf
>
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
