Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to (force) update Name (label) object in insight ?

Benoit Heylens August 27, 2021 edited

I sync'd my Active Directory with Insight to create a User Scheme.

At first, every object was named as the User CN (Name and Label and Identifier).
Then I tried to set up sAMAccountName as a second identifier, but it messed with how I wanted the field to be human readable so I unchecked it back.

Now some objects "user account" shows as John Doe and others as "u09390329". The only way to get it back to John Doe is to edit the user and save it, without changing anything.

I have 3000+ users and I don't want to do that by hand.
insight_problem1.png insight_problem2.png insight_problem3.png
How can I force refresh object names ?

1 answer

1 accepted

0 votes
Answer accepted
PD Sheehan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 27, 2021

Can you temporarily set the identifier in your import to another field that is unique and populated for 100% of the users? Like, maybe the mail attribute?

When you sync, the Name should be refreshed back based on your mapping.

FYI, the "Identifier" in the import, the way it works is that this is what's used to decide if a record in LDAP is a new or existing user. If you select both CN and sAMAccountName as identifiers and run a synchronization, it should not do anything immediately. But if in the future, an LDAP person record has either the CN or the sAMAccountName changed, you will now have a new combination of the two LDAP attributes and insight will think this is a new object (and perhaps delete the old object depending on your import configuration).
Now, I have seen issues where after changing which attribute is the label for the object type, the existing records are not always updated until each record is touched somehow.

One way you can trigger that is to create a new attribute on your object type. Just a simple checkbox. Then, do a bulk change on all 3000+ objects setting the value of your new checkbox to true. This should cause the label to be re-calculated correctly. After that, you can delete that checkbox attribute.

Another option might be to create a new CN  or Username attribute. In your import, add the new attribute and map it to the CN LDAP attribute. Then, for the "Name" attribute, map both the "displayName" and CN LDAP attributes and run a full sync.

This way, each user's label will show "Full Name - username". That might be a better user experience.

Benoit Heylens August 30, 2021

The solution of creating a new attribute (checkbox) did the trick. I really wish there was a cleaner approach (like a "force refresh").

Thank you for your help :) !

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events