V
Vivek ARORA
We have Windows authentication for our employees on Project Server.
We add employees to resource pool using a scheduler run and add the employee
code to the name while creating the resource pool entry.
Our employees' employee code changes when they become permanent (from
on-probation earlier) OR when their location gets changed .
I would like to retain an earlier entry of an employee as inactive entry as
I am running an external costing scheduler based on MSPE assignments.
My problem is that when such a case like employee status change (to
permanent OR transfer to another location) happens, the windows domain
remains the same and hence the Enterprise resource pool cannot take a
duplicate entry ( windows domain and resource login remaining the same).
Can you suggest a workaround to this. BEcause of this problem, all such
cases of employee status change or transfer are causing problem in my costing
application (developed outside MSPE).
We add employees to resource pool using a scheduler run and add the employee
code to the name while creating the resource pool entry.
Our employees' employee code changes when they become permanent (from
on-probation earlier) OR when their location gets changed .
I would like to retain an earlier entry of an employee as inactive entry as
I am running an external costing scheduler based on MSPE assignments.
My problem is that when such a case like employee status change (to
permanent OR transfer to another location) happens, the windows domain
remains the same and hence the Enterprise resource pool cannot take a
duplicate entry ( windows domain and resource login remaining the same).
Can you suggest a workaround to this. BEcause of this problem, all such
cases of employee status change or transfer are causing problem in my costing
application (developed outside MSPE).