Hi,
It has been over 3 months since you confirmed the *CombinedRuleUserList *with
a ruleOperator of *AND *is not yet supported in the API V13 though
email("RE: Private message regarding: Upgrade CombinedRuleUserList
(ruleOperator = AND) to the new FlexibleRuleUserListInfo") .Besides, API
V14 also doesn’t support it.
You also confirmed that you raised a feature request with your wider team
for this. But we couldn’t see any mention of it in the latest release
notes Release Notes | Google Ads API | Google for Developers
<https://developers.google.com/google-ads/api/docs/release-notes>
We can get these data through API V12 but cannot through API V13/V14. It's
a breaking change and blocks us migrating to API V13/V14. It's a blocking
issue that needs to be fixed quickly, not just a feature request.
Could you let us know when the breaking change can be fixed?
On Wednesday, March 22, 2023 at 6:35:56 PM UTC+8 Google Ads API Forum
Advisor wrote:
> Hi Ye,
>
> Thank you for the reply.
>
> Upon checking, I can see that you are providing us the response logs.
> However, for our team to further check this and see the full picture of
> what you are doing, could you please provide us with the complete API logs (
> *request*
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>
> and *response*
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>
> with *request-id*
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>)
>
> generated on your end?
>
> Note that logs can be requested or provided to the developer handling the
> Google Ads API transactions when logging of the API requests has been
> enabled. You may check *here*
> <https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging>
>
> and click your client library for the specific guideline to enable it.
>
> For REST interface requests, you can enable logging via the curl command
> by using the -i flag. This will cause the tool to include the HTTP response
> headers in the output.
>
> You may then send the requested information via the Reply privately to
> author option. If this option is not available, you may send the details
> directly to our googleadsa...@google.com alias instead
>
> Best regards,
> [image: Google Logo] Google Ads API Team
>
> ref:_00D1U1174p._5004Q2k1HLI:ref
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/d255b5ab-d4da-4814-b5f2-35738508b37en%40googlegroups.com.
