The UUID field is added to content types where it is used, presumably to help with avoiding duplication but this isn't actually mentioned anywhere.
There is a valid use case that someone would use this once. Ideally, it should be possible to remove this field from the content type, but at the very least, it should be unlocked when the module is uninstalled.
Maybe the intention was for the field to be locked in the node edit screen, rather than locked to prevent it being removed from the content type in perpetuity.
I had to go in to the field config file, set locked to false before I could then delete it.
The UUID field is added to content types where it is used, presumably to help with avoiding duplication but this isn't actually mentioned anywhere.
There is a valid use case that someone would use this once. Ideally, it should be possible to remove this field from the content type, but at the very least, it should be unlocked when the module is uninstalled.
Maybe the intention was for the field to be locked in the node edit screen, rather than locked to prevent it being removed from the content type in perpetuity.
I had to go in to the field config file, set
lockedtofalsebefore I could then delete it.