# Conditional Property Reporting, Workflows, and Forms **URL:** \ **Category:** Tips, Tricks & Best Practices\ **Tags:** how-to\ **Created:** [January 29, 2024, 6:41pm UTC](https://community.hubspot.com/t/conditional-property-reporting-workflows-and-forms/98915 "2024-01-29T18:41:10Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\ **Post date:** [January 29, 2024, 6:53pm UTC](https://community.hubspot.com/t/conditional-property-reporting-workflows-and-forms/98915/2 "2024-01-29T18:53:54Z")
Hi @JLittle2, Conditional property logic is “enforced when creating records and when manually editing values on a record or an object index page”, see here: [Set up conditional logic for enumeration properties](https://knowledge.hubspot.com/properties/set-up-conditional-logic-for-enumeration-properties) That’s why workflows and forms don’t respect the logic. Workflows ignore dependent property logic. It is not enforced in workflows. You can set the controlling property value without being prompted to set the dependent one. The logic does currently not apply to website forms either. Website forms only support dependent fields: [Use dependent form fields (legacy)](https://knowledge.hubspot.com/forms/use-dependent-form-fields) Reports work exactly the same with conditional property logic as they did before. If you want to see the controlling property broken down by the dependent property, you would do exactly that: You would visualize the controlling property and the count of contacts/companies/deals/tickets, then add a breakdown by the dependent property. In other words, dependent property logic doesn’t affect reports. The work as usual. Best regards --- _[View the full topic](https://community.hubspot.com/t/conditional-property-reporting-workflows-and-forms/98915)._