Skip to main content
New Idea

Allow Additional Identifiers on Update Actions to Users

Related products:CS Rules Engine
heather_hansen
tracy_streetman
TMaier
kstim
+9
  • heather_hansen
    heather_hansen
  • tracy_streetman
    tracy_streetman
  • TMaier
    TMaier
  • jivanova
  • kstim
    kstim
  • benwanlessmenlo
    benwanlessmenlo
  • nheller
  • alizee
    alizee
  • jenlpro
    jenlpro
  • dayn.johnson
    dayn.johnson
  • Stuart
    Stuart
  • ElleShutty
    ElleShutty
  • emily.silva
  • Adam.LaFreniere

TMaier
  • Helper ⭐️
  • 175 replies

Recently I’ve found the need to mass update user email addresses and usernames. Long story. Anyway, the users with corresponding SFDC profiles are no problem now because I can update UN and email with SFDC User ID as the identifier in the Connector sync (yay!). However, when I tried my hand at writing a quick rule to update the UN and Email for non-SFDC users I hit a wall: apparently you MUST still use Username as an identifier in Update actions to the User object (boo!). 

 

This really stings because instead of running this rule that took all of 5 minutes to set up, I get to update four dozen users by hand. I’m sure it could have been worse but man, this would be easier if I could use a rule. For the record, I am attempting to use GSID as my identifier in the user which is, like, THE primary and immutable identifier for a single user profile in Gainsight.

 

So, I’d like to suggest that you remove the requirement to use Username as an identifier to allow people to mass update UN’s via a rule.

 

 

3 replies

jenlpro
Forum|alt.badge.img+3
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • 55 replies
  • January 20, 2024

I am running into this issue right now!!! My company is in the process of migrating our domain from ending in .io to .ai, so all email addresses were updated yesterday & need to be edited in SFDC & GS to match. Any non-SFDC users have to be done manually by hand now in GS. It should be mandatory to have a single identifier of ANY OF: GSID, email, username, or SFDC User ID. 

Glad to find that I’m not the first person to run into this @TMaier 😂


Stuart
Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • 144 replies
  • January 22, 2024

I ran into this last year and it caused quite the issue, but with userIds changing.  Seems to be across the board, including APIs. Per the support docs:

 

SfdcUserId - 

String value that contains SfdcUserId of the user.

Note:

  • This is a non updatable field and can be used as an upsert key for update operation.

 

Needing to change this wouldn’t come up often, but I agree 100% with @TMaier here update should be allowed using GSID as identifier.  The lack of this functionality led to a set of exchanges with support, delaying the changes by a couple of days versus creating a rule in a matter of minutes.


  • Contributor ⭐️⭐️⭐️⭐️
  • 44 replies
  • June 12, 2024

We need to be able to sync usernames from Salesforce as we log to Gainsight through Salesforce,  so the explanation given by Gainsight that updating username with a rule will disrupt user logins does not apply to us. Quite the opposite, if we are not able to sync usernames from Salesforce our users lose access to Gainsight until we manually update the username. Also, the connector user sync tricks you into thinking username can be updated as it doesn’t pop this message about being a required identifier, but the update never happens. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings