Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Is there a workaround for this problem?

One of the things I like about scripted importing is the ability to ability to prepare my field matches. One of the things I don't like is that I apparently can't save the set and do the actual import later.

I often find after I've spent 30 minutes preparing a complex match up there's some detail I need to check elsewhere. I'd dearly love to save the set, exit, find my detail, come back tomorrow or whatever.

The only workaround I've found is to select only one record to import, allow the import so I can save the set in progress, delete the imported record, do my research and then come back to working the matchup script.

Is there a better way?

Are you sure you're using the word "script" correctly?

If working inside a script, the Import Records script step will save whatever work you've done. Some issues come up if you add or delete fields though.

What you're doing is what I was going to suggest, however, you could script the whole thing including the download and then delete the found set. Then once you've run the script your mapping is saved.

I would have two scripts. One to run and delete and the other to do the download later.

One word of caution. Have your script back up your file before you do the download. I always worry about deleting through a script. You never know when Mr. Murphy is paying a visit. :)

I believe that's true only if you complete the import. If you map all your fields and then do not complete the import your settings are not saved. At least, that's what I've observed. Perhaps we're both doing something wrong?

Are you doing this by going to the drop down menu File-->Import Records or are you going to Scripts-->ScriptMaker and editing a script that contains the script step Import Records[]?

I suspect it's the former, which is NOT scripting. The answer is to script it.

No, I'm running it through a script with the proper script step. What I didn't do was map the correct file because the file name will change depending on the where I get the records from. It's an excel file and the fields are always the same. Therefore, I didn't map the file path. I guess I could just have a generic file name and rename the file and then the mapping will always be there. I tried it and it works just fine. Thanks for making me look at it again.

  • Author

Are you sure you're using the word "script" correctly?

If working inside a script, the Import Records script step will save whatever work you've done. Some issues come up if you add or delete fields though.

My experience is the same as Aldipalo. I create a script. I add the Import Records step to it. I edit the matchup of fields. Now I have just two choices — proceed with the import or cancel.

Is there a third choice I'm missing?

What I didn't do was map the correct file because the file name will change depending on the where I get the records from.

That's the problem.

I create a script. I add the Import Records step to it. I edit the matchup of fields. Now I have just two choices — proceed with the import or cancel.

Is there a third choice I'm missing?

No third choice. You're just missing the point that you're not in the process of importing anything, you writing a script to import. Clicking "OK" is what you're supposed to do to confirm the field set up. The import won't run until you run the script.

Edited by Guest

  • Author

Sorry, problem solved, my confusion.

I created a scripted import and in the process of completing the matching I was taken to an "import options" dialogue. From the look of it I came to the mistaken assumption that the matched fields arrangement would only be saveable if the actual import proceeded. After all that was the way FMP6 and before handled things.

But FMP9 does indeed save the match list in the script without having to perform the import. I can indeed work part way through the matching process, save the script, and come back later to continue working on the matching process without losing previous matching work, without having to start the match process from scratch.

My confusion. Thanks for everyone's help.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.