There are different approaches that could achieve that goal:
1. If you know exactly what the new columns will be you can use wrapper on your classes and define your artificial fields as properties.
2. If its not your case:
a) Use Dictionary with Key - Artificial Field name, and value - Artificial Field value. Then you can easily bind Dictionary to control in WPF, only taking care when you save artificial fields in database.
b) You should implement IValueConverter with artificial type as value, and artificial field as parameter, but it will be more difficult to implement in TwoWay binding mode.
Do not hesitate to get back to us if you have any questions regarding the usage of Artificial Types.
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.