The special characters in the column names are incorrectly parsed by the binding path parser.
So a column binding to 3/4 is actually only binding to the property 3, and not the property 3/4. (The same thing with the . binding)
You'll probably see binding errors in the debug window while this is running that should say the same sort of thing.
System.Windows.Data Error: 40 : BindingExpression path error:
'3' property not found on 'object' ''DataRowView'
According to this answer
There are a number of different characters which have special meaning
in a binding path including full stop ('.'), slash ('/'), square
brackets ('[',']') and parenthesis ('(',')'), the parenthesis will
cause your app to crash. These special characters can be escaped by
surrounding the binding path with square brackets. More information
about paths and character escaping can be found in the [Binding
Declarations Overview][2]
That linked question also contains a good solution for dealing with grids that want to use auto-generated columns.
Use the AutoGeneratingColumn event, and manually create the bindings for columns with these special characters in their name to escape them using the square brackets.
<DataGrid x:Name="dgLFKPI"
AutoGeneratingColumn="dgLFKPI_AutoGeneratingColumn" />
private void dgLFKPI_AutoGeneratingColumn(object sender, DataGridAutoGeneratingColumnEventArgs e)
{
if (e.PropertyName.Contains('/') && e.Column is DataGridBoundColumn)
{
var col = e.Column as DataGridBoundColumn;
col.Binding = new Binding(string.Format("[{0}]", e.PropertyName));
}
}