Hi, In the current scenario, I am using the declarative rules for provisioning at AD. However, I want to ensure that the DN value is unique. DN is CN = <First Name + Last Name> , OU=City,DC= FIM, DC=COM. In case of duplicacy, i should be adding 1,2,3 etc like CN=<First Name + Last Name +1>. However, i am not sure if this can be achieved using declarative rules. Migrating to classic meta-verse rules extension will be difficult as it might break other use-cases like deprovioning (where i just remove the declarative sync rule). Please suggest any method to check for existing DN value. Also, is it possible that I continue my provisoning logic using declarative rules, but at the same time, handle the exception "DN already exists" in the 'metaverse rules extension'' provisioning method ? ThanksMayank Vaish

How/Where do you generate the "unique" sAMAccountName? I would suggest you add to that process to also generate a "unique" CN value that FIM can import and use. Otherwise you would need a custom WF to do this, if you do not want to build your on, try this one http://www.tools4fim.com/function-evaluator.aspx

Thanks Kent. I am generating the 'unique' sAccountName while importing the data from HRMS. In my case, the sAMAccount Name has Employee ID in it. Hence it is always unique. In case of DN, i cant calculate it in HRMS rules extension as there are few attributes decided by FIM portal. Also. please guide on how Function Evaluator can help in generatiing a unique CN value.Mayank Vaish

An easy way would then be to incorporate the EmployeeID (or sAMAccountName) in the CN as well ;-). Your approach will also cause problems for non-employees (people not in HR system) I guess. Regarding the Tools4FIM FunctionEvaluator. If you download it, i recall it having a nice helpfile with a good example on how to use the Unique Name Generator.