With this version there are is a set of breaking changes change that must be considered when upgrading from a version before 11.
Namespaces
The following namespaces has been removed:
DFS.Connect.Digizuite
DFS.ContentSearch
DFS.Digizuite
DFS.Services
Custom Indexes
The 2 custom indexes dfs_assets_master_index and dfs_assets_web_index has been removed. The assets will be indexed in Sitecore’s default indexes Sitecore_master_index and Sitecore_web_index. You have the opportunity to create your own custom index. DFS 11.1 - Custom content search index
Pipelines
All the pipelines around synchronization has been removed. New one has been added. If you hooked into one of our synchronization pipelines, then read about the new pipelines DFS 11.1 - 6 Pipelines in DAM for Sitecore .
Configuration
All the .config files in App_Config\Include\damforsitecore has been reorganized. The most important config file DFS.Settings.config, contains the settings to Digizuite. You properly have a patch file where you overwrite these settings.
These settings have been removed.
DFS.AssetSiloSettings.Default.BaseAddress
DFS.AssetSiloSettings.Default.Username
DFS.AssetSiloSettings.Default.Password
DFS.AssetSiloSettings.Default.ConfigVersionId
The patch file should now as a minimum contain the following settings.
DFS.Digizuite.BaseAddress
DFS.Digizuite.MediaManagerUrl
DFS.Digizuite.ChannelFolderId
You can read more about the setting DFS 11.1 - 3 Setting up Sitecore
Synchronization
The full synchronization that was a requirement before you could start using the connector, has been removed. It is no longer required to synchronize all assets into Sitecore before you can add assets to pages. Now the assets will be synchronized as they get used.
It’s still possible to do a full synchronization. We have moved this feature to the Administration dashboard. The full sync is useful if you need to search for dynamic content on the website. DFS 11.1 - Synchronization
Asset template
The asset template at /sitecore/templates/DFS/Data/Asset has changed.
...
Field
...
Changed To
...
Deleted
...
OriginalAssetId
...
DerivedFrom
...
IsPublic
...
x
...
Published
...
x
...
MetaDateStrings
...
DynamicMetadata
...
MetaDataTreeItems
...
DynamicMetadata
...
MetaDataComboValues
...
DynamicMetadata
...
LastPublished
...
x
...
CreatedDateTime
...
UploadDate
...
ChangedDateTime
...
LastModified
...
VideoLength
...
Duration
...
VideoWidth
...
Width
...
VideoHeight
...
Height
...
VideoFps
...
x
...
VideoRotation
...
x
...
ImageHeight
...
Height
...
ImageWidth
...
Width
...
ImageDpi
...
x
Html Templates (AssetTypeOutputRoot)
The asset html templates has been moved from
/sitecore/system/Modules/Digizuite/MetaDataRoot0/AssetTypeOutputRoot
To
/sitecore/system/Modules/Digizuite/Render Templates
The Branches AssetTypeOutputRoot has been deleted at /sitecore/templates/Branches/DFS/AssetTypeOutputRoot
DAM Explorer replaced with a new UI
The Asset picker UI, DAM Explorer has been removed and replaced with a new UI. Now we load an embedded asset picker from Digizuite in an Iframe. Because of this, we have removed all the configuration items at /sitecore/system/Modules/Digizuite/MetaDataRoot0.
The Hook - Detect dam changes
The background process that ran every 1 minute which was looking for changes in Digizuite and updating the items in Sitecore, has been removed. You should use the Digizuite webhooks, listening for asset updates.
AssetMetadata
The AssetMetadata model has changed some of its properties. DFS 11.1 - 4 Accessing metadata through API
...
Property
...
Changed To
...
Deleted
...
CreatedDateTime
...
UploadDate
...
ChangedDateTime
...
LastModified
...
LastPublishedDateTime
...
x
...
Extension
...
FileExtension
...
VideoLength
...
Duration
...
VideoPreview
...
x
...
VideoWidth
...
Width
...
VideoHeight
...
Height
...
VideoFps
...
x
...
ImageWidth
...
Width
...
ImageHeight
...
Height
...
ImageDpi
...
x
...
ThumbSmall
...
x
...
Thumb
...
x
...
Preview
...
x
...
WebPreview
...
x
...
RawUrl
...
x
...
AllowReCrop
...
x
...
AccessKey
...
x
Video playback
The html template for video has changed. Now is uses the native video tag. We also change the video streaming url. Our media handler for serving images and documents can now also stream a video asset1.
Mediahandler
In digizuite DAM 5.10 the transcode system has change DC 5.10 Breaking changes - Transcode system. What that means for the DFS connector is that, when requesting rendition that hadn’t been generated yet a fallback image will be returned and the statuscode is 202 (Accepted). The fallback image is of type svg and controlled by Digizuite. Once the rendition is ready in Digizuite is will be served to the mediahandler in Sitecore.
Resizing
The logic when resizing in the mediahandler has changed. In the previous version the resizing was done in code, first we downloaded the image into memory and resized the image. In this version the rezising har moved to Digizuite. We now call a new endpoint at Digizuite that handles the resizing. This also means that if the excact resized rendition requested hadn’t been generated yet a fallback image will be returned, as the above section.