Skip to main content
Discovery

[Rules engine] - Option to not overwrite fields with NULL/empty values

Related products:CS Rules Engine
heather_hansen
bradley
romihache
alizee
Molly.McQ
+2
  • heather_hansen
    heather_hansen
  • bradley
    bradley
  • romihache
    romihache
  • alizee
    alizee
  • Molly.McQ
    Molly.McQ
  • dayn.johnson
    dayn.johnson
  • corey.henningsen
    corey.henningsen

Jef Vanlaer

Use case:

We are loading Gainsight PX Users to the Gainsight CS People/Company People/Relationship People objects. Our users do not always have their first name and last name set in their profile, so these fiels might be NULL/empty in Gainsight PX. If the person already exists in Gainsight CS, their first/last name will be overwritten by the Upsert (which we need as we are also populating username and usage metrics).

Idea:

Provide an option to not overwrite fields when they would be overwritten with NULL or empty values.

3 replies

pgeorge
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • 233 replies
  • November 23, 2020

Hi @Jef Vanlaer 

Just to confirm my understanding. Would the name details be required from PX and only in case they are null should they not be updated in the Person object?

Could I also know how you are pulling these details from PX? Is it using Rules, jobs or any other route?

 

Thank you

Preethi


Jef Vanlaer
Forum|alt.badge.img+2
  • Author
  • Helper ⭐️⭐️
  • 187 replies
  • November 23, 2020

Hi Preethi,

User data is exported to an S3 bucket from Gainsight PX and loaded to a PX Users object via the Rules Engine. Another rule matches PX users to Gainsight CS Persons based on the email address. People are created if they do not exist yet and updated if they do (upsert).

If the name is null in the PX Users object, the name of the Gainsight Person should not be updated, so CSM's can manually set those names without them being overwritten by an empty value all the time.


pgeorge
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • 233 replies
  • January 6, 2021

Got it. Thank you for the update @Jef Vanlaer.

I will check with the team on this and update you with the timelines once it is fixed. 

 

Thank you

Preethi


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