Employee ID's are generated by my HR system. These are input into FIM by a text MA I also need to facilitate a requirement to create generic users that also have an employee id. This creation will be done via the FIM portal. I want to be able to specify a 6 digit number starting with G and then increment by one when the next user is created - so these numbers are unique.

You could set a validation regex on the RCDC to enforce the format here when someone creates a user via the FIM portal...My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

You could set a validation regex on the RCDC to enforce the format here when someone creates a user via the FIM portal...My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Also check out this thread for how to use the UniquenessValidationXPath property. You will see the example there only works in CREATE mode, but you can use it in EDIT mode too if you change the xpath statement to something like "/Person[EmployeeID='%VALUE%' and not(ObjectID='%ObjectID%')]". I take it that you want to ensure users which are created in the FIM Portal are assigned a unique employeeID when there is NO linked HR user? If so, I presume that you will want to use the regex idea to ensure that nobody creates a user with an EmployeeID which will eventually clash with a future HR value ...Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using Event Broker 3.0 for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

Also check out this thread for how to use the UniquenessValidationXPath property. You will see the example there only works in CREATE mode, but you can use it in EDIT mode too if you change the xpath statement to something like "/Person[EmployeeID='%VALUE%' and not(ObjectID='%ObjectID%')]". I take it that you want to ensure users which are created in the FIM Portal are assigned a unique employeeID when there is NO linked HR user? If so, I presume that you will want to use the regex idea to ensure that nobody creates a user with an EmployeeID which will eventually clash with a future HR value ...Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using Event Broker 3.0 for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM