workaround is to override the OnInitialized of the custom column:

 protected override void OnInitialized(EventArgs e)
        {/* //if XAML assemblies

            Theme theme = StyleManager.GetTheme(this);
            Type themeType = null;
            if (theme != null)
            {
                themeType = theme.GetType();
            }
            this.DefaultStyleKey = new ThemeResourceKey() { ElementType = typeof(Telerik.Windows.Controls.GridViewColumn), ThemeType = themeType };*/
        }

As a temporary workaround, the following custom keyboard command provider can be used:

	public class CustomKeyboardCommandProvider : DefaultKeyboardCommandProvider
	{
		private GridViewDataControl parentGrid;

		public CustomKeyboardCommandProvider(GridViewDataControl grid)
		 : base(grid)
		{
			this.parentGrid = grid;
		}

		public override IEnumerable<ICommand> ProvideCommandsForKey(Key key)
		{
			List<ICommand> commandsToExecute = base.ProvideCommandsForKey(key).ToList();

			if (key == Key.Enter)
			{
				commandsToExecute.Clear();
				commandsToExecute.Add(RadGridViewCommands.CommitEdit);
				commandsToExecute.Add(RadGridViewCommands.BeginEdit);
				commandsToExecute.Add(RadGridViewCommands.MoveDown);
			}

			return commandsToExecute;
		}
	}

DataFormatString is not respected when exporting RadGridView to .xlsx file and a GridViewDataColumn is bound to a nested property.

Available in LIB version: 2017.2.605

When an Extended selection is performed by the user, the items programmatically added to the  SelectedItems collection need to be taken in consideration. Currently, they are not  A scenario with a source collection of 10 items  and the item at index 4 being added to the SelectedItems of the control can serve as an example. If the user presses Shift+Down, the expected result would be the items at index 4 and 5 to be selected. Instead, all items until the item at index 5 are selected. The same behavior can be reproduced with Shift+Click as well.


Available in LIB version: 2017.2.605

Available in LIB version: 2017.2.529

When pasting data to create new rows(which are created in the AddingNewDataItem event), the pasting logic on the existing cells stops working.


Available in LIB version: 2017.2.529

Available in LIB version: 2017.2.522

Available in LIB version: 2017.2.515

Available in LIB version: 2017.2.515

The issue is replicated only when a filtering operation is applied. For a grouping and sorting one it is not. This behavior is replicated in WPF only.

UPDATE: The issue is reproduced with columns bound to other data types as well.

Can you add a grid-level option to hide any grouped columns automatically (rather than at the column level)?

I've tried creating a attached property behavior to do this (see attached), but it doesn't work well with auto-generated columns.