UniqueCounter is not working for multiple attributes in create account policy

Hi Experts,

The concept of unique counter does not seems to be working correctly for multiple attributes in create account policy, here If I need to calculate two unique values for two different attribute while Entra account provisioning while account creation unique counter is working correctly for one attribute but not for other attribute,
I tried several approaches but none of them work for me, Now I am trying to explore if we can achieve this via create account or we need some rule for this?

Example I have to calculate two unique attribute where I am calculating values like this

for first attribute

$(firstname).$(lastname)$(uniqueCounter)@domain.subdomain.com via Unique Account ID generator it seems to be work correct as I can see unique counter has been added on account creation.

Another similar change I need to use for email as unique attribute I am trying to create similar pattern with slight change on the domain name

mail
unique ID generator
$(firstname).$(lastname)$(uniqueCounter)@domain.com

I have used custom transform also with the mail to fetch my previously calculated account attribute from previous value calculated correctly for previous attribute, I also tried to use reference from previously calculated value , none of them work for me , reference I mean under mail : $(previousattributename) that was calculated previously not sure which Approach would be fit inside this use case,

Your help is valued for me to complete this use case. Thanks in Advance for looking into this. I hope to get the best solutions from experts :slight_smile:

Hello @LearningStar

You are right ! Unique Attribute generator doesn’t work on multiple attributes . Also , it only works on an attribute which is Account ID . Refer to the similar usecase.

So the solution I figured out is to proceed with cloud rule . The following the cloud rule that might help you in building yours.

Hope this helps !

Thanks
Sid

Thanks @sidharth_tarlapally for looking into this. I had also tried to implement unique ldap attribute name via generator following with the pattern along with uniqueCounter but that didn’t worked for us, only cloud rule is the only possibility ?

If yes we have to create mail by using firstname .lastname (uniqueCounter)@domain.com

If it has already entry in target it will be able to create new accounts like this
1,2,3 with the logic of counter.
[email protected]