Skip to main content

We are moving to NXT soon and need to know what Gainsight’s future plan is with Email Logs. In our SFDC org, we currently rely on the Email Logs object quite a bit for reporting. I see that in NXT there is still an Email Logs object, but there is also an Email Logs Merge object and an Email Log V2 object. 

 

We’ll definitely need to load historical emails into our new NXT environment, so what is the best way to go about doing that? Map them to the Email Log V2 object? Or should we just do a straight 1:1 mapping between the two Email Logs objects? I want to make sure we’re not creating any potential tech debt.

+@Divya, @PavanCh, @Chandu for any insights?

@sshroff for anything you are aware of?

@spencer_engel as I understand, whenever “Email from Anywhere” comes out, all email logs in NXT will be housed in Email Log v2. Currently, that object doesn’t capture emails from all NXT feature areas.

I suspect/hope that the Merge object is just a placeholder that will be used to facilitate the migration of old, non-duplicate data from Log to Log v2 when the Email from Anywhere feature goes live.

Just speculating here as it’s a...maybe released? feature and Gainsight hasn’t responded yet - but I imagine the answer will depend on the timing of your migration and how it lines up to the release of this feature.

This doc indicates it is supported with Log v2 https://support.gainsight.com/Gainsight_NXT/Email_Assist/Email_From_Anywhere/Email_From_Anywhere_FAQs but I am also curious if I am correct in my understanding that that means all email logs will be in the V2 object and the OG object deprecated.

 

I guess it’s not a definitive answer but maybe gives some more context as well, and something else to validate.

@PavanCh do you want to chime in here?

Email logs v2 is the way to go here. Email-from-anywhere (new Email Assist in NXT) writes to that object as its primary. We are syncing new entries back to v1 as well to make sure reports and dashboards continue working, but this will stop once reports have been moved to v2 (have to be rebuilt because v2 is in a different database).

Reply


Terms & ConditionsCookie settings