This one is going to make a huge difference for data cleanliness and process enforcement.

This update, now in public beta, is available to basically all pro and enterprise hubs and lets you set and/or logic in those conditional property rules.

The Previous Workaround

In the past, I have seen people who create a “combination” property, for example taking two dropdowns and concatenating their values together, so these conditional rules can use a “contains” function to work off of both properties in concert.

That doesn’t help when one of the properties is a number or a date.

Now, we can build real criteria just like the list builder into these conditionals.

I am honestly not sure when they added this, but I found it a few weeks ago and it feels like a huge unlock.

We’re talking about the “data sources” tab within a property’s settings.

This is not even an easy report to make. This is not giving you values for the property itself. It is looking at the history across all records and giving you the sources of that property being updated.

It does require data hub professional, though.

If you need something similar, you’re best bet will be to export that property’s history from property settings and hand it to an LLM to tell you about what sources are changing it.