TIBCO Scribe® has released an update to the Connector for HubSpot that includes the following changes: 
 

• Querying the Engagement entity for a small number of records sometimes generated the following error: Error converting value {null} to type 'System.Int32'. Path 'offset', line 1, position 1251. Null object cannot be converted to a value type. " (57601, 58230 / Case # 62649)
• Updated the API endpoint used for the Form entity to a HubSpot V2 API Endpoint. (55070)

IMPORTANT NOTE: Forms created in the HubSpot UI can contain rich text fields used to display descriptions or notes about the Form.  The information contained in those fields is not actual Form data, but part of the Form itself.

The contents of these fields were returned in the metadata for the Form entity from the HubSpot V1 API endpoint and could be mapped. Now that the Connector uses the HubSpot V2 API endpoint, the rich text fields are no longer provided in the metadata as fields, but as a property that cannot be modified and cannot be mapped.

If you have any of these rich text fields mapped in the Submit operation of a Map, the Connector will ignore them when comparing them to the metadata and will pass them through to HubSpot in the Submit target operation. However, best practice would be to reset metadata and remove them from your Maps. Field names displayed for the rich text fields in the TIBCO Scribe® Online field mapper are similar to the following:

hs_rich_text_213709b622c40374cc821a587b522637b3d36358


NOTE: To access any changes to metadata support, such as new API endpoints, operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata in the TIBCO Scribe® Online Help.
 
For additional information on this Connector, see Connector For HubSpot in the TIBCO Scribe® Online Help.



 

Release notes for the January 31, 2018 release of the Connector for HubSpot.