Problem with diacritics in campaign name

[lukas.benes]

Hello

I have problem with characters with caron, for eg.: s with caron, c
with caron, etc...
This problem is only in Campaign service! In AdGroup and Ad Service
is this ok.

#request

<addCampaignList>
<campaign>
<name>šem z toho srnka</name>
....
</campaign>
</addCampaignList>

#response
soapenv:Server.userException
One or more input elements failed validation.
code: 122
Message: One or more input elements failed validation
Index: 0
Field: name
Trigger: &#x161;em z toho srnka
Code: 36
isExemptable: false
Detail: These characters are not allowed: &#x161;


Thank You

[AdWords API Advisor]

Hello Lukas,

How are you accessing the API--are you using a client library or
directly via a SOAP toolkit? Which language are you using?

Cheers,
-Jeff Posnick, AdWords API Team

[lukas.benes]

Hello

We are using nuSOAP (via PHP) and UTF-8 encoding (we also tried non
multibyte encodings liek ISO-8859-1 and WINDOWS-1250, but with same
result )

We have problem only with campaigns names, in adgroups or ads is
everything ok.
On our side is no difference between code, that we are using for
CampaignsService and other Services (i mean encoding and etc.)



On 23 Čen, 17:58, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:

[AdWords API Advisor]

Hello Lukas,

I'm able to successfully create campaigns with "š" in their names in
my tests. I tried by directly sending an XML document with the XML
entity &#x161; and also using the APIlity PHP client library (which I
believe uses NuSOAP under the hood), specifying a PHP string with the
"š" character and letting PHP encode the XML entity for me.

I don't think there should be anything account specific that limits
this, but to cover all bases, have you tried creating a campaign in
that account with that character in it via the AdWords web interface?

Cheers,
-Jeff Posnick, AdWords API Team

[Hypper]

Hello!

Same problem with V11, russian characters with UTF-8 in Sandbox.
While i try to create campaign I have this error.
I've got this problem just today. About month or more i didn't use
Sandbox. Earlyer i didn't get this problem.

Request:
<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<useragent env:mustUnderstand="0">Playing with the API from
ruby</useragent>
<developerToken env:mustUnderstand="0">XXXXXXXXXXX</developerToken>
<password env:mustUnderstand="0">XXXXXXXXXXX</password>
<clientEmail env:mustUnderstand="0">XXXXXXXXXXX</clientEmail>
<email env:mustUnderstand="0">XXXXXXXXXXX</email>
</env:Header>
<env:Body>
<n1:addCampaign xmlns:n1="https://adwords.google.com/api/adwords/v11">
<n1:campaign>
<n1:budgetOptimizerSettings
xsi:nil="true"></n1:budgetOptimizerSettings>
<n1:dailyBudget>1000000000</n1:dailyBudget>
<n1:enableSeparateContentBids
xsi:nil="true"></n1:enableSeparateContentBids>
<n1:geoTargeting xsi:nil="true"></n1:geoTargeting>
<n1:id xsi:nil="true"></n1:id>
<n1:languageTargeting xsi:nil="true"></n1:languageTargeting>
<n1:name>Продаем слон</n1:name>
<n1:networkTargeting xsi:nil="true"></n1:networkTargeting>
<n1:schedule xsi:nil="true"></n1:schedule>
<n1:status xsi:nil="true"></n1:status>
</n1:campaign>
</n1:addCampaign>
</env:Body>
</env:Envelope>

Response:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<responseTime
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
xmlns="https://adwords.google.com/api/adwords/v11">45</responseTime>
<operations
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
xmlns="https://adwords.google.com/api/adwords/v11">1</operations>
<units soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
xmlns="https://adwords.google.com/api/adwords/v11">1</units>
<requestId soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
xmlns="https://adwords.google.com/api/adwords/v11">6fb5dec7a6ce521ae0833ff7d9bf0c5e</requestId>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>One or more input elements failed
validation.</faultstring>
<detail>
<ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/v11">
<ns1:code>122</ns1:code>
<ns1:message>One or more input elements failed
validation.</ns1:message>
<ns1:errors>
<ns1:index>0</ns1:index>
<ns1:field>name</ns1:field>
<ns1:trigger>&#x41F;&#x440;&#x43E;&#x434;&#x430;&#x435;&#x43C;
&#x441;&#x43B;&#x43E;&#x43D;</ns1:trigger>
<ns1:code>36</ns1:code>
<ns1:isExemptable>false</ns1:isExemptable>
<ns1:detail>These characters are not allowed: &#x41F;, &#x430;,
&#x434;, &#x435;, &#x43B;, &#x43C;, &#x43D;, &#x43E;, &#x440;,
&#x441;</ns1:detail>
</ns1:errors>
</ns1:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

lukas.benes пишет:

--
Успехов!

[AdWords API Advisor]

Hello,

I can confirm that the Sandbox is rejecting those Cyrillic characters
in Campaign names. If you send the same request to the Production
servers it should go through without issue.

The Sandbox should match the validation logic in Production, and
those characters should be considered valid, so there's something
amiss in the Sandbox. I'll let the core engineering team know and see
if there is a difference in configuration somewhere.

Thanks for sending along that sample.

Cheers,
-Jeff Posnick, AdWords API Team

[Hypper]

Hello!

Problem still not solved in Sandbox. Would you let me now if problem
just ignored?

AdWords API Advisor пишет:

--
CU!

[AdWords API Advisor]

Hello Hypper,

I'm sorry that it's taking some time to get to the bottom of the
issue. There is a bug in with the engineering team regarding it and it
is not being ignored, no. It does sometimes take longer to resolve
issues with the Sandbox than with the production environment, and I'll
let you know when there's an update. Thanks for your patience in the
meantime.

Cheers,
-Jeff Posnick, AdWords API Team