in

 

Ordering Fields on the List Layout

Last post 07-24-2008 2:05 PM by John Filicetti. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 07-23-2008 9:00 AM

    Ordering Fields on the List Layout

    How do we control the sequence of fields on the List Layout - the default display for a Dynamic App?  I have worked on a DA called Requirements Tracker (I have actually modified John Filicetti's DA that I downloaded from the Solutions Library).  I defined the following fields in sequence:
         Requirement ID
         Priority
         Type
         Requirement
         Description
         Requested By
         ...

    The Wizard, for some unknown reason, has decided that, of these fields, "Requested By" is to be the key for this DA.  "Requested By" is the first field in the List Layout and is the forced field for any View that is defined for this DA.  How do I change this?  "Requirement" or even "Requirement ID" would be far better candidates for the key.

  • 07-23-2008 2:34 PM In reply to

    Re: Ordering Fields on the List Layout

    The easiest way for a picklist is to lables the items 1-, 2-, and so on. This will also work for reporting.
    John F. Filicetti, PMP, MBA
  • 07-24-2008 1:30 PM In reply to

    Re: Ordering Fields on the List Layout

    The problem is not with individual pick list values in a field.  It is with the way Daptiv selects which field is considered the "key" to the DA itself.  If I want to be sure which field is considered the "key" (the one that is assumed whenever a view is defined and is the first field displayed for the DA under a Project), how do I do that?

  • 07-24-2008 2:05 PM In reply to

    Re: Ordering Fields on the List Layout

    Ah, great discussion topic. The first required field becomes the default field for views. Sometimes you can select another field. Other times you may have to export your data, rebuild the DA, and import the info.
    John F. Filicetti, PMP, MBA
Page 1 of 1 (4 items)

Navigate: Home | Blogs | Forums | Solution Library  Get Help:  Contact | Feedback | FAQ   Terms of Use:  Terms & Conditions | Privacy Policy