Starting with the Winter '18 release, Salesforce added validation to Process Builder to ensure that object names referenced in formula syntax use the correct case. In Process Builder, field references in formula syntax must begin with the name of the object the process is built on, enclosed in square brackets (e.g., [Case].CreatedDate for a Process on the Case object).
Prior to Winter '18, this validation did not exist. As a result, existing Processes may contain formulas with incorrect object name casing (e.g., [case].CreatedDate instead of [Case].CreatedDate). When attempting to save or clone such a Process in Winter '18 or later, the following error appears:
"The object referenced in the square brackets must be [Object Name]"
If the incorrect object reference appears in only one element of a draft Process, the fix can be made directly in Process Builder:
[case] to [Case]).If the incorrect object references appear in multiple elements, or if the Process is or was previously active, the error cannot be corrected in the Process Builder UI. The Process must be retrieved via the Metadata API, edited in the .flow file, and redeployed as a new version.
Important Note: Manipulating metadata is beyond the scope of Salesforce Support. Use caution when following these steps.
Steps using Workbench:
package.xml with the following content, replacing the members value with your Process name and version number:
<members> to the name and version of the Process (e.g., My_Process-4 for version 4 of a process named "My_Process")<version> to 40.0 or the appropriate API versionpackage.xml file, check the Single Package checkbox, and click Next.package.xml file and a flows/ folder with the Process .flow file.My_Process-7.flow)<members> value in package.xml to match the renamed .flow filename000383560

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.