Skip to main content
J
janakiramk524063
April 24, 2026
Question

Checkbox Control in UI -- saveinto (NOT saveInto)

  • April 24, 2026
  • 2 replies
  • 0 views

Has anyone else noticed this in checkbox component. The expression mode does not show error when i have both saveinto and saveInto (notice the difference "i" vs "I"). I am able to save, and the selected value is not getting saved as expected. The expression mode does not show the parameter as invalid for "saveinto" and also does not save the value.

 

I always thought the correct syntax is saveInto with capitalized "I"

Janaki Ram

2 replies

stefanhelzle0001
stefanhelzle0001
April 24, 2026

I tried to replicate this. Saving the value works for me. The saveInto is evaluated and the saveinto is ignored.

shubhama926776
shubhama926776
April 28, 2026

Yes, ideally the expression editor should warn about duplicate use of the same parameter, but in this case Appian is not flagging it because saveInto is the documented parameter and saveinto is being tolerated due to case-insensitive parameter handling in the component parser.
So your point is correct: from a developer experience perspective, Appian should highlight this as a duplicate parameter or invalid usage, but currently it appears to be a parser/editor limitation rather than expected validation behavior.

Terms & ConditionsAccessibility statement