Accounts are not getting created in the target domain due to conflict. Need to make change so the account does get created but add logic to if already exists add 1.
It's currently not possible to check if target object exists, then modify a creation of the new one, adding 1 or any other modification. Such change in objects creation mechanism is not feasible because running the same workflow multiple times will generate multiple new target objects instead of updating the current one as a result of successful Match.
Right now, the mechanism of object creation is like this (using a default workflow set):
1) Read is reading both, source and target objects within their respective scopes. Objects are being ingested into the backend database.
2) Match is using matching rules, comparing source and target objects in the database and sets source->target relationship if match conditions are true. When there are multiple rules, match is stopping to process them as soon as specific rule becomes True. Rest of rules will be ignored after that.
For example: Match is set to compare the following attributes:
display_name->display_name
samAccountName->samAccountName
mail->mail
If displayName comparison got False (attributes' content was different), then samAccountName will be compared. If samAccountName will be the same, then objects become matched and mail attribute won't get compared
If no match was found, then usually object will be marked for creation
3) Stage processes database objects, comparing attributes for matched objects and populating a changeset according to template Mapping rules. Only different attributes will be present in the changeset. Unmatched objects, marked for creation will also be processed according to the template. It's just target attributes do not exist at this time.
4) Write will commit pending changeset transaction to the actual target environment
