Merge pull request #109281 from vamuzumd/vamuzumd/IntroduceOutputMappingFunctions

Enable mapping functions for output field mapping

Author: PRMerger7

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

@@ -17,6 +17,9 @@ In this article, you learn how to map enriched input fields to output fields in
 
 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.
 
+> [!NOTE]
+> 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)
+
 ## Use outputFieldMappings
 To map fields, add `outputFieldMappings` to your indexer definition as shown below:
 
@@ -46,7 +49,10 @@ The body of the request is structured as follows:
     "outputFieldMappings": [
         {
             "sourceFieldName": "/document/content/organizations/*/description",
-            "targetFieldName": "descriptions"
+            "targetFieldName": "descriptions",
+            "mappingFunction": {
+                "name": "base64Decode"
+            }
         },
         {
             "sourceFieldName": "/document/content/organizations",

articles/search/search-indexer-field-mappings.md

@@ -32,7 +32,7 @@ A field mapping consists of three parts:
 
 1. A `sourceFieldName`, which represents a field in your data source. This property is required.
 2. An optional `targetFieldName`, which represents a field in your search index. If omitted, the same name as in the data source is used.
-3. An optional `mappingFunction`, which can transform your data using one of several predefined functions. The full list of functions is [below](#mappingFunctions).
+3. An optional `mappingFunction`, which can transform your data using one of several predefined functions. This can be applied on both input and output field mappings. The full list of functions is [below](#mappingFunctions).
 
 Field mappings are added to the `fieldMappings` array of the indexer definition.