to be more specific, the default value of the text field argument (that can be set when editing the custom commands), can't set with a value having a colon ":", when doing so, the field description get strange charachters and the default value will have the colon removed.
as for passing the argument, it was a mistake that i couldn't handle on my script but i got it fixed.
to summarize: field description and actual value passed can have colon, just the default value of the field won't
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you mean the value of the field cannot contain ":" , or the name cannot contain ":" ?
to be more specific, the default value of the text field argument (that can be set when editing the custom commands), can't set with a value having a colon ":", when doing so, the field description get strange charachters and the default value will have the colon removed.
as for passing the argument, it was a mistake that i couldn't handle on my script but i got it fixed.
to summarize: field description and actual value passed can have colon, just the default value of the field won't
for exmaple
checking the .cmd file
BALANCE_EXPIRATION_VAL:0:Exp Date:0,0:Credit Exp: "actual text before exp" date
in this caes, the defualt field value "Exp Date" can't have a colon ":" in it, otherwise it would shift whats after it to the field description
This isn't easy to fix with the current format, but I can at least add a check to prevent use of : in that field.