Haven't find a right section to post this.
When I use Grid, Grid headers doesn't respect their 'display name' but instead Fieldname. Am I missing some sort of setting here?
Hello powerbala,
I have been researching your issue and have submitted it to our development team with id: 96703 for further investigation. I have also created a support ticket (CAS-78456-G91B10) on your behalf in order to link the development issue to it and you get an automated notification when it has been resolved.
Thank you for reporting this to us.
Hi Elena,
I have the same issue. May I also be contacted when a fix is available.
Kurt Radamaker
Hello Kurt,
I also created a support ticket with number CAS-81018-BJWNY5 on your behalf in order to link the development issue, so you get an automated notification when it has been resolved. Furthermore I can ensure you that as soon as the service release containing the resolution of the issue is available, I will update this forum thread, so the other community members can benefit from this too.
Has this issue been resolve? Please include me on the notifications.
Thank you
Hello,
The issue that you reported has been fixed in our new version 12.1. You can download it from the following link:
http://ko.infragistics.com/dotnet/netadvantage/lightswitch.aspx#Downloads
if you need any additional assistance on this please feel free to ask.
We upgraded to version 11.2.20112.1010 and the Grid still does not use the correct column headers(Display Name:). Configuration information: VS 2010, LS 2011 current service pack and security updates. Created a new LS application with one table called TEST, table with 3 columns called Column1, Column2, Column3More. Display name for column3more is 'Column 3 More'. Used Infragistics Grid Row control in a List and Details Screen called TestScreen. When we run the app the column headers are still using the General, Name: not the General, Display Name. Are we using the correct version? Please advise ASAP! Thank you, Chris canderson@smarttracklogistics.com
We have resolved this issue in our new version 12.1 therefore I can suggest you just upgrade to it:
http://ko.infragistics.com/dotnet/netadvantage/lightswitch.aspx#Overview