Available in the 2018 R2 SP release.
Setting DataFormPasswordEditor inside a custom renderer on Android leads to the following exception:
Java.Lang.NullPointerException: Attempt to invoke virtual method 'java.util.Iterator java.util.ArrayList.iterator()' on a null object reference
If the following data annotations are defined: [DisplayValueFormat(Date = "MM-dd-yyyy HH:MM tt")] [ReadOnly] DisplayValueFormat is not applied properly.
The segmented editor does not change the underlying property immediately.
Please refer to the attached project that reproduces the issue. In the MainPage constructor, you can switch between using the PickerEditor (validation works) and the SegmentedEditor (validation doesn't work).
// Works with validation
dataForm.RegisterEditor(
"Location"
, EditorType.PickerEditor);
// Doesn't work with validation
//dataForm.RegisterEditor("Location", EditorType.SegmentedEditor);
This prevents content below the control to be visible. Available in the R2 2018 release.
There is an empty group title view above the editors even if there are no groups. The red area on the attached screenshot.
On UWP, the IntegerEditor has a default max value of 100. This is not present on other platforms. Current Workaround The workaround is to explicitly set the max value via a NumericalRangeValidator E.G. [NumericalRangeValidator(int.MinValue, int.MaxValue)] public int PropertyName { get; set; }
When DisplayValueFormat is set to an Integer property, Zero value is not applied.
If an editor does not have positive/negative feedback, an empty text view still appears after validation and shifts the editors. Available in the 2017 R2 SP release.
When the decimal separator is comma "," for example on a device with Spanish location (es-ES), and the source property is of type decimal, the DecimalEditor of RadDataForm does not receive the decimal separator.
The issue is not reproduced with properties of type double.