Built-in way to Keep or Omit Distinct records of a foundset (cool for de-duplicating)

Idea created by Vincent_L on Aug 23, 2017
    Active
    Score3

    I propose to have 2 new commands (in the "Records" menu for instance),

     

    a) maybe called "Keep first records of each unique sort values" that will narrow down the found set to unique combination of the sort criteria.

    b) maybe called "Omit first records of each unique sort values" that will narrow down the found set to unique combination of the sort criteria.

     

    Obviously, this would only work on a sorted found set, an alert dialog would pop-up up if the foundset is not sorted to warn the user about it.

     

    So the user would sort the records as he wish, and the feature would only keep the first record of each combination of the search fields.

     

    For instance, if we have this foundset, Sorted by  Category  &  Brand   :

     

    SKU     Category    Brand          Product

    A1        15               FMI              FMP 14

    A2        15               FMI              FMP 15

    A3        15               FMI              FMP 16

    B1        15               APP             iMac

    B2        15               APP             Macbook

    B3        15               APP             MacMini

     

     

    a) "Keep first records of each unique sort values" Would result in

     

    A1        15               FMI              FMP 15

    B1        15               APP             iMac

     

    b) "Omit first records of each unique sort values"

     

    A2        15               FMI              FMP 15

    A3        15               FMI              FMP 16

    B2        15               APP             Macbook

    B3        15               APP             MacMini

     

    Those would be super useful :

    a) would allow the user to grasp instantly the different content of a data set,

    b) will be super useful to delete duplicates while keeping the fisrt record, so only removing the worthless dupes.

    all of a sudden thousands of hard to master, cumbersome techniques would be obsolete, replace with a much faster native way. Countless of newbies won't scratch their heads for hours to figure out to remove duped. And yet at the same time, FMI wouldn't have any responsibilities in removing dupes (something that may have frightened them for good reasons), as this won't be advertised / labelled as a deduping feature.

     

    Of course there will be a lot of other usage.

     

    Doing this nowadays in filemaker is pretty complex, while it's a basic need.

    The GUI would be straight foward, as it leverage the sorting GUI

     

    P.S  : of course that would be fully scriptable (ad in script this will lead to pretty good optimizations)