We're using XamDataGrid v11.2 and we get one BindingExpression path error for each XamDataGrid as it renders. The whole message is:
BindingExpression path error: 'FieldLayout' property not found on 'object' ''GridUserControl' (Name='')'. BindingExpression:Path=FieldLayout.AutoFitToWidth; DataItem='GridUserControl' (Name=''); target element is 'DataRecordPresenter' (Name=''); target property is 'NoTarget' (type 'Object')
The data context for the whole user control is pointing to our GridUserControl object and the XamDataGrid inherits that data context (we set the DataSource for the grid). The binding expression (FieldLayout.AutoFitToWidth) must be something internal to the XamDataGrid. I have searched our code completely (not case sensitive, not whole word, entire soluton, *.*) and there are no occurances of AutoFitToWidth (and any occurances of FieldLayout are not used in binding expressions).
Am I right that this is an internal issue with XamDataGrid v11.2? Is there anything I can do to get rid of this error (we log all binding errors and customers may be confused if they see this in our log)?
Thanks,
Mike
Hello Mike,
Thank you for your feedback. I am glad that you resolved your issue and I believe that other community members may benefit from this as well.
Thanks again.
I just thought I would pop in and mention that I have tested the SR and it does indeed solve the problem.
Hello,
We have shipped out a new service release where your issue is resolved. I'd be glad to find out if you had tested it out and if it had met your requirements.
You can download the Service Releases by logging to our web site and going to My IG \My Keys and Downloads.
Thank you for your response. I did try to reproduce it in a sample project but I could not . I will let you know as soon as i am able to reproduce it .
I have checked the issue state and I can say that it will be fixed in our next service release, which is planned for March 14, 2012. Also it will be great if you could provide an isolated sample project, where the issue is reproduced, so we can verify if it has already been fixed .
Looking forward for your reply.