Skip to content

Commit 4131bc7

Browse files
authored
Update search-indexer-field-mappings.md
Updated with the missing link to the advanced scenarios
1 parent 15a80b0 commit 4131bc7

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Field mappings apply to:
3030

3131
+ Physical data structures on both sides of the data path. Logical data structures created by skills reside only in memory. Use [outputFieldMappings](cognitive-search-output-field-mapping.md) to map in-memory nodes to output fields in a search index.
3232

33-
+ Parent AI Search indexes only. For "secondary" indexes with "child" documents or "chunks", refer to the [advanced field mapping scenarios]().
33+
+ Parent AI Search indexes only. For "secondary" indexes with "child" documents or "chunks", refer to the [advanced field mapping scenarios](advancedFieldMappingScenarios).
3434

3535
+ Top-level search fields only, where the `targetFieldName` is either a simple field or a collection. A target field can't be a complex type.
3636

@@ -449,6 +449,7 @@ The field mapping needs to be specified as shown below.
449449
]
450450
```
451451

452+
<a name="advancedFieldMappingScenarios"></a>
452453
## Advanced field mapping scenarios
453454

454455
In scenarios where you have "one-to-many" document relationships, such as data chunking or splitting, follow these guidelines for mapping fields from parent documents to "child" documents (chunks):

0 commit comments

Comments
 (0)