Skip to main content

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.

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

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.

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

Terms & ConditionsCookie settings