Allow for remapping/disabling of Standard Fields in SalesForce App.
I'm running into issues with a specific Standard field mapping in the SalesForce app. This field does not exist in SalesForce and won't be used in HubSpot, but I'm a bit stuck now. Standard fields should be able to be disabled, remapped to another field, or automatically look for a {fieldname}__c field if {fieldname} is not present (checking for object type as necessary).
This may be a simpler UI issue. In this state the contacts do still sync, the disabled toggle (see below) is actually not a bug but actually means that contacts MUST be synced. *If* this is an artifact of the field mismatch it should be rectified. If contacts are simply assumed to be synced no change is required here.
However, the Contact Field Mappings status should be listed as grey when set to unsynced, displaying a big red dot AND having a disabled toggle causes a lot of consternation from a UI perspective:
It would still be nice to be able to remap standard fields rather than needing to create custom fields and use workarounds to map them, as a user I'm uncertain as to why standard mappings need to be treated separately but I can think of a few backend reasons why assumptions were made around them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
