I'm not sure if this is a bug, but I've come across a troubling issue with the import mapping being different from what I set for accounts with limited (no access) field access. I don't believe this was an issue in FM6, but it seems to be consistent in FM7, FM8, and FM8.5.

In the attached example, with access to the Salary and Hourly Rate field restricted for the "User" privilege set, if that user tries to run an Import of that file, the stored field mapping is lost for the Name field with was created after the Salary and Hourly rate.

It is understandable why this would be. Since those two fields aren't visible, they shouldn't be selectable in the Import dialog. But since this is a stored Import mapping, it would be nice if it still worked for all the fields the user can see.

The real danger here is not knowing about this so you can work around it (with lookups or something). Someone might go through and add such field access restrictions after the interface and import scripts are all set up, and not check that their imports work correctly for every field with every privilege set.

So does this sound like a bug, or what?

To see the example, login with Account: Admin, Password: admin

ImportMapping.zip

I wonder if the order would be preserved if you set the script which contains the import function to run with full access privilege?