Not Considering

Agree with the previous review status

"Schema changes are considered high impact changes in general. Why would you remove a Schema field if you expect that you want to add it back in the future?

Do you want to temporarily hide the field from authors/editors in the GUI? In that case, would it be an option to keep the field in the underlying data?"

Hiding a field might be interesting although it requires a use case

Due to inactivity in discussions and votes, we are not considering this idea

Record lost component fields in comment

We all know that when you remove a schema field the next time you open the component, the field is removed and if you save & close, its lost forever.

Why though?

Why can't Tridion at least record any removed field value (or all changes since the previous version) in a comment in the Source view of the component for example?

At least this gives me advanced authors a chance to recover a value if a field is added back.

Neil Gibbons

  • Its not a question of removing the field with an expectation of adding it back - more a case of making Tridion more forgiving if you do need to add it back (for whatever reason). As Dominic mentions some kind of link between schema version & component version might be nice.

  • When a schema is modified, the old versions of the components are not updated. The data is still there, just not visible via the gui any more. This would be a good candidate for a GUI extension. What's missing is the relationship between which version of the schema you need to use to display which version of the component. I guess you could piece that together from the DateTime stamps.