February 12, 200916 yr Hi, I'm having a problem getting FM10 to obey me when importing records. It seems to have a mind of it's own. I specify a Field Import Order so that fields from one FP7 file get placed into the correct fields into the other (current) FP7 file. XName > YName XCity > YCity XPrice > MyPrice XSnarf - XFloot - You'd think this would be pretty straightforward, basic, classic stuff, but no. Filemaker decides to import something like this : XName > YName XCity > MyPrice XPrice > XSnarf > YCity XFloot - It doesn't seem to remember what I just specified. What must I do to make the import work as I want it to? Is there some secret shift-click magic I should know about? I've tried Custom import order and last order. Neither works. The only option that works OK every time is Matching names but I'm always able to use that. Sometimes I have files where the names don't match. Any help appreciated. TIA Bobbby
February 12, 200916 yr Are you saving the import in a script using the Import Records script step? How are you referencing the file path for the data source? I believe that if you manually add a file when you build the Import script step, then specify the import field mapping, you will successfully save the import specs. Then, create a $importPath before the Import Records step, and use that as the file path for the data source. Delete the "hard-coded" one that you used to build the import mapping.
February 12, 200916 yr Author Are you saving the import in a script using the Import Records script step? --- Yes. I should have specified that. This in a script. How are you referencing the file path for the data source? ----- file:temp-export1.fp7 I believe that if you manually add a file when you build the Import script step, then specify the import field mapping, you will successfully save the import specs. ------------ Well I did that. Then I copied/pasted a block of script steps and I modified stuff such as Find criteria according to my needs. Then I export into "file:temp-export1.fp7", then I import. I'm not very FM savvy, but why would a $importPath produce a different result from a "hard-coded" path? (I'd rather be watching Spooks :!
February 12, 200916 yr A hard-coded path is fine, provided that you don't need a "smart" import path. So, you've created some sample data by exporting some of your current data. OK. It should come up with Last Order, providing you did a custom import order. Of course, you'll end up with duplicate records, since your exporting and then importing the same data. I can't get this to fail. Perhaps post a sample (use Full Reply)
Create an account or sign in to comment