It is possible. How much experience/ability do you have for writing scripts?
Here's a general outline of a method that I use.
Define a global container field and put it on a layout.
Write your script to:
1) change to layout with container field.
2) Use Insert File to insert the file to be imported into the container field with the "store a reference" option specified. Do not click the "no dialog" option, instead, a dialog box will appear where the user can select the excel file for import.
3) Extract the file path to this file from the container field, putting that path into a variable.
4) Use the variable with Import Records to import the data from the file that the user selected in step 2.
I understand scripts and have been improving in my abilities. I think I get it, just not sure how to define the match field(s) and automate the data to be imported.
The trick to setting up matching fields is to set up the script step with a data source reference to two files:
A reference to an Actual excel sample file formatted the way you need for these imports.
$Path will receive a value from a set variable step that extracts the file path from the container field. The second line is a direct reference to a file you have on your hard drive at the time you create this script step. The presence of this file reference lets you set up the matching fields and other import records settings for your script step and they will be retained and, as long as you have that file in place, you can return to this script step any time you need to modify the import records options. But when you run the script, the script step will use the file path in $Path to find and import your data.
When testing your script, it's a good idea to move or rename your sample excel file first, to make sure that your script is successfully importing from the file selected via insert file in your script.