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 2024-05-15 UTC."],[[["DateTimeRangeTargetingError outlines errors encountered when associating a line item with a targeting expression, specifically related to date and time ranges."],["This error can occur across various services like AdjustmentService, ForecastService, LineItemService and more, indicating its relevance in managing line item targeting."],["Reasons for this error include issues like overlapping date-time ranges, ranges falling outside the line item's active period, and inconsistencies between the line item's start/end time and targeted date-time ranges."],["The `reason` field provides specific details about the cause of the DateTimeRangeTargetingError, enabling developers to identify and address the issue effectively."]]],["The core content outlines errors related to date and time range targeting within ad management services. These errors, categorized under `DateTimeRangeTargetingError`, arise when associating a line item with targeting expressions. Reasons include empty ranges, incorrect line item types, overlapping ranges, mismatches with line item start/end times, ranges outside the active period, past start times, and ranges with start/end times in incorrect time format. Additionally, general `ApiError` fields provide context, including `fieldPath`, `trigger`, and `errorString`.\n"]]