Conditional Property Logic - Limiting Options Between Properties

My goal is to use conditional logic and workflows to enforce ‘pairings’ between the values in two custom properties. Can you please review and confirm if my suggestion is the best way to proceed?

Current Configuration

In our environment, our Deal records have two custom properties: ‘Type 1’ and ‘Type 2’. The ‘Type 1’ property has ~10 options which are the broad categories our deals fall under. The ‘Type 2’ field has over 100 options which are specific types that fall under the broad category in Type 1.

We’ve created a document that outlines what ‘Type 1’ and ‘Type 2’ options should be paired. However, we don’t currently enforce that with conditional logic.

An important note – we integrate with an ERP system and both properties are required for the integration.

Recommendation

To better enforce these pairings, I plan to do the following:

  1. Create a custom property for each of the options under ‘Type 1’. For example, a Type 1 option is ‘Bulk’. The property I create would be ‘Bulk Type 2’.
  2. Use HubSpot’s conditional logic to require the ‘Bulk Type 2’ property when ‘Type 1’ equals ‘Bulk’.
  3. Utilize a workflow to copy the property value from ‘Bulk Type 2’ to existing ‘Type 2’ property. Trigger would be ‘Type 1’ property value changed and ‘Type 1 equals Bulk’.

This should work based on my testing but I am afraid of the scalability. Are there other ideas/features that might help me reach my goal easier?

Hi @TWallen,

Instead of conditional logic, this sounds like a case for conditional options: Limit available options based on a controlling property

You would simply make both type 1 and type 2 required to fill. Whatever selection is made in type 1, decides which options are shown in type 2.

:slightly_smiling_face:

Best regards!

Thank you @karstenkoehler ! This feature is exactly what I was looking for.