Hello Joe

I'm not sure what you mean by ClearValue(TemplateProperty)!

My XamDataGrid has two fieldlayouts (master/nested), with different styling. What is the TemplateProperty are you are referring to?

The Template property that is defined by the Control class which XamDataGrid ultimately derives from. So if you set the  xamDataGrid.Template to 'null' and then call.ClearValue(Control.TemplateProperty) the grid's entire tree of elements should get re-created and therefore your converters should get called again.

Still not following...

I don't have a specific template for my XamDataGrid, only the FieldLayouts.

Could you post some sample-code?

In C# you would do this (assuming your instance of the XamDataGrid was named 'xamDataGrid1'):

this.xamDataGrid1.Template = null;

this.xamDataGrid1.UpdateLayout(); // This line is proabaly not necessary. I wouldn'use it unless it is.

this.xamDataGrid1.ClearValue(Control.TemplateProperty);

Hello Joe

I tried the above code and it didn't work for me.

The ItemsSource of my XamDataGrid is bound to a collection within an object. I could just try to "refresh" this collection, but this would keep the user waiting and might require a database-call.

Hi Christian,

You are correct, it doesn't work. My apologies for not trying this first. The reason is that we are caching the RecordListControl inside the data grid.

Here are 2 workarounds that I have tried that work:

1: Toggle the template of the RecordListControl inside the XamDataGrid (DG1)

 RecordListControl rlc = Utilities.GetDescendantFromType<RecordListControl>(this.DG1, true, null);

ControlTemplate

template = rlc.Template;

rlc

.Template = null;

rlc

.Template = template;

or 2: Toggle the RecordContainerGenerationMode:

this

.DG1.RecordContainerGenerationMode = ItemContainerGenerationMode.Virtualize;

this

.DG1.RecordContainerGenerationMode = ItemContainerGenerationMode.Recycle;

You can leave it set to 'Virtualize'.

However, that mode is not as performant when scrolling new records into view. In virtualize mode element trees for records that are scrolled out of view will be discarded and new element trees for records that are scrolled into view will be hydrated.

This differs from 'Recycle' mode (which is the default mode) where the element trees of records that are scrolled out of view will be reused for the records that are being scrolled into view. This results in a much smoother scrolling experience.

Hello Joe

Thanks for your reply!

I used the second method. Just one question. Is it correct that I need to set the "mode" to Virtualize first and then set it to Recycle, right after?

If I only use Virtualize the whole thing only work once...