AI-generated Key Takeaways
-
The
CmsMetadataService
handles metadata operations and may return specific errors relating to metadata merge specifications. -
MetadataMergeSpecError
details issues encountered during the merging of metadata, such as conflicting input IDs or improperly defined value ranges. -
Errors are categorized by reasons like
INPUT_ID_ALREADY_USED
,BOUND_SPECIFIED_WITHOUT_VALUE
, orVALUE_SPECIFIED_WITHOUT_BOUND
, offering insight into the cause of the problem. -
Detailed information on each error, including the field path and a descriptive error string, aids in troubleshooting and resolution.
-
Developers can utilize the provided namespace and field descriptions to interact with the
CmsMetadataService
and understand potential errors.
Errors associated with metadata merge specs.
- Namespace
-
https://www.google.com/apis/ads/publisher/v202411
Field |
|
---|---|
ApiError (inherited)
|
|
|
The OGNL field path to identify cause of error. |
|
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)}. |
|
The data that caused the error. |
|
A simple string representation of the error and reason. |
MetadataMergeSpecError
|
|
|
The error reason represented by an enum. Enumerations
|