Hi All,
Please could someone help me understand this error? I am wanting to Property Sync my Contact Country property with a Deal Country property.
Hi @Hyroxware,
Where exactly are you creating this property? This doesn’t look like you’re doing this from Settings > Properties. Try to do it from there - that path should flag if anything is not configured correctly or blocking.
Best regards
@Hyroxware can you click “Edit more options” to see if any warnings show up?
If not, then I’d recommend flagging this with HubSpot support directly in-app via chat or email as this seems to be a bug.
Hi @Hyroxware,
I’ve encountered a similar issue before, and here are a few things to check:
- Field type compatibility: Ensure that the Contact Country and Deal Country fields have compatible types (e.g., both dropdowns or both text fields).
- Naming conventions: Verify that the property names match exactly, including spacing and capitalization.
- Existing syncs: Make sure you’re not trying to sync a property that’s already set up.
Since you’re on a Professional plan, this shouldn’t be a plan limitation. Sometimes the “Create new sync” UI can trigger a false error, so Karsten’s suggestion to contact HubSpot support is also valid.
If all of the above checks out, and the error persists, you could consider creating a workflow-based workaround to update the Deal property from the Contact property as a temporary solution.
@JoeA14 please don’t share misinformation and, if you’re using generative AI for answering, keep in mind that you must disclose the use of AI.
- Compatibility between fields doesn’t matter in a sync property. One isn’t syncing to an existing property, the sync property is automatically creating the compatible “target”.
- Naming convention doesn’t matter either, as, again, the sync property is creating the compatible “target”.
- Existing syncs don’t have any relevance either, as sync properties don’t interfere with one another.
Hi @karstenkoehler,
Thanks for the clarification, you’re right about how sync properties automatically handle compatibility, naming, and target creation. I appreciate you pointing that out.
I also want to disclose that I used AI assistance to help structure my initial response. My intent was to share a workflow-based workaround I’ve used in certain situations where Operations Hub wasn’t available, rather than making a statement about default sync behavior.
I’ll ensure future answers are double-checked and AI usage disclosed. Thanks again for helping keep the conversation technically accurate!