Unique number for NE sourced identities

Greetings, all. Wondering if anyone has dealt with the creation of a unique number for non-employee records using the NE source? For instance, an “employee number/id” type value. We’ve utilized the random number generator on a first valid transform to create a random number and maintain it on the identity, but there is no way to verify uniqueness here. I’ve developed some java code that will perform the generation but it’s complicated and a bit clunky. Wondering if there are better ways, or are people just implementing NE sources without a unique number value/id since the account request requires a unique username in itself?

1 Like

Another user recently posted a question to help troubleshoot a transform they are creating to generate unique account names. Here’s the post. Transforms do provide some capabilities to verify account names/ids are unique, as mentioned in the post.

That’s embarrassing. I will see myself out. :slight_smile:

1 Like

No problem at all :grinning_face_with_smiling_eyes:. Let me know if you are able to solve your need with that post. If it works for you, can you mark my response as the solution? It helps future readers identify solutions to their problems if they see answers marked as the solution.

1 Like