We have moved!
You are currently looking at documentation for Umbraco 8 and older versions.
Go to docs.umbraco.com for documentation for Umbraco 9 and newer versions.
Extraction error: Data Type collisions
When creating a new environment on your Umbraco Cloud project, you might encounter some issues regarding some of the default data types built into Umbraco. The data types in question are:
- Content Picker
- Media Picker
- Member picker
- Multiple Media Picker (using Media Picker)
- Related Links
Since these 5 data types are part of the Umbraco CMS, these will be created by default on each new environment on Umbraco Cloud. If metadata files/structure files for these data types have been generated on your Live environment, you might run into extraction errors on your newly created Development or Staging environment. New environments will be exact clones of the Live environment, thus containing all structure and metadata files from that environment.
How do I know I have this issue?
The issue will present itself as an extraction error on your Development or Staging environment once you're created them.
Open the error message by clicking More info.
In the case illustrated above, there are four data types and each has two
What this means is that a file has been generated for each data type on both the Live and the Development environment. The Umbraco Deploy engine needs to create one instance of each data type but is currently not able to do so, since it doesn't know which files to build the data types based on.
See the steps below on how to resolve the issue.
How to resolve the issue
- Access the backoffice of the affected environment (Development or Staging)
- Find the Data Types folder in the Developer section
- Delete only the data types mentioned in the error message
- In the case above, I would need to delete Member Picker, Multiple Media Picker, Related Links, and Content Picker
- Access Kudu for the affected environment
- Follow the Kudu Documentation to run an extraction on the environment
- When you get a
deploy-completemarker, the issue has been resolved!
When you've followed these steps, go through your Development / Staging environment and make sure everything has been created as expected.
The final step you need to take before your Development / Staging environment is completely in sync with your Live environment is to restore the content.