Skip to content

Commit e384bb2

Browse files
author
Varsha Muzumdar
committed
Comments
1 parent 7d4a2fd commit e384bb2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/search/cognitive-search-common-errors-warnings.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Indexer read the document from the data source, but there was an issue convertin
7575
<a name="Could not map output field 'xyz' to search index due to deserialization problem while applying mapping function 'abc'"/>
7676

7777
## Error: Could not map output field 'xyz' to search index due to deserialization problem while applying mapping function 'abc'
78-
Applying output mappings failed possibly because of incompatibility between the output data format and the format expected by mapping function. For example, applying Base64Encode mapping function on binary data would generate this error. To resolve the issue, either retry the operation without specifying mapping function or ensure that the mapping function is compatible with the output field data type. See [Output field mapping](cognitive-search-output-field-mapping.md) for details.
78+
The output mapping might have failed because the output data is in the wrong format for the mapping function you are using. For example, applying Base64Encode mapping function on binary data would generate this error. To resolve the issue, either retry the operation without specifying mapping function or ensure that the mapping function is compatible with the output field data type. See [Output field mapping](cognitive-search-output-field-mapping.md) for details.
7979

8080
<a name="could-not-execute-skill"/>
8181

@@ -314,8 +314,8 @@ Output field mappings that reference non-existent/null data will produce warning
314314

315315
| Reason | Details/Example | Resolution |
316316
| --- | --- | --- |
317-
| Cannot iterate over non-array | "Cannot iterate over non-array `/document/normalized_images/0/imageCelebrities/0/detail/celebrities`." | This could happen if the skills output does not conform to the path of output source field-mapping expression/path. Please double check the paths for extra or missing * provided in the output source field name and ensure that the field value conforms to the given path. Find similar details in [Skill Input was Invalid](cognitive-search-common-errors-warnings.md#warning-skill-input-was-invalid) section. |
318-
| Unable to select `0` in non-array | "Unable to select `0` in non-array `/document/pages`." | This could happen if the skills output does not produce an array and the output source field name has array index or `*` in its path. Please double check the paths provided in the output source field names and the field value for the warned field name. Find similar details in [Skill Input was Invalid](cognitive-search-common-errors-warnings.md#warning-skill-input-was-invalid) section. |
317+
| Cannot iterate over non-array | "Cannot iterate over non-array `/document/normalized_images/0/imageCelebrities/0/detail/celebrities`." | This error occurs when the output is not an array. If you think the output should be an array, check the indicated output source field path for errors. For example, you might have a missing or extra `*` in the source field name. It's also possible that the input to this skill is null, resulting in an empty array. Find similar details in [Skill Input was Invalid](cognitive-search-common-errors-warnings.md#warning-skill-input-was-invalid) section. |
318+
| Unable to select `0` in non-array | "Unable to select `0` in non-array `/document/pages`." | This could happen if the skills output does not produce an array and the output source field name has array index or `*` in its path. Please double check the paths provided in the output source field names and the field value for the indicated field name. Find similar details in [Skill Input was Invalid](cognitive-search-common-errors-warnings.md#warning-skill-input-was-invalid) section. |
319319

320320
<a name="the-data-change-detection-policy-is-configured-to-use-key-column-x"/>
321321

0 commit comments

Comments
 (0)