This seems a bit like a step backward - we're introducing a field that existed in the old type, but wasn't present in the new one. It would be better to avoid having this field at all - but it depends on the supported code versions. We could check whether clients that can send this field are no longer supported. But it isn't critical.