SelectUniqueValue Error - This function cannot be nested

Question

SelectUniqueValue Error - This function cannot be nested

Michael Liben 261

I am trying to provision users following two naming conventions. If users are in a certain division, they follow one convention which uses their employee ID. If they are in another division, they get a unique lookup based on their first and last name. I am trying using the following expression, but I get the error, "This function cannot be nested : SelectUniqueValue"

Switch([divisionId],"",
"ABC",Mid([personIdExternal],3,9),
"DEF",Mid([personIdExternal],3,9),
"XYZ",SelectUniqueValue(
Mid(NormalizeDiacritics(StripSpaces(Join("", Mid([PreferredName], 1, 1), [LastName]))),1,12),
Mid(NormalizeDiacritics(StripSpaces(Join("", Mid([PreferredName], 1, 2), [LastName]))),1,12)
)
)

Appreciate some guidance on developing an acceptable expression.

1 answer

Your answer

Answer 1

Limitless Technology 44,771

Hello there,

Can you make sure that you've followed the rules for implementing this function?

This function cannot be applied to attributes that have a matching precedence.
This function is only meant to be used for entry creations. When using it with an attribute, set the Apply Mapping property to Only during object creation.
This function is currently only supported for "Workday to Active Directory User Provisioning". It cannot be used with other provisioning applications.

Similar discussion can be found on this thread https:// github.com/MicrosoftDocs/azure-docs/issues/47786

--------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer--

Michael Liben 261 Reputation points

2022-10-26T15:08:37.233+00:00

Yes, I have followed the rules and read the limitation where the SelectUniqueValue function cannot be nested. I am looking for suggestions on how to achieve different SamAccountName naming convention within the same domain while still being able to determine a unique value.

I am disappointed that the unique name function is severely limited. Since you don't expose the specifics of the ldap lookup, I'm not even sure it can take an entire forest into account.

I can readily do this in PowerShell but I am currently limited to executing as a standalone application since it cannot be integrated into the Success Factors "solution." The whole point of moving to AZure AD-based provisioning is to get away from the mutiple on-premises point solutions.

From the available examples, it doesn't appear I can trigger using a LifeCycle Workflow.

Share via

SelectUniqueValue Error - This function cannot be nested

1 answer

Your answer