OK... I have kindof a sepecialised case. I am getting log data back from a DB that has 5 static properties and then any number of variable properties. The class looks like this:
Prop 1, prop 2, prop 3, collection of properties 4-n... all possible properties are known.
Based on the type of log, properties 4-n will be different, again, all possible properties will be known.
The values of these properties will always be text.
binding properties 1-3 are easy... but is it possible to bind column values to items within a sub collection? for example, key="{Binding PropCollection.Prop4}"
Thanks in advance for any help
Marc
Well I am confused on your problem. If your problem is creating the columns then many approaches were posted previously, including the one I suggested here.
If your problem is grouping and sorting, well that is just a limitation of TemplateColumns in the XamDataGrid for now, and you may want to try Stephen's suggestion of trying the unboundColumn in the 10.1 CTP.
Hi Ted,
I'd recommend you check out our 10.1 CTP, which introduces a new column type, called UnboundColumn.
The way the UnboundColumn works, is it allows you to specify a ValueConverter, and we can use that to allow GroupBy and Sorting without any additional work. You don't even need to specify a DataTemplate, as we'll use the value from the ValueConverter to fill the cells for that column.
Hope this helps,
-SteveZ
So what are my options? I essentially have a IDictionary that is my main datasource that gets returned by my SOA layer for all calls to my application server. The dictionary object is also used heavily in all our clients including our WPF based clients where binding with a index works ( Text="{ Binding datasourceprops [fieled] }" ) so i cannot duplicate data objects on the client, im stuck with the the IDcitionary
in silverlight I wrote a converter for all fileds that pull out the correct values from the dictionary, what can i do in the Infragistic grid? any ideas?
thanks
Upon further testing, sorting causes the same error as Grouping
That is because currently functions such as sorting, grouping, and filtering do not work on template columns.