Naming strategy for Form Links and Field Deluge Names
A general question as I have encountered what many have probable encountered before me, when you set out on building your applications you find yourself a few years down the road, with a mess of a backend due to lack of clarity of what a field represents and does.
I am therefore interested in knowing if someone has a clever, generic system on how to name the Form Links and Field Deluge Names in a hierarchical way so everything is easily identied?
As a thought example in Application A, we have form B which contains field 002 (Surname). The standard deluge name would just be surname, but I was thinking that it may be smarter to name that field A_B_002_surname.
So when working with surnames accross the application I would know that this related to the surname from form B and not from for example form Z?