Order of Sync Operations can cause YSOD about usync-legacy HOT 2 CLOSED

This is potentially complex.

uSync / umbraco needs to know that the property it is putting on a doctype isn't used on any child composition types, and then either not do it, or do something about the child one (Just deleting doctype properties can be quite destructive as it will remove all the content as well)

I would assume the logic is somewhere in the core to stop you doing this - its not in the core api bits because you can, so there must be a check somewhere else. putting checks on all doctype property creation could cause quite the slow down, so it would probably be some form of cache to do this at any great speed.

from usync-legacy.

Done, in latest release - will just do some perf checks before roll out

from usync-legacy.