Hello. While considering that good and proven software development techniques utilize some form of standardization of naming conventions database methodologies I'd like to know what the Zoho Creator user community is using to make their development projects easier in order to conform to naming standards and database normalization.
This is what I'm planning to use for naming conventions (for the actual "link name" as the form will have its regular name in the "XXX" part of the form name):
Forms - start with Frm_XXX (Frm underscore and Form name)
Views - start with Vw_XXX (Vw underscore and View name)
Stateless Forms - start with SF_XXX (SF underscore and Stateless Form Name)
HTML views - start with Htm_AAA_BBB_XXXX (Htm underscore and which AAA - form and BBB -View and the HTML view name) so that I know which forms and views are contained within that HTML view.
Functions - start with Fn_XXX (Fn Underscore and Function Name).
_______________________________________________________________________________________
To make normalizing a Zoho Creator database easier, my objective is to make sure a Form should have a field that uniquely identifies each of its records, and each field in the Form should describe the subject that the Form represents.
To help with this, I've standardized on making any "Drop-down" or "Select" list its own Zoho form since I usually end up making additions or removal from this list and it makes it easier in the long-run.
I've also included a Rec_ID field (sometimes converted to string format if I'm using HTML views) for any other Form that it references - to use as a Relationship link even though the "Lookup" feature takes care of it. It makes the referencing for a "For Each Record" or a "Fetch Records" script much easier to work with instead of having to combine fields like:
for each <rowvariable> in formname[<optional criteria where Name = input. Name & Address = input.Address>]
to use instead
for each <rowvariable> in formname[<optional criteria where ID = Rec_ID>]
I'd like to know what some of you are using for your own development standards.
Thanks.