A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-06 UTC."],[[["\u003cp\u003eThe NativeStyleService allows management of native styles, which are used to define the look and feel of native ads.\u003c/p\u003e\n"],["\u003cp\u003eNative styles can only be created under active, native creative templates and require an HTML snippet.\u003c/p\u003e\n"],["\u003cp\u003eTargeting for native styles can include inventory and custom targeting, with limitations on the number of key-value pairs.\u003c/p\u003e\n"],["\u003cp\u003eErrors related to native styles can arise from various reasons, such as invalid targeting types, incorrect status, or missing required fields.\u003c/p\u003e\n"],["\u003cp\u003eDetailed error information is provided through fields like \u003ccode\u003efieldPath\u003c/code\u003e, \u003ccode\u003etrigger\u003c/code\u003e, and \u003ccode\u003eerrorString\u003c/code\u003e, aiding in troubleshooting and resolution.\u003c/p\u003e\n"]]],["The `NativeStyleService` uses `ApiError` as its base, extending to various error types like `ApiVersionError`, `AuthenticationError`, and `NativeStyleError`. Key fields within `ApiError` include `fieldPath`, `fieldPathElements`, `trigger`, and `errorString`. `NativeStyleError` specifies issues like `ACTIVE_CREATIVE_TEMPLATE_REQUIRED`, `INVALID_CUSTOM_TARGETING_MATCH_TYPE`, `UNIQUE_SNIPPET_REQUIRED`, and `UNRECOGNIZED_MACRO`, amongst others, with specific enumerated reasons. It ensures the integrity of native style setup and targeting, restricting targeting types and limiting key-value pairs.\n"],null,[]]