Hello again,

I got another problem with name binding. It seems that I'm unable to bind to properties that are defined on the base class of my view model. This is the same in your sample application. I get following error in vs output:

A new FieldLayout is being created because none of the supplied FieldLayouts matched for the following reasons:
Fieldlayout: ' - 8 Fields - index = 0' was not matched because of the following reason:
	There was no property found with a name of: 'IsChecked'. Note: name matching is case sensitive.

Regards

Hello Andrew,

I can't reproduce it in the sample project either (I just made a mistake yesterday). But I'm not able to get it to work in one view in our application. I tried to create a sample project, but I am unable to reproduce the behavior. We got the (almost) following structure in our code:

public class SampleData : SampleDataBase<ISomeModelInterface>, ISampleData
    {
        public SampleData(string name, long? id, string userName, string number, decimal sum, decimal? otherSum)
            : base (number, sum, otherSum)
        {
            this.Name = name;
            this.Id = id;
            this.UserName = userName;
        }

        //i can bind to these
        public string Name { get; private set; }
        public long? Id { get; private set; }
        public string UserName { get; private set; }
    }

    public interface ISampleData : ISampleDataBase
    {
        string Name { get; }
        long? Id { get; }
        string UserName { get; }
    }

    public abstract class SampleDataBase<TModel> : SomeOtherBaseClass<TModel>, ISampleDataBase
        where TModel : class, ISomeModelBaseInterface
    {
        protected SampleDataBase(string number, decimal sum, decimal? otherSum)
        {
            this.Number = number;
            this.Sum = sum;
            this.OtherSum = otherSum;
        }
        // I cannot bind to these, Field Layout error Propertyname cannot be found but the values are displayed in the view.
        // on the grid there are 2 FieldLayout definitions one with all fields (typeof SampleData), one with 0 fields (typeof ISampleData)
        public string Number { get; private set; }
        public decimal Sum { get; private set; }
        public decimal? OtherSum { get; private set; }
    }

    public interface ISampleDataBase
    {
        string Number { get; }
        decimal Sum { get; }
        decimal? OtherSum { get; }
    }

As I mentioned in the comments, I get the PropertyName not found error for all the properties in SampleDataBase. But only in our main application not in the sample. I don't get why the error is thrown and a new FieldLayout is generated but the property value is correctly displayed in the field.

Regards

Hello Andrew,

I'm sorry for my late response, I tried various constellations in our application. Only sometimes, the xamdatagrid seems to be unable to bind to inherited properties, on some views it works like in your sample application. If I use alternate bindings it always works without exceptions. If I use name binding the values are correctly displayed but I get the property not found exception in the output window. I'm also curious as why I always find 2 FieldLayouts. The first, which contains all fields, is of the type of the class itself, the other which contains no fields is of the type of the corresponding interface.

Edit: If I remove the inherited properties from the FieldLayout the layout type is of the Interface. If I add the Field back I get 2 FieldLayouts, one from the Interface with no Fields, one from the corresponding class with all the fields

Do you have any further ideas?

Regards

I think I've found the problem.

In the sample applications we don't use the UnityContainer to resolve the Interface and set the data collection to items of the resolved interface. In the sample application the FieldLayout type is always the type of the class itself. Using the UnityContainer to resolve the interfaces for the items in the collection the FieldLayout is generated from the interface. Which results in the binding exception, because the Interface itself has no property with the specified name, even if it inherits an interface which has the member. If I hide the member of the base interface in the derived interface with new, it works as expected.

I'm unsure on how to fix this because we heavily rely on the UnityContainer and I'm not realy a fan of adding the property to each of my interfaces and hide the base member.

Hello Matthias,

Thank you for your update(s).

Regarding the two FieldLayouts, I think this is likely due to the error message that you are seeing that “a new FieldLayout is being created…” This will effectively keep your current FieldLayout but use the one that is being created. The one that is being created is being created because in your XAML, it does not appear that you currently have the XamDataGrid.FieldLayoutSettings.AutoGenerateFields property set to false – this defaults to true.

Regarding being able to explain why this is happening in the first place though, I am really not sure as I don’t believe I completely understand what is going on with the resolution of your interfaces. As I am really unsure what is happening and I have no experience at all with UnityContainer, would it be possible for you to please modify the sample project that I sent you such that it implements these pieces and reproduces the behavior you are seeing? Alternatively, if you have an isolated sample project of your own that reproduces this, then would it be possible for you to please provide that?

Please let me know if you have any other questions or concerns on this matter.