This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 94%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
Salesforce Production Permission Set Group Mapping Erroring Expression.txt
Salesforce Production Permission Set Group Mapping Working Expression.txt
I am building an expression for User Provisioning in an Entra ID enterprise application used for SSO and automated User Provisioning to our Salesforce Production org.
The expression will map the Job Title in Entra ID to a Permission Set Group in Salesforce.
The expression is attached in the file Salesforce Production Permission Set Group Mapping Erroring Expression.txt
If I copy and paste this into the expression it displays a "The expression you entered is not valid" error.
If I copy and paste a smaller set of Job Titles into the expression it shows as valid. This expression is attached in the file Salesforce Production Permission Set Group Mapping Working Expression.txt
If I add one more Job Title mapping to the expression the "The expression you entered is not valid" error displays again.
Is there a limit to the number of IIF arguments that can be added to an expression?
Is there a more efficient way to build this expression?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 36%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Craig,
I just provided an answer to this exact same question that you asked on a different thread
The IIF argument is not well suited to expressions with lots of variables as there is a limit to the amount of variables you can use. The Switch argument worked much better as there is no limit.
Example of a Switch argument when mapping a provisioning field to a Salesforce user account boolean field using jobTitle.
Switch([jobTitle], "", "Head of Commercial", "False", "Head of Digital Marketing", "False", "Head of Partnerships & Events", "False", "Digital Product Manager", "False", "Digital Marketing Manager", "False", "Inbound Marketing Manager", "False", "Financial Controller", "False", "Senior Finance Assistant", "False", "Senior Finance Assistant - Sales Ledger & Cashbook", "False", "Assistant Management Accountant", "False", "Finance Assistant", "False", "Financial Transaction Manager", "False", "Director of English Regions", "False", "Project Co-Ordinator", "False", "Project CoOrdinator", "False", "Regional Development Manager", "False", "Development Manager", "False", "Deputy Head of English Field Staff", "False", "Senior Development Manager (Wales)", "False", "Senior External Affairs Manager (London)", "False", "Field Operations and Training Manager", "False", "Operational Support Co-Ordinator", "False", "Operational Support Co-ordinator - Midlands", "False", "Operational Support Co-ordinator - South East", "False", "Operational Support Co-Ordinator - South (English Regions)", "False", "Operational Support Co-ordinator - London", "False", "Operational Support Co-Ordinator - South (London)", "False", "Membership Advisor", "False", "Director of Sales", "False", "Divisional Sales Manager (North)", "False", "Divisional Sales Manager (South)", "False", "IT Software Engineer", "False", "Sales Support Manager", "False", "Regional Sales Manager", "False", "Director of Membership", "True", "Contact Centre Operations Team Manager", "True", "Contact Centre Manager", "True", "Contact Centre Team Manager", "True", "Operations Administrator", "True", "Quality and Development Manager", "True", "Contact Centre Quality Analyst", "True", "Memberships Team Manager", "True", "Membership Engagement Specialist", "True", "Customer Services Team Manager", "True", "Customer Services Advisor", "True", "Sales & Retention Team Manager", "True", "Sales and Retention Advisor", "True", "Data Insight Manager", "True", "Campaign Selections Analyst", "True", "Data Insight Administrator", "True")
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
@Craig Dyson Thank you for reaching out to us, check the limitations mentioned here - limitations and workarounds for the IIF function.
If this doesn't help, feel free to reply back, will check with my team further on this.
@Givary-MSFT Thank you for the link. There must be a limit to the amount of nested IIF arguments you can use. I have decided to use a mixture of user's departments and job titles to reduce my expression down to 12 arguments for my provisioning mapping.
@Craig Dyson Further checked with my product team on this issue, they suggested - for this type of logic, use Switch instead of nested IIF. It is easier to manage and doesn't have any nesting limitation.
Let me know if you have any further questions, feel free to post back.
Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.
Switch worked much better. Thank you for your help.