MS Dynamics 365 CRM uses lookup fields and HubSpot provides text fields. When will the complete synchronization of all user-defined fields between the systems be made possible?
No - unless you're referring to the ones offered default out of the box. Those are part of "default mappings". But when you're making a custom lookup field in Dynamics going from lead to account, supposedly you'd want these to work as actual associations - in HubSpot referring to not the Dynamics account but the corresponding HubSpot account right? In a sync, that's a complex undertaking, and this is why we are working on rolling out "custom associations" as part of our work on custom object sync.
The following fields should already sync bidirectionally:
Text
Integers
Dates / Datetimes
Single checkboxes
Additionally, we're pushing Owner Sync (a type of lookup field) live in a couple of days. Certain lookup fields should already sync one way sometimes... Which one in particular do you need @ChandanV ?
Hi @FransLeys Is there any update on this issue please? We have a client that urgently needs to sync lookup fields between HubSpot and Microsoft Dynamics
We launched updates to field mapping earlier this year already. It was communicated in various places but I missed this thread, sorry.
"Lookup fields" can be an ambiguous term. Sometimes it's just picklists, and sometimes it could refer to something that looks like a picklist but in reality acts as a direct association to a very different object in Dynamics. That is still not supported. We sync the objects that are there - and the associations. If you have a lookup on a D365 company form that points to e.g. a custom entity in D365, we can't pull that data in, because we'd need to support custom entity syncing first and that's far out.
But when it's a simple picklist, we do now support two-way syncing of those
Hi Frans, thanks for the update to this thread! Lookup fields like an account / AccountID on a lead, a lead/leadid on a contact and vice versa, is that supported?
No - unless you're referring to the ones offered default out of the box. Those are part of "default mappings". But when you're making a custom lookup field in Dynamics going from lead to account, supposedly you'd want these to work as actual associations - in HubSpot referring to not the Dynamics account but the corresponding HubSpot account right? In a sync, that's a complex undertaking, and this is why we are working on rolling out "custom associations" as part of our work on custom object sync.
