Import records with matching field names AND update matching records

Idea created by mrwatson-gbs on Feb 6, 2017
    Active
    Score5
    • Benjamin Fehr
    • Johan Hedman
    • Malcolm
    • mrwatson-gbs
    • robertnaud

    Context

     

    In every situation importing records by matching field names is to be preferred over a custom field mapping order, where possible, since

     

    • As we know, Import Records with custom field order suffers when fields are added to or deleted from the (source) table (even in FM15 due to )
    • Import Records with matching field names is ALWAYS stable (given that the developer knows better than to rename fields)
    • Import Records with matching field names has minimal - indeed NO - maintenance requirements
    • Import Records with matching field names guarantees data quality

     

    Currently, however, the option 'matching field names' is incompatible with the option 'update matching records' - As soon as you click on the arrow of the field which is to be used for matching records, the option 'matching field names' is lost.  :-(

     

    This means that imports with update matching records are always 'fallible'.

     

    Idea

     

    It should be possible to apply BOTH 'matching field names' AND 'update matching records' in an Import Records Script Step / Menu import…of course: so long as the fields to use in the update records match also have matching names.

     

    Example:

     

    Import Records[ With Dialog: Off ; "$path" ; Source Table: S ; Target Table: T ; Matching Fields ; Update matching ]

     

    I would also suggest the following refinements:

     

    • (given that the fields to use in update records match also have matching names) the two options should be completely independent of each other
      • it should be possible to select the options in any order
      • selecting matching names and then choosing the update records match fields should retain 'matching names', and
      • selecting the update records match fields and then choosing matching names  should retain the update records match fields

    Benefits

     

    • Database far easier to maintain
    • Improved Data Quality
    • No unpleasant shock, after deleting / adding fields and an import starts misbehaving
    • FileMaker is a better middleware

     

    Use Cases

     

    • Update records using import
    • Many, many, many!
    • Duplicating records / line items
    • Importing records between tables
    • Moving records using Export + Import

     

    Thoughts

     

    According to the FileMaker Roadmap the Import / Export steps are due to be revamped in "FileMaker Beyond" (FM17+) - so I thought it better to get the idea in early :-)

     

    Make FileMaker Great again! ;-)

     

    MrWatson