# Multi-Valued Identity Attribute **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** identity-security-cloud\ **Created:** [February 5, 2026, 3:09pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149 "2026-02-05T15:09:27Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![ts\_fpatterson](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ts_fpatterson/32/26704_2.png) [@ts\_fpatterson](https://developer.sailpoint.com/discuss/u/ts_fpatterson)\ **Post date:** [February 5, 2026, 3:09pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/1 "2026-02-05T15:09:27Z")
Anybody having issues or know the best process for setting an Identity Attribute to be multi-valued? I tried through the API to set isMulti to true. I also tried through vscode. It takes the setting, but I can’t populate the Identity attribute with more than one value. It has been several days. The identity profile was updated afterwards and changes applied. I tried through a rule initially to set the multiple values and then I used a mock delimited file connector to set multiple - values directly to the source attribute that should the multi-valued attributes on the source attribute. I wrote a python script to validate the schema across accounts for an identity as well as the Identity attribute itself. Below is the JSON response for the schema on the Identity Attribute. # ====================================================================== STEP 3: SCHEMA CONFIGURATION CHECK & FIX 🔎 Fetching Schema definition for ‘activePositions’… 📄 — DEBUG: SCHEMA DEF FOR activePositions JSON START — { “displayName”: “Active Positions”, “multi”: true, “name”: “activePositions”, “searchable”: false, “sources”: [ { “properties”: { “ruleName”: “Cloud Promote Identity Attribute”, “ruleType”: “IdentityAttribute” }, “type”: “rule” } ], “type”: “rule” } “type”: “rule” } “type”: “rule” } “type”: “rule” } ], “type”: “rule” } “type”: “rule” } ], “standard”: false, “system”: false, “type”: “string” “type”: “rule” } ], “standard”: false, “type”: “rule” } ], “type”: “rule” } “type”: “rule” “type”: “rule” } ], “standard”: false, “system”: false, “type”: “string” } 📄 — DEBUG: SCHEMA DEF FOR activePositions JSON END — Found Attribute. ID: NONE (Implicit) Current ‘multi’ setting: True ✅ SCHEMA VERDICT: Correctly Configured as Multi-Valued. Mock Data Source attributes: “attributes”: { “familyName”: “Doe”, “givenName”: “John”, “id”: “130343”, “idNowDescription”: “aecfebcdc786797d791cc7de7091e39698538816ccba11”, “mocked\_active\_positions”: [ “10000328##Teacher Secondary##JC139##Ballard Ridge##2004-08-13##”, “10060468##Teacher Sec - PE##JC131##Seacrest Middle##2024-10-16##”, “10060469##Teacher - Coach##JC104##Timp High##2024-11-16##” ], “name”: “John Doe” }, Thoughts on why multiple values are not being added to the Identity Attribute, the first one is, the subsequent are not? ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [February 5, 2026, 3:59pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/2 "2026-02-05T15:59:04Z")
Hi @ts_fpatterson Multi valued Identity Attributes aren’t supported. Yes, there’s a multi attribute visible on the API, but it doesn’t enable the ability to store multi valued attributes ---
**Author:** ![amulpuru](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/amulpuru/32/39238_2.png) [@amulpuru](https://developer.sailpoint.com/discuss/u/amulpuru)\ **Post date:** [February 5, 2026, 6:33pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/3 "2026-02-05T18:33:31Z")
You can’t make identity attribute as multi Even though it shows at API instead of you really what to populate all the values of multi attribute to an identity attribute try concatenation as provide in this thread > [@Merge multi valued attribute using delimiter](https://developer.sailpoint.com/discuss/t/merge-multi-valued-attribute-using-delimiter/99535): > > Hi All, I have a source with a multi valued attribute and I want to map that attribute to an identity attribute and create a single value separated with a delimiter. For example, if the values on the account are Dep1 and Dep2, I want to create the corresponding identity attribute as |Dep1|Dep2|. I have tried using rule transform and identity attribute rule both, but I am not getting the required output. In both the cases, the output is |Dep1|. Which means only one value is being picked up by … ---
**Author:** ![ts\_fpatterson](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ts_fpatterson/32/26704_2.png) [@ts\_fpatterson](https://developer.sailpoint.com/discuss/u/ts_fpatterson)\ **Post date:** [February 5, 2026, 8:06pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/4 "2026-02-05T20:06:52Z")
So if we have multiple positions and a user has multiple job codes How do we best represent the job codes for a role to evaluate if the Identity has. Do we put it in a JSON format {jc001, jc002} build the string as a transform? ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [February 5, 2026, 8:29pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/5 "2026-02-05T20:29:40Z")
Have you thought about using an Entitlement Type? ---
**Author:** ![ts\_fpatterson](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ts_fpatterson/32/26704_2.png) [@ts\_fpatterson](https://developer.sailpoint.com/discuss/u/ts_fpatterson)\ **Post date:** [February 5, 2026, 10:28pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/6 "2026-02-05T22:28:24Z")
Any best practices with the Entitlement type approach? I would need to exclude the entitlement from the certification. ---
**Author:** ![phodgdon](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/phodgdon/32/3452_2.png) [@phodgdon](https://developer.sailpoint.com/discuss/u/phodgdon)\ **Post date:** [February 6, 2026, 12:50am UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/7 "2026-02-06T00:50:29Z")
You can store them as delimited strings such as job1|job2, etc. ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [February 6, 2026, 9:17am UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/8 "2026-02-06T09:17:18Z")
Hi Fred. See [Creating and Managing Entitlement Types - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/loading_entitlements/entitlement_types.html) I would also recommend updating the Display Name and Description see [Managing Entitlements - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/access/entitlements.html) Entitlements would only be added to Certifications if you configured the Certifications that way. ---
**Author:** ![amulpuru](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/amulpuru/32/39238_2.png) [@amulpuru](https://developer.sailpoint.com/discuss/u/amulpuru)\ **Post date:** [February 6, 2026, 10:37am UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/9 "2026-02-06T10:37:23Z")
Hi @j_place Can you elaborate a bit on this statement ` Entitlements would only be added to Certifications if you configured the Certifications that way.` So they don’t include certificate as they coming from source because neither we are requesting nor assigning as birth right is that correct statement ? Reference > **[Understanding Certifications - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/certs/understanding_certifications.html)** > > SailPoint Identity Services Documentation ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [February 6, 2026, 12:01pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/10 "2026-02-06T12:01:04Z")
Not really. I’m assuming that there are no certification campaigns set up for this source because it’s an auth source. Entitlements that are aggregated would need to be added to a campaign and then the source would need to be enabled for provisioning to make any sense. Think of an AD source where group membership is aggregated. A user could be a member of many many groups and you wouldn’t want all of them in a certification campaign. The document to which you link is just saying that _if you wanted to certify entitlements_ they should be stand-alone and not incorporated into APs or Roles ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [April 7, 2026, 12:01pm UTC](https://developer.sailpoint.com/discuss/t/multi-valued-identity-attribute/195149/11 "2026-04-07T12:01:51Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.