Salesforce Picklist on Task Property Not Syncing w/HS

[acjandler]

Hi all,

I'm using the HS/SF connector app and the tasks in Salesforce are not being brought over to HS. I can see that the SF field is a picklist, and HS's are default HS-created enumeration fields. Not sure how to resolve this? Anyone have an idea?

[acjandler · Accepted solution]

Hi Trevor,
Thanks so much - I appreciate your suggestion. The only thing, is that the HubSpot fields (there are actually 3 that this is occurring with) are all default HubSpot fields which cannot be altered by me, and they are showing as enumeration fields, which I think is incorrect. They are dropdowns/picklists. Not sure if there is any workaround, or if this is an error on HubSpot's part... I've got a support ticket in and awaiting an answer. Will post an update...

[trevordjones · Accepted solution]

Hi @acjandler ,

In that case, I would either remove the mapping (if you can) or set it to "Don't Sync" in the integration and create a new property in HubSpot to sync your Salesforce values to.  You should be able to at least change the label or description of the HubSpot default field so it is clear that it should not be used going forward.

If you use "Don't Sync" you will likely see a warning in the inegraiton because there are two mappings, but you can safely ignore it.

Unfortunately, there is no way to get mis-matched dropdowns/picklists to sync.  You must have a matching set of values.

[acjandler · Accepted solution]

Hi Trevor,
Thanks so much - I appreciate your suggestion. The only thing, is that the HubSpot fields (there are actually 3 that this is occurring with) are all default HubSpot fields which cannot be altered by me, and they are showing as enumeration fields, which I think is incorrect. They are dropdowns/picklists. Not sure if there is any workaround, or if this is an error on HubSpot's part... I've got a support ticket in and awaiting an answer. Will post an update...

[trevordjones · Accepted solution]

Hi @acjandler ,

In that case, I would either remove the mapping (if you can) or set it to "Don't Sync" in the integration and create a new property in HubSpot to sync your Salesforce values to.  You should be able to at least change the label or description of the HubSpot default field so it is clear that it should not be used going forward.

If you use "Don't Sync" you will likely see a warning in the inegraiton because there are two mappings, but you can safely ignore it.

Unfortunately, there is no way to get mis-matched dropdowns/picklists to sync.  You must have a matching set of values.

[acjandler · Accepted solution]

Ah! OK. Totally overlooked the idea of just not syncing those. That seems to work. Thank you!

[trevordjones]

You will need to modify one or both picklists so the Internal Values of the options available in th eHubSpot Dropdown Property match the API Names of the values in the Salesforce Picklist.

This can make for a bit of a messy process if you already have values entered in the field in both systems:

The simplest option is to add all of the Internal Values in the HubSpot dropdown as the API Names of the options in the Salesforce Picklist, and then add oll of the API names of the options in the Salesforce Picklist as Internal Values in the HubSpot dropdown. You probably need to add them, since you can't change or delete the internal value of a dropdown option that has entries in it. 

The above process might leave you with duplicative values in both picklists (multiple options which mean the same thing.)  To avoid this, I would add the values form the Salesforce Picklist to HubSpot, and then use workflows in HubSpot to change the the values entered into this field to the most appropriate alternative that is on the Salesforce list.  Once you no longer have any selections in the dropdown with the old HubSpot values in it, you should be able to remove them from the dropdown so you have matching picklists.