Skip to content

Commit 4527438

Browse files
committed
small fix
1 parent 58b099f commit 4527438

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/transform/modernize-userinterface-site-pages-model-publishing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -398,7 +398,7 @@ See [Page Transformation Functions and Selectors](modernize-userinterface-site-p
398398
</WebParts>
399399
```
400400

401-
### I want to populate a managed metadata field with one or more terms
401+
### I want to populate a managed metadata field with one or more terms (as of February 2020 release)
402402

403403
When you have a managed metadata field in the source page metadata then you might want to have a similar managed metadata field for the target page. Given page transformation currently does have a managed metadata mapping feature this poses a problem. A possible workaround is to populate the target managed metadata field with a chosen term or a set of terms in case of a multi-value managed metadata field. This can be done using the `DefaultTaxonomyFieldValue` function as shown in below example:
404404

0 commit comments

Comments
 (0)