Child pages
  • Custom Fields Sorting in Item Custom Tab
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/a349ed51f100597e#

I didn't found the thread about it, but I really don't understand how the
fields are sorted for displaying.

It seems it's a mix of custom field name + Field Label + Heading and maybe
field prompt?

I've created 15 fields, named ndp_1 to ndp_15, and while they appears under
the same title thanks to identical Heading name, they are not at all in
alphanumerical order... then which parameter is used here to display them?

7 Comments

  1. There is "Priority" field in each custom field, that defines sort value for
    each custom field.

    Custom fields are spitted into several groups based on their heading. Then
    within each groups they are sorted by DisplayOrder field.

    When custom fields with identical heading have same display order, then they
    will be sorted by custom field ID (latest created custom field will be at
    the end of the list).

  2. thanks for this info !

    2011/8/8 Alexander Obuhovich <aik.b...@gmail.com>

  3. after my tests, here is a bug saw in 513: Display order value affects also
    Custom fields listing in grids, overriding all other sortings we could
    request by clicking on top column green mark.

    2011/8/8 Phil -- wbtc.fr -- <p...@wbtc.fr>

  4. I see that now.

    We should only apply DisplayOrder forced sorting when custom field value is
    entered or *General *or *Custom *tabs.

    *Developer Note:*
    Apply sorting only when $event->Special is "general" or "all". In all other
    cases sort by FieldName ASC and administrator can change to whatever he
    needs.

  5. note: display order value should be unique for all customs fields, because
    it's not only the display order in the group, but for all the custom field
    tab.
    We should check for unique value entered, don't you think so?

    the very best thing would be to let admin enter values from grid, because
    it's the place where we can have a global view about sorting... but that's
    another thing...

    2011/8/9 Alexander Obuhovich <aik.b...@gmail.com>

  6. *note: display order value should be unique for all customs fields, because
    it's not only the display order in the group, but for all the custom field
    tab.*
    *We should check for unique value entered, don't you think so?*

    If unique, then unique within same heading. And if admin changes heading of
    custom field, then he won't be able to save it all, since it won't be unique
    anymore at new heading.
    I won't that fast to add unique checks here. That DisplayOrder is same as
    Priority for category items. Do you want to introduce unique there for the
    same reason?

  7. I get your point, here is the problem:

    -create a new heading
    -insert 3 values, with display order set as 1,2,3
    -because we have in default install 1,2,3 values, then the result is a
    heading with only 2 values, and the third one appears alone

    in other words, we can't have 2 times the same display property, otherwise
    it breaks the display system in tab

    2011/8/9 Alexander Obuhovich <aik.b...@gmail.com>