Hi Matt Kalinowski,
I am not sure what exactly is your scenario. So I cannot be entirely sure what is causing the issue.
However, if you have a hierarchy of Companies for example. And each company has a collection of Departments, where for every department is defined a collection of employees. Now in this scenario, if you create two trees displaying such hierarchies, you will notice that you will only be able to drop employees into departments and departments into companies. In other words if the destination data item doesn't contain a collection of items, which type is the same as the type of the dragged item, then the drop operation is not allowed.
If your case is similar, you will need to make sure that the definition of the items that you want to drop onto allow the operation.
I prepared a sample project illustrating this scenario. In the example all data items inherit one common class thus allowing all "drop onto" operations between and inside the trees.
Please take a look at the project and let me know if it helps. Also if your scenario requires a different approach, can you please elaborate on it. Thank you in advance.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items