5 Answers, 1 is accepted
It will be better to send us a sample project where the problem can be reproduced. If this is not possible for you please give us some more details about the grid and the defined columns.
Best wishes,
Yordanka
the Telerik team

https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B88SmcJsxJySNDU0MzI3ODItOWNhZC00NWYyLWJkZWQtNzUyYzExZDRlNWU4&hl=en_US
Regards,
Vali
The UniqueName is a "ghost from the past" property that we are currently trying to obsolete. The correct way to bind columns is to use the DataMemberBinding property. Please, don't use UniqueName. It was left for compatibility purposes only and will soon be gone, I hope.
Regards,Ross
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>

Thanks!
If the column was bound to "LastName" with DataMemberBinding for example, you can get it back like this:
column.DataMemberBinding.Path.Path
will return "LastName".
You can add checks for null before each consecutive property access of course. However, this is not unique, since we can have 10 columns bound to "LastName', but I doubt that you will actually do that in your real-world project.
I hope this helps.
Ross
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>