Loss of data when creating / updating custom datetime fields through the API

Currently the api wrongly sets the type of custom datetime fields to 'date' when exterminating the type of a custom field.

This causes data loss when creating / updating custom date time fields, as the time part is never saved, but set to 000000 instead.