Tips, Tricks & Best Practices

MRoberts8
Participante

Making a deal property required based on other properties

resolver

We have a deal property that is required at the Closed Lost stage of a deal, but we want to make it not required/appear if the Closed Lost customer is in a certain industry segment (captured in a segment deal field at deal creation). 

 

I know conditional property logic can make it so that if a property equals a certain value you're prompted to fill in another, but is there a good way to filter what is required? Especially when the thing being used to filter appears at different deal stages?

0 Avaliação positiva
1 Solução aceita
karstenkoehler
Solução
Membro do Hall da Fama | Parceiro
Membro do Hall da Fama | Parceiro

Making a deal property required based on other properties

resolver

@MRoberts8 thanks for elaborating. In that case, correct, this can currently not be done. It's not possible to configure conditions based on the deal stage.

 

There might be a workaround by copying the industry value to a clone of that field via a workflow, once it's known. This would not trigger the dependent field and you could make that field view only in Enterprise, reducing the risk of it being edited. In the closed deal stage, you could make it required and set up the conditional field based on this clone.

 

I haven't tried this but it might work.

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

Exibir solução no post original

0 Avaliação positiva
3 Respostas 3
MRoberts8
Participante

Making a deal property required based on other properties

resolver

I might be being dense.

 

Someone enters the industry at the first stage of the deal ahd the property in question is something entered at the Closed Lost stage, so i basically would not want the rep to enter Industry A, B, or, C and then be required at the first deal stage to fill out a Closed Lost-specific field.

 

But when they get to Closed Lost, I want the field in question to only be required for Industry A, B, C. My understanding is the way conditional property logic works is it prompts the dependent field immediately after the first field is filled in.

0 Avaliação positiva
karstenkoehler
Solução
Membro do Hall da Fama | Parceiro
Membro do Hall da Fama | Parceiro

Making a deal property required based on other properties

resolver

@MRoberts8 thanks for elaborating. In that case, correct, this can currently not be done. It's not possible to configure conditions based on the deal stage.

 

There might be a workaround by copying the industry value to a clone of that field via a workflow, once it's known. This would not trigger the dependent field and you could make that field view only in Enterprise, reducing the risk of it being edited. In the closed deal stage, you could make it required and set up the conditional field based on this clone.

 

I haven't tried this but it might work.

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

0 Avaliação positiva
karstenkoehler
Membro do Hall da Fama | Parceiro
Membro do Hall da Fama | Parceiro

Making a deal property required based on other properties

resolver

Hi @MRoberts8,

 

What would speak against showing the required property for industries A, B, C, assuming that those are the ones where it applies, and D, for example, not? What do you mean when you say "is there a good way to filter what is required"?

 

From what I understand, this should work for you: https://knowledge.hubspot.com/properties/set-up-conditional-logic-for-enumeration-properties

 

Best regards

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

0 Avaliação positiva