👋Hi all! I'm Rachel from the Product team. An update for you - we are now in private beta for Conditional Property Logic, a feature that will enable you to set conditional logic for enumeration properties. This logic will be triggered when users make edits to properties across the CRM - specifically, in the ‘create record’ form, on the record page, and on the index page. If a property is required, users will not be able to save their changes until the required property has been filled. This feature is available for all Hubs, Professional+ subscription.
Your Customer Success Manager can request access to this beta on your behalf. We plan to move this feature to public beta in the near future based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!
@rwebb1 Are you planning to expand this logic to be compatible with non-checkbox/radio/dropdown properties? I understand this could add quite a bit of complexity, but even just an "is known"-style condition to trigger when someone fills out a text-input property would be incredibly useful. Thanks!
I second the comment above. Our need for this stems to date picker fields, which is not available in this public beta. We need reps to be forced to update required fields any time they are edited, specifically date pickers.
@rwebb1 Super excited about this update! Just for my reference, do you expect down the line this logic will either work alongside or replace the conditional logic built with dependent fields in forms? This is another portion (that although admittedly not the exact same) is a similar issue I often see our clients run up against.
It's great that this is being worked on, but I'm worried that it's in public beta already with the extremely limited functionality that's implemented. We need to be able to add AND/OR functions, and have conditions other than "Equal to". I need to be able to choose "If Property A is known, then make Property B a dependant field", and I need to be able to make Property X required if BOTH Property Y AND Property Z are populated. I understand it's still only in beta, but the way it's currently implemented with only being able to choose "equal to" and only being able to choose a single field value, and with no AND/OR, doesn't make any sense.
And of course, like others have mentioned, all field types need to be supported.
I'd like it if every time I engaged with a property that had conditional logic it would open the dependent properties window for viewing even if the controlling property had been previously filled out and saved. A way for my users to easily access the Dependent properties without having to edit the controlling property would really help our users workflow in our custom objects.
I agree with the others that have said having the conditional logic check for only being "equal to" is very limiting. It's a great start but should mimic the behaviors of the other logical checks you have already available in workflows, reports, etc. i.e. "is known", 'is any of....[multi-select] value", and other options would be more along the lines of what I would need for my use-case.
For instance, if my users populate X-field (regardless of value) require that Y-field is populated.
We are happy that this was finally implemented. One of the first couple of things that I notice with it is that we are unable to apply the dependent logic to all values in a certain property. We would like to choose an event, and then choose whether they were invitied, registered, attended or a no show. Unfortunately, we have to create a new logic for each value under this property. This leads to the next issue which is that we cannot pace these logics into folders to help keep them organized. The dependent logic need to be more visible after selecting the controlling property, you have to look for the arrow and pull up the dependent property. The UX needs a little work.
I'm using the public beta. Why is it not possible to write a condition based on Lifecycle Stage? If that property is essential to managing contact/company status, why can't we use that?
This is a great addition, alls we need now if the ability to clone these!
Going through each pipeline and stage to add conditional fields can take an age. If we can clone and edit groups of conditional property logic, that would be awesome
Limiting this to enumeration properties only is not very helpful. The idea of conditionally required properties would be much more useful if we could bind to any Property. For example, I have several use cases where if a particular property has any value, then I need to require a value in another property. I also have use cases where if a property has a specific value (multi-select drop down), then there are other properties that I need to require on the Deal.
The current implementation doesn't help me in either of these cases.
Yet I don't understand why this has not been set up for Lifefcycle stages. To me, the Lifecycle stage is the most crucial stage that this feature affects. As the original poster said, it is crucial to ensure sales are updating records properly. We require certain fields to be known in order for a contact to be considered an MQL, SQL and etc so it would be extremely helpful to prevent a person from changing the lifecycle stage until certain fields are filled out.
