If you move a data type out of a folder and then delete that folder, you will hit a dependency error, when content transfering from the source environment to target environment
Reproduction Bug summaryIf you create a data type and move it into a folder, and then deploy this to the target environment, you will hit a dependency error if you later decide to move the data type out of the folder and then deleting that folder.
SpecificsHappens for Deploy 4.5.0.0.
Steps to reproduceThis is tested between 2 Cloud environments, but a customer experienced it in a Local to Dev scenario.
To fix it, you can create a folder on Dev again and name it whatever you like.
Then move the Data Type in there.
Resave the Data Type and deploy these code changes from Dev to Live.
You can now content transfer successfully.
You should be able to content transfer without hitting a dependency error on a folder, given that you deployed these code changes prior to content transfering.
Actual resultThis is an example of what happens if I move the data type out of a folder, delete the folder, deploy the code change and then try to content transfer content that uses the data type:
Dependency Error
The operation cannot be completed due to dependencies that cannot be found for 1 item selected for transfer.
There are dependencies on 1 item to resolve.
Dependency Details
Item selected for transfer: Cool Data Type
Id: 1075
Udi: umb://data-type/4ed4d05e5f6d44d9bfcded0802a3e75c
Type: data-type
Depends on:
Udi: umb://data-type-container/69176de8db6c4f4b83db1e6291e6dd8c
Type: data-type-container
Dependency does not exist.
These issues must be resolved before the transfer operation can succeed. For more information, please refer to this documentation page.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4