Skip to content
  • There are no suggestions because the search field is empty.

What are Dynamic Property Sets?

Dynamic Property Sets lets Quotivity admins define which line item properties appear on a per-product basis in the Quote Builder. Instead of showing the same columns to every rep on every quote, your rules ensure that the right properties always show for the right product.

Example: Doors and Door Hinges

A building products company sells both doors and door hinges. Both products require reps to specify a Material, but the allowed values differ — doors come in Wood, Steel, and Fiberglass, while hinges come in Steel and Brass. Doors also require a Style selection (e.g., Panel, Flush, Louvered) that's irrelevant to hinges.

Rather than showing every property to every product, the admin creates two rules:

Rule Conditions Properties
Door Attributes Product Type = Door Material (required, options: Wood, Steel, Fiberglass) · Style (required)
Hinge Attributes Product Type = Door Hinge Material (required, options: Steel, Brass)

When a rep adds both a door and a hinge to the same quote, Quotivity evaluates each line item independently:

  • The door row displays Material (restricted to Wood, Steel, Fiberglass) and Style — both required.
  • The hinge row displays only Material (restricted to Steel, Brass) — required.
  • Neither product sees properties meant for the other.

If the rep tries to submit without selecting a material for the hinge, the field is flagged and submission is blocked until it's filled in.

Setting up Dynamic Property Sets

Navigate to the screen

In Quotivity Studio, navigate to the Dynamic Property Sets link under Rules Engine.

Create a rule

Click Create Dynamic Property Set to open the rule editor.

1. Name your rule

Give the rule a descriptive name (e.g., "Steel Door Attributes" or "Sliding Window Specs"). An optional description can help your team understand the rule's purpose.

2. Define conditions

Conditions determine which line items this rule applies to. Every condition evaluates a line item property — including product properties synced to the line item (e.g., Product Type, Category, Material).

These conditions are evaluated for each line item individually. When a line item matches the conditions, the properties configured below appear for that line in the Quote Builder.

You can add multiple condition groups. Within a group, conditions can be combined with AND or OR logic. Groups themselves are combined with the operator shown between them.

3. Select properties to display

Use the property picker to choose which HubSpot line item properties appear on matching line items in the Quote Builder. Properties are sorted alphabetically and searchable.

For each selected property, you can:

  • Toggle Required on or off — required properties display a red asterisk in the Quote Builder and must be filled before the rep can submit the quote.
  • Restrict allowed options (enumerated properties only) — click the option chip next to a property to limit which dropdown values reps can choose. If you restrict options, you must select at least one allowed value. Omitting a restriction means all HubSpot-defined options are available.
  • Reorder properties — drag rows to control the display order in the Quote Builder.

Some internal and system properties are excluded from selection (e.g., price, quantity, hs_product_id, Quotivity internal fields).

4. Save

Click Save. The rule becomes active immediately and applies to all quotes going forward.

Edit or deactivate a rule

From the Dynamic Property Sets list, click any rule to edit it. You can rename it, adjust conditions, add or remove properties, change required flags, or update option restrictions. You can also deactivate a rule to pause it without deleting it, or delete it permanently.

To create a rule similar to an existing one, use the Clone action on the list.

How it behaves in the Quote Builder

Rep experience

When a rep adds a product to a quote and executes it, Quotivity evaluates all active Dynamic Property Set rules. If one or more rules match a line item, the configured properties appear inline below that row — scoped to that product only.

  • Properties display with their HubSpot label and the input type matching the property's field type (text, number, date, dropdown, etc.)
  • Required properties are marked with a red asterisk (*)
  • Default values defined on the HubSpot line item property are pre-populated automatically
  • For dropdown properties with restricted options, only the allowed values appear in the picker
  • Rep-entered values write back to the HubSpot line item record when the quote is saved

If no rules match a line item, no additional row appears for it — the Quote Builder stays clean.

Submission validation

The Quote Builder uses standard form validation. If a required Dynamic Property Set property is left blank when the rep tries to submit, the field is flagged with an error message and submission is blocked until all required fields are complete.

Rule merging

When multiple rules match the same line item, their configured properties are merged automatically:

  • Properties from all matching rules are combined. If two rules both include the same property, it appears once.
  • Required flag uses OR logic. If any matching rule marks a property as required, it is required in the merged result — regardless of how other rules configure it.
  • Option restrictions are unioned. If two rules each restrict the same dropdown property to different option subsets, the rep sees the combined set of allowed options from both rules.

Tips for keeping rules manageable

  • Use product-class conditions, not SKU conditions. A single rule targeting Product Type = Door covers every door in your catalog. Rules targeting specific SKUs require more maintenance as your catalog grows.
  • Use descriptive names. Names like "Commercial Door Attributes" are easier to scan than "Rule 3."
  • Start with optional properties, then add required ones. Roll out new attribute fields as optional first; flip them to required once reps are familiar with the workflow.
  • Deactivate instead of delete when testing rule changes — you can re-enable a deactivated rule without rebuilding it.