Background:

In October 2022, in response to Salesforce beginning the process of sunsetting workflow rules and process builder in favor of flows, an architectural change was made in Rattle so that all newly created Rattles would leverage Flows instead of Workflow Rules. [More on that update here]

There are known parity gaps between Salesforce Workflow Rules and Flows, including some custom objects and fields not being supported by Flows.

If you attempt to add an unsupported field to an existing workflow created in SFDC using Flows, you may receive an error similar to the one shown above.

Solution:

Fear not! There is a workaround available.

By following the steps below, you will be able to create your Rattle with the unsupported field using Workflow Rules.

​​1. Click the duplicate button for the respective Rattle workflow.

2. Add the condition for the unsupported field and save your Rattle workflow.

After performing these steps, our engineering team has developed a system to identify the unsupported field and fall back to creating the Rattle using workflow rules.

If the issue still persists after following these steps, customers can reach out to Rattle's support team for further assistance on Slack by tagging @Support in our shared Slack channel.