What does it mean when "invalid value" appears in red next to a contact's property?

Last updated: January 23, 2018


You may find that some of your contacts' property values are displayed in red with an "Invalid value" error. 


Why this error appears

Property values can be invalid if:

  1. The property value doesn't match the format that the property type requires (e.g., the contact has a text value in a date picker type property).
  2. The property is an enumeration property (dropdown select, multiple checkboxes, radio select, or single checkbox) and the contact's value does not match the values defined in the property's options.

How this happens

  1. The contact has a value set when the property is one type, then the property is changed to another type, making the contact's value invalid. For example, you are using a single-line text field to capture the birthday for your contacts who fill out one of your forms:
    • A contact fills out the form and provides the value October 25, 2015.
    • Later, you edit the property Type and make it a date picker property.
    • Now that the property is a date picker property, the value October 25, 2015 is invalid because date picker values must be stored on the backend as unix timestamps (e.g., 1445745600000) even though the timestamp value for the property is displayed in-app as a human-readable date format, like 10/25/2015.
  2. The contact has an invalid property value set via the Forms API, which allows any value to be passed to a property, even the value is invalid.
    • For example, when passing a value to a date picker property via the Forms API, the value must be passed in UNIX millisecond format. As mentioned above, the HubSpot app will display the timestamp in a human-readble format, but the value must be passed as a timestamp:
      • If you want to set a value for a date property for your contact to October 25, 2015, passing values of 10/25/2015, 10-25-2015, or October 25, 2015 via Forms API will result in an invalid value error.
      • Instead, you must pass a value of 1445745600000 (the UNIX timestamp equivalent of October 25, 2015) via the Forms API.
    • In another example, you are passing values via Forms API to an enumeration property like the default HubSpot property Persona. This property has a number of different property options that can be set and each option has a different label and internal value:
      • When passing a value via the Forms API to any enumeration property, you must pass the internal value, not the label.
      • HubSpot will display the label of each property option when the correct internal value is passed. If an invalid value is passed, that value will be displayed as is, but it will be colored red and Invalid Value will appear when you hover over the value. 

    • In a third example, you are using the Forms API to pass values to a single checkbox property (which is also an enumeration property).
      • Single checkbox properties have two options with labels Yes and No and corresponding internal values true and false, respectively.
      • If you pass the value Yes via Forms API, that value is invalid because you must pass the corresponding internal value for that option's label, which would be true.

For more on the Forms API, check out or developer documentation.

How to fix an invalid value error

To fix an invalid error issue on enumeration

  1. Add those invalid value(s) as options for the property, then merge the invalid option(s) with the correct, valid option(s). Check out this article for information about merging property options. Note: this won't work for single checkbox properties or other default properties like Persona or Lifecycle Stage because the property options are not editable.
  2. Create a list of contacts who have any value for the enumeration property by using the "is known" list filter for the selected contact property, then export those contacts. Once exported:
    • If the value that had been set on the contact matches the property option's label, you don't need to change anything; you can just reimport the contacts with that value because the import process looks for the property label (it's only via API where you need to pass the internal value).
    • If the value that had been set on the record does not match the property option's label, set the correct label, then reimport the contacts.
  3. Export the form submission data where the invalid values were set, then reimport the contacts with the property option's label.