Method Community

 

Minor Annoyance - Field/Object Naming Suggestion

Last post 08-24-2009 3:27 PM by Joe. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 08-24-2009 8:51 AM

    • Joe
    • Top 50 Contributor
    • Joined on 08-17-2009
    • Posts 97

    Minor Annoyance - Field/Object Naming Suggestion

    Hi.

    It seems when customizing a page with new fields/objects, these new f/o's are identified in properties and in dropdowns by only their captions. This makes it very difficult to tell the difference between:

    1) an object and field both named "myName"

    2) multiple objects named "myName"

    example: Company's Bill To "city" , Ship To "city" , and "city" of residence of contacts at this company. These will not all necessarily have the same value nor necessarily all be saveable fields. However all are recognized as "city".

    Perhaps a nameing convention that the user cannot alter would make these objects more unique and identifiable.

    Obviously fields can never have the same name internally, so if the edit properties of a field showed its internal name as well as the alterable caption, screen items would be much easier to tell a part.

    -----------

    #example for field on screen from Table "Customer" named "MyName" :

    Step 1 of 3: Object Properties

    Caption               = "MyName" (alterable)

    Caption Location = [ ]      (dropdown)

    Default Value      =  [ ]      (alterable)

    **Identifier            = "Customer_MyName" (static)

    For example, if i were to create a new textbox for "SectionA" and name it "Notes", a reliable (unalterable) format may show in the properties of this object as follows:  SectionA.Obj.Notes1

    #example for textbox on screen from Section "A"  named "MyName" :

    Step 1 of 3: Object Properties

    Caption               = "MyName" (alterable)

    Caption Location = [ ]      (dropdown)

    Default Value      =  [ ]      (alterable)

    **Identifier            = "ScreenName_TxBx_1" (static)

     

    If there is already a unique naming convention visible by the end-user please let me know.

    Thx,

    ~Joe

  • 08-24-2009 12:28 PM In reply to

    Re: Minor Annoyance - Field/Object Naming Suggestion

    Hey Joe,

    If you open the table "customer" and add a field named "Fullname" to the table, that field's name is set as Fullname. If you change the caption of that field to "Name in Full" the field name is still "Fullname".

    On the other hand, if you drag the text box onto the screen from the objects list, then the caption does become the name of that object.


    If you're creating a field to input data into the table, then you would want to create the field on the table. After you have created the field, then add it to your screen. Now when you change the caption of that field. The field name does not change.

     

  • 08-24-2009 2:11 PM In reply to

    • Joe
    • Top 50 Contributor
    • Joined on 08-17-2009
    • Posts 97

    Re: Minor Annoyance - Field/Object Naming Suggestion

    I understand that.

    My situation was that at one point i was moving cells around >alot< and found that i had fumbled around 2 fields with the same caption and had no way to tell which was which. Which "City" was the ship to ? ... Which "City" was the bill to? ... from the tables/fields section yes they are seperated and maintain the same names. But on screen, as far as knowing which field is which, is impossible without jumping through some hoops with test data.

    Just thought it would be easier if the field name listed in the table, was also stated in the properties ( referring to the properties reached by clicking 'Edit' on the field/object in the screem customization - same place caption is changed ). When choosing to do anything with a field on screen, the dropdown always lists all fields/objects by caption (city city city). There is no easily found difference between the 2 or more on screen fields.

     

  • 08-24-2009 3:27 PM In reply to

    • Joe
    • Top 50 Contributor
    • Joined on 08-17-2009
    • Posts 97

    Re: Minor Annoyance - Field/Object Naming Suggestion

    Hi, just bringing some closure to this thread since u have now addressed  this issue w/ me in another post.

    Thanks for looking into the possibility of displaying field names in the edit wizard to make differentiating between them during customization alot smoother.

    ~Joe

Page 1 of 1 (4 items)