I have a scripted import that imports between two tables in the same solution but we found that the import mapping changes for different privilege sets due to field access restrictions.

We are finding that the data is going into the wrong fields because a user does not have access to certain fields in the source table even though those fields are not being imported. This makes a huge mess and inaccurate results.

I would have thought that setting the import order in the script and using last order would keep the fields aligned correctly but that does not work even when running the script with full access privileges.

I hope there is something simple that I have missed but this is a huge error if FileMaker remaps the import order because a users privileges do not allow them access to fields that they do not even need to import.

Edited October 7, 201015 yr by Guest

Try setting the script to run with full access privileges.

I already tried running the script with Full Access privileges but that didn't help.

The script is running in an interface file and I am not sure that running the script with Full Access extends through to the Data file where the users field access restrictions are.