During attribute sync i am getting error and sync isnt happening of the attribute

Identity Security Cloud (ISC) ISC Discussion and Questions
1

hey guys ,
for testing attribute sync i made a transform and put a static value in one of the attibutes in identity profile.the change of transform is reflecting in idenity level but not on the target account .i got below error :

sailpoint.connector.ConnectorException: [LDAP: error code 20 - 00002083: AtrErr: DSID-03151F38, #1:
0: 00002083: DSID-03151F38, problem 1006 (ATT_OR_VALUE_EXISTS), data 0, Att 908ec3b2 (WorkforceType):len 16
]

can someone pls help

2

Can you provide more details about the application you’re using, what attribute you’re trying to update, and perhaps the transform as well?
The error you have provided seems to indicate that you are trying to synchronize a value to your target system, but that attribute already exists. This could be happening if you are trying to synchronize something like a username to your application, but that username is already in use on another account.

3

Hey Margo,

Yes that attribute exist and I mapped with target application attribute as well. That attribute is office cube and I made a static transform in which I passed a value “testoffice” so when I applied changes on identity profile using transform it is reflecting the change in office cube attribute in all users when I previewed it so I applied changes on identity profile. Now when I tried to see the account inside the identity the same attribute is not synced inside that account but on identity level it’s is synced in not sure why

4

What is the current value that is stored in that attribute?

5

Testmiddlename is the status value that I put in transform

6

Hey @Apoorv0802,
Okay so what i understand from the error message u have posted is that, the attribute value you are trying to sync already exists in any other account.

So if you could check on the application and see if the value you are trying to sync to the target account is already present on any other account. Also you can try passing some unique value to that attribute and see if that works.

I see that you mentioned that attribute is office cube. So it would be a good option to check with application team as well if there exists any uniqueness check on that attribute which is not allowing you to sync the updated value from ISC to target application account.

What else can you try?

  1. Create a new account and make sure that the attribute value is removed from the application side, that is it should return empty on aggregating that account. Try syncing that “testoffice” value again and see if it works. If it does then probably it does not allows overwriting to an existing value.
  2. Create a new account on the application, pass the same value [with which it was throwing an error] while creating the account.
  3. Verify if that also throws the same error. If it does then surely there is some uniqueness check associated with that attribute.

Hope this helps… :slight_smile:

7

I am not sure if you fixed this yet but I found one thing that indicated that you could get this error if your existing and new data were too similar. They had an example of something like a room number in a building - ex. Old Office - Towers 123 and New Office - Towers 456.

Can you try to sync with totally different data?