Nullable int property is validated against range when no data is input.

 When a field is of type Integer and is configured to use IntegerEditor, currently it is shown with a decimal point

Numeric and date editors are not aligned identically to the other editors inside the dataform

The maximum value that the DecimalEditor can set seems to be 100. If the underlying property is more than 100 it automatically sets it and you cannot increase it through the UI.

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; }

Available in minor release 2018.1.202. It will also be available in the R1 2018 SP release.

Built the SDKBrowser project for iOS, using VS 2017 and latest stable Xamarin.Forms.
When editing a field, the OS keyboard appears and above it are "Prev" and "Next" buttons for moving between form fields.  Those buttons behave erratically.  Attached 2 images.

01: the 1st field is focused.
02: after pressing Next, the 3rd field is focused ("Age").

Pressing Next again does not change which field is focused, and Prev becomes active.  Pushing either Prev or Next does nothing at all.

Available in the 2018 R2 SP release.

With the current implementation in Xamarin.Forms, the control has no built-in support for enumerable properties. The approach is to create custom renderers and use the native editors.  We need to expose default editors for enumerable and custom types.

Currently, all groups are expanded by default. We should expose methods to collapse/expand certain groups. Furthermore, CollapseAll, ExpandAll groups should be considered as well.

In Xamarin.Forms, there is no multiline text box editor in RadDataForm.

Provide capability to replace the native view with Xamarin Template.

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.

There is an empty group title view above the editors even if there are no groups.
The red area on the attached screenshot.

We need to simplify the way the editors can be customized.  XAML only solution would be great.