We use cookies to make HubSpot's community a better place. Cookies help to provide a more personalized experience and relevant advertising for you, and web analytics for us. To learn more, and to see a full list of cookies we use, check out our Cookie Policy (baked goods not included).
Jan 16, 2020 12:49 AM
I'm trying to get to the bottom of some wierd errors my clients keep getting. It looks like HubSpot CRM users can change a custom field type from one to another without existing fields being changed (until editing). At least, this is my assumption.
The backstory: We're trying to update a company with a field value that was fetched from the user account shortly before. We get a validation error that the enumeration or input type is not correct. Our latest example is a custom field value we pulled which is suppose to be an ID that has numbers and letters, on update we get a integer validation error because of the text. How could those invalid values exist if we're no longer allowed to update them with the same value?
This is what I need to know:
This has been an issue for multiple customers now. I don't know who holds the burden of responsibility here. If it's ours I've love to know so we can fix it right away.
Solved! Go to Solution.
Jan 23, 2020 11:28 AM
Hi, @Dedupely.
Apologies for the delayed response.
A HubSpot user can indeed change the type
of a custom object property via the UI.
Following your example, if a custom company property with "type":"string"
is changed in-app to "type":"number"
, then you as the integrator will no longer be able to write strings to the property, but the company's value will remain a string. HubSpot does its best to retain known values despite incompatible changes to the property's type
.
I'll try to address each of your specific questions:
type
. If you need to write a string back to that field, you must change the custom property's type
back to string
via the corresponding object properties API, undoing the in-app change.string
and number
type
properties, and HubSpot would not programmatically change the type
s of custom object properties.type
via API.Isaac TakushiAssociate Certification Manager |
Jan 23, 2020 11:28 AM
Hi, @Dedupely.
Apologies for the delayed response.
A HubSpot user can indeed change the type
of a custom object property via the UI.
Following your example, if a custom company property with "type":"string"
is changed in-app to "type":"number"
, then you as the integrator will no longer be able to write strings to the property, but the company's value will remain a string. HubSpot does its best to retain known values despite incompatible changes to the property's type
.
I'll try to address each of your specific questions:
type
. If you need to write a string back to that field, you must change the custom property's type
back to string
via the corresponding object properties API, undoing the in-app change.string
and number
type
properties, and HubSpot would not programmatically change the type
s of custom object properties.type
via API.Isaac TakushiAssociate Certification Manager |
Jan 23, 2020 5:05 PM
Thanks for the explination.
Th only way I can see this being fixed then is either we ignore that field or filter it based on the type provided in the fields list. Which is a bit of a pain and maybe not going to be very accurate.
I find it very odd HubSpot would allow users to change field types like this but not much we can do about it now except write some workarounds in the backend.
Thanks for the response. I appreciate you taking the time to go deep with this.
Jan 24, 2020 8:23 AM
Happy to help, @Dedupely.
I agree that mutable property types can be a pain point for integrators like you, so I'll definitely keep this in the back of my mind going forward.
Isaac TakushiAssociate Certification Manager |
Jan 27, 2020 6:32 PM
Thanks for the help. This is great that you were able to confirm the issue. We have a fix for it in Dedupely now and we just launched a blog post on this: https://dedupe.ly/blog/minor-update-hubspot-field-type-change-and-dedupely/
Jan 28, 2020 6:53 AM
Thanks for updating the Community, @Dedupely!
Isaac TakushiAssociate Certification Manager |