Hello all. We have a workflow/record type for which workflows and records should be synced to Ironclad Workflows and Ironclad Contracts in Salesforce only when they have a Salesforce Account ID populated, and should not be pushed to Salesforce if they do not have a Salesforce Account ID populated. I've had several conversations with Ironclad Support and have been told that if the workflow is configured for Workflow Sync and Record Sync, all workflows and records for that workflow configuration and record type will be sent to Ironclad Workflows and/or Ironclad Contracts even though it doesn't have an account to attach it to, and there is currently no way in Ironclad to prevent that. As a workaround, they suggested setting up a flow action on the Salesforce side to stop the Ironclad push if there isn't a Salesforce Account ID populated in the workflow or record. We are working on that now, but confirmed with Ironclad that the flow action will not prevent Ironclad from flagging and emailing an integration error for every workflow or record which does not have a Salesforce Account ID (which is getting increasingly annoying). Has anyone else encountered this issue and found a workaround in Ironclad that would prevent the sync to SF for the ones that shouldn't sync while also preventing Ironclad from flagging it as an integration error?
