No, this is not possible. The typical workaround is to create a copy of the property, use either of the two in the form, then create a contact based workflow that copies (only once) the value from the property used in the form into the other one. The one time copy effectively freezes the second property.
Your team would then update the second property only.
The workflow would enroll contacts "When filter criteria is met" > "[property] is known", then leverage the "Copy property value" workflow action. Reenrollment should of course remain disabled.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
No, this is not possible. The typical workaround is to create a copy of the property, use either of the two in the form, then create a contact based workflow that copies (only once) the value from the property used in the form into the other one. The one time copy effectively freezes the second property.
Your team would then update the second property only.
The workflow would enroll contacts "When filter criteria is met" > "[property] is known", then leverage the "Copy property value" workflow action. Reenrollment should of course remain disabled.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
ago 27, 20249:20 AM - editado ago 27, 20249:21 AM
Participante
Freeze prroperties
resolver
Thank you for your response @karstenkoehler . Could you please assist me with how we can send this update to the team and how can the copying the property happen only once?
"The workflow would enroll contacts "When filter criteria is met" > "[property] is known", then leverage the "Copy property value" workflow action. Reenrollment should of course remain disabled."
Out of the box, unless you actively turn on reenrollment, this will be a one time copy.
If you're getting stuck, please let me know where exactly you're getting stuck.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer