Hi! I’ve been looking into using the new conditional property logic in our account. But, before going through all the trouble of setting it up, I was hoping to get some information on how reporting works with these conditional properties.
Can you create reports using dependent properties? Can you create reports using the controlling property, and display the dependent properties? Are there any issues that arise with this?
Second, is it possible to update these properties using workflows? What happens if a workflow tries to update a dependent property to an entry that isn’t available for the contact (because the controlling property doesn’t align)?
Last question - can these fields be added to forms? I assume the controlling property will be fine, but is it possible to add the dependent field? And if so, would the options update with their selection of the controlling property?
Thanks for the help!
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
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)
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
Hi @karstenkoehler !
Thanks for the information, its incredibly helpful!
So say we’re using conditional properties to record attribution - since the logic doesn’t apply to forms, could we potentially use GCLID/UTM parameters to set the primary source (ie google ads) and secondary source (ie campaign name)? Primary source, our controlling property, would also include selections like “word of mouth” or “tradeshows” that would be filled out manually by our reps. Is this functionality possible? is there a way to create logic to parse the utm parameters to pull out just what we need to populate the controlling/dependent properties?