Skip to content

Commit 9c2736d

Browse files
committed
Addressed blocking issues
1 parent 7be6dd6 commit 9c2736d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/search/knowledge-store-projections-examples.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -301,7 +301,7 @@ Add the above Shaper skill to the skillset.
301301
}
302302
```
303303

304-
Now that we have all the data needed to project to tables, update the knowledgeStore object with the table definitions. In this example, we have three tables, defined by setting the `tableName`, `source`` and `generatedKeyName` properties.
304+
Now that we have all the data needed to project to tables, update the knowledgeStore object with the table definitions. In this example, we have three tables, defined by setting the `tableName`, `source` and `generatedKeyName` properties.
305305

306306
```json
307307
"knowledgeStore" : {
@@ -358,7 +358,7 @@ The ```generatedKeyName``` and ```referenceKeyName``` properties are used to rel
358358

359359
Power BI relies on these generated keys to discover relationships within the tables. If you need the column in the child table named differently, set the ```referenceKeyName``` property on the parent table. One example would be to set the ```generatedKeyName``` as ID on the pbiDocument table and the ```referenceKeyName``` as DocumentID. This would result in the column in the pbiEntities and pbiKeyPhrases tables containing the document id being named DocumentID.
360360

361-
## Projecting to Objects
361+
## Projecting to objects
362362

363363
Object projections do not have the same limitations as table projections and are better suited for projecting large documents. In this example, we project the entire document to an object projection. Object projections are limited to a single projection in a container and cannot be sliced.
364364

0 commit comments

Comments
 (0)