Migrating AdWords ReportDefinitionField to Google Ads API

[Dylan Sprayberry]

On the AdWords API our application uses the ReportDefinitionService getReportFields() method for each report to retrieve each field's exclusiveFields list. Our service retains that list locally to ensure reports can be configured only to include only compatible fields. In migrating to the Google Ads API, there appears to be no direct parallel for this functionality, and the GoogleAdsField returned by the GoogleAdsFieldService instead includes a selectable_with list that requires cross referencing the total list of available fields for each report to determine which fields must be excluded when a given field is selected. Are we missing an easy way to solve this problem, or was this functionality simply not recreated for the Google Ads API? If the latter, how would you recommend dynamically maintaining a list of fields that must be excluded from each other while adhering to the API's request limits?

[Google Ads API Forum Advisor]

Hi Dylan,

Thank you for reaching out to us. Let me do the best I can to assist you in this.

With regard to your concern, please do note that the GoogleAdsFieldService is similar to the AdWords API ReportDefinitionService, but instead of returning metadata for report types, it returns metadata for resources and resource views. For migrating reports from AdWords API to Google Ads API, you will need to cross reference the fields between the two APIs. We recommend our user to check this document which contains mapping list of fields between old and new API.

Regards,

Teejay Wennie Pimentel Google Ads API Team

ref:_00D1U1174p._5004Q2TlFkj:ref

[Dylan Sprayberry]

For others who might find this thread, the blog post here advises the best approach for mitigating the lack of `exclusiveFields` availability in the new GoogleAdsFieldService. It would be good if the API team were familiar with their own team's blog content to direct users to appropriate resources for assistance.

[Google Ads API Forum Advisor]

Hi Dylan,

Thank you for sharing the blog post.

If you have additional clarifications on the topic which may not be covered by the blog, let us know so I can then raise this to the rest of our API support team.

Best regards,

Peter Laurence Napa Oliquino Google Ads API Team

ref:_00D1U1174p._5004Q2TlFkj:ref