3 Replies Latest reply on Jun 22, 2012 12:32 PM by dloughlin

    Imports - last order

    dloughlin

      When scripting a recurring important, and a "custom import order" is used when the script is initially set up. Subsequent runs of the script will run as "last order". What I have noticed, is that if you delete one of the fields from the source, the fields will no longer align properly. Apparently, Filemaker does not use the field name when using "last order", but rather some other indicator (field order?). It seems that every field from the place where the removed field was is shifted by one in the field alignments. Is there any workaround for this? I suspect not, but figured it couldn't hurt to ask.

       

      Dennis Loughlin

        • 1. Re: Imports - last order
          DrewTenenholz

          Dennis --

           

          I don't know if this is helpful, but from the FM12 Help file:

          Home > Using FileMaker Pro > FileMaker Pro basics > New features in FileMaker Pro 12

          >Changed and removed features

          >>Features changed in FileMaker Pro

          "Importing data from FileMaker Pro databases - Import order has been improved. The addition or deletion of fields after field mapping no longer affects the sort order in import target files."

           

          Maybe this is only good for FMPro<-->FMPro?

           

          -- Drew Tenenholz

          • 2. Re: Imports - last order
            fm4alluvu

            What is the format of the file containing the information you are importing?
            If you could format your input file as a CSV with the first line containing the field names, the rest of the lines the data, you could select
            "Matching Field Names" as your import Order, then if you delete one of the source fields from the import file, you will not change the import
            order of the remaining fields.

             

            fm4alluvu

            • 3. Re: Imports - last order
              dloughlin

              I should have been more specific, I am importing from another FMPro database.

              Drew, I'll have to try it with FMPro 12. That would make things a lot easier when setting these things up if that is in fact the case.