Skip to content

Commit 9e678be

Browse files
address automated feedback
1 parent 6f956e8 commit 9e678be

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/general-development/managed-metadata-and-navigation-in-sharepoint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ A term store manager can enhance and expand term usage models based on more flex
132132
- Link to another site collection and view others' terms. If you want to make your term set available to other site collections connected to the managed metadata service, create a **global term set**. If you want to create a private term set that is available only to a specific site collection when it is stored in the managed metadata service, create a **local term set**.
133133
- Block users from using keywords outside of a specific term set.
134134
- Gain additional multilingual support, including support for automated translation and flexible LCIDs.
135-
- For programmatic creation of taxonomy fields using the SharePoint Server Object Model, please refer to the sample [](/dotnet/api/microsoft.sharepoint.taxonomy.taxonomyfield)
135+
- For programmatic creation of taxonomy fields using the SharePoint Server Object Model, please refer to the sample: [TaxonomyField Class](/dotnet/api/microsoft.sharepoint.taxonomy.taxonomyfield)
136136
- For programmatic creation of taxonomy fields using the SharePoint Client Side Object Model (CSOM), you can use a similar pattern as above taking into consideration the following sample: [Complete basic operations using SharePoint client library code](../sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md#add-a-field-to-a-sharepoint-list)
137137

138138
## Unsupported scenarios for working with custom site definitions

0 commit comments

Comments
 (0)