Old Name was. "Implement a feature to change the Value property based on the Text property ". However, Value is the primary property for this control and that is why we want clients to use Value property, not two-way binding of the Text property that changes the Value internally. That is why we changed the name of the feature request. Its meaningful and clients will benefit from it. Basically clients want the literals to be included in in the VALUE. And this is meaningful only in TextInput. So new property in RadMaskedTextInput (for ex. IncludeLiteralsInValue) seems fine - Estimate 10. Example Scenario: Mask="##--##--##", User types 123456, Value property becomes "12--34--56" which will have the same value as the Text property. Example Scenario: IP Address SDK demo. Look at its code - there is converter in file and convert methods in ViewModel.cs. Both Value and Text are bound. If Value includes the dots, only 1 converter and 1 2way bingding would do the job with less code.