When creating a new Variable in Salesforce Flow, you must follow specific naming rules for the Object API Name field. Violating these rules will prevent the variable from being saved.
Naming Rules #
- ✅ Use single underscores between words (e.g. cadmusformProject_forCreate)
- ✅ Write all words together with no underscores (merged) (e.g. cadmusformProjectforCreate)
- ❌ Do NOT use double underscores (“__”) (e.g. cadmus_form__Project_forCreate)
- ❌ Do NOT start or end the name with an underscore (e.g. _cadmusformProject or cadmusformProject_)
💡 Tip
If your intended name contains double underscores (“__”), simply remove all underscores and write the name merged together.
Example
cadmus_form__Project__c -> cadmusformProject_forCreate (all underscores removed, suffix _forCreate kept)
Why this restriction exists #
This is a Salesforce platform restriction — double underscores (__) are reserved for custom objects and fields (e.g. My_Object__c) and therefore cannot be used in Flow variable API names.
Screenshots — Step by Step #
Step 1 #
Enter the original object name with double underscores — Salesforce will show a validation error:
❌ cadmus_form__Project_forCreate — invalid, double underscores not allowed
Step 2 #
Remove all underscores from the object name prefix and use the merged version — the variable saves successfully:
✅ cadmusformProject_forCreate — valid, variable saved successfully
Where to Find the Field API Name & How to Use It in Flow #
Field API Name in Actionable — This is the original Field API Name as it appears in the FORM Butler configuration (e.g. cadmus_form__Project__c). Note the double underscores — this value cannot be used directly in Flow.
Field API Name in Actionable — cadmus_form__Project__c
Variable API Name in Flow — When creating the corresponding variable in Salesforce Flow, remove all underscores from the object name prefix. Use the merged version: cadmusformProject_forCreate.
Variable API Name in Flow — cadmusformProject_forCreate
