Skip to main content
josh_grigone
Gainsight Employee ⭐️
josh_grigone
Gainsight Employee ⭐️
December 1, 2016
New Idea

Allow Task Type mapping when syncing Activities to SFDC

  • December 1, 2016
  • 22 replies
  • 359 views
It may be beneficial for end users/admins to have the option to adjust Task Type mapping when syncing Activities from Gainsight to SFDC. Currently, it appears it is set up in such a way that the Task Type to any Activities synced from Gainsight to SFDC will automatically pull the Default Task Type and, depending on which activities are synced, may cause confusion for end users.

For example, a user logs a call from the Activities tab with the "Sync to Salesforce Activity" checked off on the Activity config, this call will appear with the default Task Type which may not be set to "Call" and could throw off some end users. 

Having the ability to map Task Type in the Activities config may assist in resolving this.

Thanks!

      22 replies

      Show previous replies
      seth
      seth
      Expert ⭐️
      January 12, 2021

      @josh.berger I wanted to close the loop with you here -- after our documentation team connected with Product Management, we learned that the expected behavior is actually that the Timeline Activity Type would be stamped into the Salesforce Task/Event Type field, even if there isn’t a matching value configured in the Salesforce picklist. (Our documentation has been updated with that note. NXT | Salesforce Edition )

      Did you end up setting it up?

      AI Transformation @ Gainsight
        josh.berger
        Contributor ⭐️⭐️⭐️⭐️
        January 15, 2021

        @seth - I appreciate the update. I haven’t actually turned it on yet, but since we only had a few values that differed between the two systems, our Salesforce team just added the missing Gainsight values so we would not have to worry about the default behavior. I’m not a Salesforce admin but that default behavior is surprising because I thought the Type field was a picklist by default which I wouldn't think would allow for an undefined value to be entered. If so, I’ve learned something new today :)

          Terms & ConditionsAccessibility statement