However, it lacks one critical functionality: these sync fields currently can not be used as mandatory deal stage fields.
Use case: You have a field called delivery address on the primary associated company. Before the deal can be moved into Closed Won, that property must be populated. Making the sync property mandatory on the deal level forces the user to go to the company record and update it.
Having the ability to require synced fields for deals would be amazing - especially if it would allow the user to update the company record property without leaving the pipeline
Yes! This would really complete this feature. My use case is the sales rep needs to complete KYC process on the Company before the Deal can be moved to a Closed Won stage. I'm looking to place a 'KYC Complete' checkbox on the Company, and a sync property for that checkbox on the Deal. The latter, I want to make mandatory so reps know they have to go to the Company to complete that process.
EDIT: Either this, or the alternative solution of making properties on associated records mandatory in certain pipeline stages, see this idea.
Yes please. We're trying to reliably populate a property on deals based on a property value of an associated company, and then requiring that property before a deal is closed won. We're achieving that currently through a workflow which copies the property value from the Company to the Deal, but that workflow doesn't get triggered if the property is populated through a merge with another company, which happens quite regularly in our case. This is not a problem with the property sync properties (they also update if the Company property was populated after a merge), but the fact that I can't require those properties before a deal enters Closed Won prevents me from being able to solve this use case with them. That would be a much more solid solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
