I have a script which imports a serial number field from one database to the other. The script works well EXCEPT when the first database is logged in with limited permissions...then the import order no longer lines up. I do not want to do matching names import because it overrides like-named auto-enter fields such as CreateDate and CreateUser. Anyone been able to solve this problem before or have any suggestions? Your help is greatly appreciated.

Yes, I have lamented about this issue in the past and I haven't seen a fix for it yet.

You'll have to consider either:

1. Re-defining the fields in a different order,

2. Adding another Import Records[] script step that does match up and have branching choose this for lower-level accounts, or

3. Adding view access to all fields for those lower-level privilege sets (you can still hide them by not showing them on layouts that that privilege set has access to).

Thanks! (That's what I was afraid of)