Map Scripted Import with File Path Variable

Discussion created by cmj on Aug 12, 2018
Latest reply on Aug 14, 2018 by cmj

I have a script that performs an import of data from another table in the same FM file.

During startup I set the application file path to a variable called $$FilePath.

I use $$FilePath for the file to choose when performing the import. Unfortunately, there's no field mapping available when FM does not know what it's importing. This results in no records being imported. When the $$FilePath is replaced with the actual file path the import works as it should.

I need the $$FilePath variable because everyone may not store their application file in the same place.

Is there a work-around that anyone can suggest so the mapping can take place?

Thank You