Good morning all.  We have noticed a particular behavior related to the HR Import process that results in incorrect information in a custom field.  Here's the situation:

1.  Our HR Import is setup with "Source contains all records = NO" and "If the delete flag = 1 then suspend the user."  

2. Our HR Import user.csv file contains a delete field which equals 1 for anyone who has left our organization.

3.  user.csv also has a custom field that stores the Termination Date for that employee, e.g. the day they left.

4.  The default for this custom field is 1/1/1900 so we can tell who is still employed.

5.  Our expectation is that if someone leaves the organization, their record will be suspended and the 1/1/1900 date in the custom field will be replaced with the actual Termination Date.

6.  Instead, the the user is suspended BUT the termination date is not being updated.

Our partner hypothesized, and I confirmed, that once a user is suspended then nothing gets updated on that user's record.

My question is:  How can we get the user's record updated before the suspension actually occurs?  One suggestion is to put the Termination Date in the user.csv file on one day and then make the delete flag = 1 the next day.  I don't think this is possible since the HR Import information comes from our HR system which would make the changes in both fields on the same day.

If we change the order of fields in our user.csv file (currently the delete flag appears before the custom field), would that help?  What else can we do?

I would appreciate any and all ideas that you have.  Thanks very much.

Carol.