...
In this case, we want to make the field "Exif SoftwareDescription" in Digizuite in Digizuite usable in Episerver. Whether the field is editable in Episerver .
...
| title | Note |
|---|
...
is determined by the settings and rights in Digizuite. If the metafield is set to read only in Digizuite, then the field woulkd be rendered as read only in Episerver and if the Episerver user in Digizuite does not have write access to the metafield.
The following episerver types are supported. Additionally, it is very important to map the Digizuite types to the correct Episerver types.
...
The table shows the mapping between episerver and digizuite types.
| Episerver type | Digizuite type | Editable |
|---|---|---|
| Bool | Bit | Yes |
| DateTime | DateTime | Yes |
| String | String, float, link, note, uniqueVersion | Yes |
| IList<string> | Tree, combovalue, multicombovalue | No |
| IList<string> | editcombovalue, editmulticombovalue | Yes |
| Int | Int | Yes |
Mapping custom fields
In order for the above property mapping to work, it is important to ensure that Digizuite also sends the specific metadata field to the Episerver integration - and that it's named the same was as specified in the attribute. This is done by customizing the output parameters for the "GetEpiserverAssets" search in the DAM Center, and adding the requested field as an output parameter, while ensuring it's named correctly.
...