Skip to content

Commit 63662f2

Browse files
author
Varsha Muzumdar
committed
remove En-Us from link
1 parent 0bf9b85 commit 63662f2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/search/cognitive-search-output-field-mapping.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In this article, you learn how to map enriched input fields to output fields in
1818
Output Field Mappings are required for moving content from enriched documents into the index. The enriched document is really a tree of information, and even though there is support for complex types in the index, sometimes you may want to transform the information from the enriched tree into a more simple type (for instance, an array of strings). Output field mappings allow you to perform data shape transformations by flattening information.
1919

2020
> [!NOTE]
21-
> We recently enabled the functionality of mapping functions on output field mappings. For more details on mapping functions, see [Field mapping functions](https://docs.microsoft.com/en-us/azure/search/search-indexer-field-mappings#field-mapping-functions)
21+
> We recently enabled the functionality of mapping functions on output field mappings. For more details on mapping functions, see [Field mapping functions](https://docs.microsoft.com/azure/search/search-indexer-field-mappings#field-mapping-functions)
2222
2323
## Use outputFieldMappings
2424
To map fields, add `outputFieldMappings` to your indexer definition as shown below:

0 commit comments

Comments
 (0)