Skip to content

Commit 32e28a7

Browse files
authored
Merge pull request #6845 from umbraco/cms/dictionaryItems
Removed section regarding Document Types
2 parents c219466 + a5ee5ae commit 32e28a7

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

14/umbraco-cms/fundamentals/data/dictionary-items.md

-20
Original file line numberDiff line numberDiff line change
@@ -54,26 +54,6 @@ It will only be possible to edit the language(s) that the given user has access
5454
Which language a user has access to is determined by the "Language permissions" set on the User Group. Learn more about this feature in the [Users](users.md#creating-a-user-group) article.
5555
{% endhint %}
5656

57-
## Using Dictionary Values in Document Types
58-
59-
In some cases, you might want to render the dictionary values in the Document Type. This is to display the labels depending on the language configured for the logged-in user.
60-
61-
To use dictionary values in the Document Type, follow these steps:
62-
63-
1. Go to the **Settings** section.
64-
2. Open the Document Type where you want to use the Dictionary value.
65-
3. Locate the label and type `#MyDictionaryKey`. For example: `#Welcome` or `#WelcomeDescription`.
66-
67-
<figure><img src="../../.gitbook/assets/Using_Dictionary_Value.jpg" alt=""><figcaption><p>Using Dictionary Value in Document Type</p></figcaption></figure>
68-
69-
4. Click **Save**.
70-
5. Go to the **Content** section.
71-
6. View the content node using the Welcome property. The property will display the dictionary value per the user's configured backoffice language.
72-
73-
{% hint style="info" %}
74-
You can translate tabs and property groups in the backoffice as well. For more information, see [How to Translate Umbraco Backoffice Document Types](https://www.youtube.com/embed/OayHhOf47LA?si=iRZ7NE-ckv9LjrSv) video.
75-
{% endhint %}
76-
7757
## Fetching Dictionary Values in the Template
7858

7959
To fetch dictionary values in the template, replace the text with the following snippet:

0 commit comments

Comments
 (0)