Sync SFDC tasks to GS timeline which are older than 120 days


Hi Team,

 

Posting this request on behalf of a customer.

 

We have a use case of acquisition or a case where bulk of the tasks in SFDC are older than 120days and there is no way to sync them back to GS timeline using SFDC to timeline integration since the max allowed days to sync past data is 120days.

 

Since allowing entire task data sync to timeline may cause timeout issues with SOQL, it would be great if we can have a customizable date filters to bring in X months / years data into Gainsight recursively.

 

Regards,

Jagadeesh

One alternative would be to enable “Import data“ for the “CS Task” standard object. Then we could bulk extract data using the Salesforce Dataloader and import the tasks without worrying of any timeouts on the Salesforce side.


FYI: @jyothi_bontha 


FYI, that 120 is last modified date not activity date. So, if you want older you should be able to just run an update on the ones you want synced over.


@jagadeesh_kumar_paidimarri thanks for sharing it. Yes currently we do have this limitation. We don’t have an immediate plan to support beyond 120 days. 


FYI, that 120 is last modified date not activity date. So, if you want older you should be able to just run an update on the ones you want synced over.

This could be a good enough solution. If we were to bulk update all our activities (preferably in smaller batches) we can trigger the sync and import everything. I’ll investigate this to see if there are any impacts on the Salesforce side.

thanks!


FYI, that 120 is last modified date not activity date. So, if you want older you should be able to just run an update on the ones you want synced over.

This could be a good enough solution. If we were to bulk update all our activities (preferably in smaller batches) we can trigger the sync and import everything. I’ll investigate this to see if there are any impacts on the Salesforce side.

thanks!

Yeah, that didn’t work. It would mess up all our reports and is definitely not best practice according to our Salesforce admin. Back to square one...