Specifies whether the provider expands association tables to include one table per object-to-object relationship.

Data Type

bool

Default Value

false

Remarks

This property controls how association data is represented in the schema. It is not available when Schema is set to HubSpot.

When set to false, the connector exposes one associations table per object type. For example:

• DealAssociations
• CompanyAssociations
• ContactAssociations

Each table returns the IDs of the objects associated with that type. For example, DealAssociations returns the IDs of objects associated with each deal.

When set to true, the connector expands the schema to include a separate associations table for each pair of related object types. For example:

• CompaniesToContactsAssociations
• ContactsToDealsAssociations
• DealsToLineItemsAssociations

These tables return pairs of IDs showing the relationships between the two object types.

Performance Considerations

Enabling this property increases the number of tables in the schema. This may improve clarity and querying flexibility when working with complex inter-object relationships, but could impact metadata loading time, especially in tools that introspect the full schema.

On the HubSpotV4, HubSpot202603, and HubSpotLatest schemas, the connector also batches requests based on how you filter the resulting association table's Id column with IN.

On the per-object-type tables exposed when this property is false (for example, DealAssociations), filtering by Id with IN combined with a Type predicate (for example, Id IN (...) AND Type = 'Company') retrieves associations for up to 1,000 objects in a single batched request, instead of issuing one request per Id. Filtering by Id with IN alone, without a Type predicate, does not trigger batching on these tables.

On the per-pair tables exposed when this property is true (for example, ContactsToDealsAssociations), filtering by the Id column with IN alone (for example, ContactsId IN (...)) is sufficient to retrieve associations for up to 1,000 objects in a single batched request, since setting this property to true is itself one of the two conditions that trigger batching.