The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.When I clone an existing form part, I am supposed to change the Field Key value. The UI doesn't make this obvious because it's buried under Advanced settings.
I think CCK makes this more obvious by generally putting a field's label and key next to each other on the field creation areas.
Filing as a UI bug because users shouldn't need to open collapsed areas for routine actions.
I'm VERY impressed with this module, BTW. First time user, already a big fan.
Comments
Comment #1
quicksketchMakes sense to me. Though I'm pondering the importance of the "Field Key" option. In truth Webform itself doesn't need the field key for anything at all because it keys everything on unique IDs. The Field Key is entirely for end-users who want to access variables more easily when theming or using e-mail templates.
Comment #2
aren cambre commentedWhat if you allowed admins to specify a custom CSS class in the advanced area instead of Field Key?
Comment #3
quicksketchCustom CSS classes are not the same thing as the field key (though the field key does get used in the classes and IDs I believe). The field key affects what tokens are available, such as
%email[submitted][field_key_name]. It also affects the names of variables in webform-mail.tpl.php.Comment #4
aren cambre commentedI understand. Earlier you said the ability to modify field key is functionally useless except for styling purposes, so generally dismissing the field key capability and only retaining the ability to affect CSS class names could make sense? Although I guess CSS class names can also be based on the field name?
Comment #5
quicksketchJust note that the location of the field key has moved up in the form as part of the restructuring in #346155: Validation option to set component values as unique. We could further improve the situation by implementing #699206: Patch submission for improved cloning behavior.