Hi, @Anonymous. You're correct this field update rule doesn't exist, and you may be able to resolve this with Salesforce validation.
If the integration user - the Salesforce user whose credentials is stored in HubSpot - is an automated user, or some user which isn't responsible for making edits to those key fields, you'd be able to write a validation rule which prevents a save from anyone who isn't the integration user (or their profile).
This way, changes would still push from HubSpot to Salesforce, and no changes from Salesforce would get back to HubSpot.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.
Hi, @Anonymous. You're correct this field update rule doesn't exist, and you may be able to resolve this with Salesforce validation.
If the integration user - the Salesforce user whose credentials is stored in HubSpot - is an automated user, or some user which isn't responsible for making edits to those key fields, you'd be able to write a validation rule which prevents a save from anyone who isn't the integration user (or their profile).
This way, changes would still push from HubSpot to Salesforce, and no changes from Salesforce would get back to HubSpot.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.