Form design notes - naming conventions
Imagine opening a form developed by someone in which no fields have been re-named, and all you have to work with are random field names from field_1 to field_300.
Naming every field, folder and control is essential when developing forms. In your solution, it is best to assign every field, control or section a unique name that does not start with Field.
Leaving fields with default names--for example, in InfoPath you may have fields with names like ‘field10’, ‘field24’ etc -- makes it harder and more time consuming for everyone involved to work with, develop, and (when necessary) troubleshoot the form.
Fields generated from Designer should already be named as described in the Script Design Notes for this section.
Other fields, however, will need to be renamed to something more intuitive and in accordance with whatever naming convention you ultimately decide upon.
In addition, when you name custom controls you can apply some rules to help you name them too.
Naming every field, folder and control is essential when developing forms.