Under Community Review

The Schema form view last had significant changes as part of the SDL Tridion 2011 UI framework (Anguilla). We'll likely revisit this specific view for the Graphene implementation.

Examples and use cases appreciated but please vote on the specific idea of move-able Schema designer fields with enough context to move or otherwise place fields.

Better control of schema field position

Hi,

We have some rather large schemas - 40+ fields.

I've just had to add a new field - requested by the client to be in a certain position. The default behaviour is for the schema to appear at the bottom of the list then for me to repeatedly click "Move up" 35 times to get the field in the right place :(

My finger hurts.

  • Why cant I drag & drop fields to the position them?
  • Why can't the GUI ask me where I want to put the field when I click "Add"?
  • Why does the schema fields box only show 7 fields and I cant expand it?

Cheers

Neil Gibbons
Parents

  • As a workaround, you could just add all your fields at the end and save, then reopen the schema and work with the source to quickly move the fields around.

    Workaround aside, this one has my vote. It would indeed be useful to mark a field and the new field would be added after that one, much like when you add new sets of embedded content. There is a plus sign on existing sets, so you can control where the new fields will appear.

Comment

  • As a workaround, you could just add all your fields at the end and save, then reopen the schema and work with the source to quickly move the fields around.

    Workaround aside, this one has my vote. It would indeed be useful to mark a field and the new field would be added after that one, much like when you add new sets of embedded content. There is a plus sign on existing sets, so you can control where the new fields will appear.

Children
No Data