Impossible to retrieve object primary key of the selected row without defining a useless column for the primary key.
Inconsistent behaviors between igGrid and igHierarchicalGrid
Here are the examples:
igGrid: http://codepen.io/anon/pen/aJILd (error in the console : "Cannot read property 'dataType' of null")
igHierarchicalGrid: http://codepen.io/anon/pen/ytdLB (error in the console : "Cannot read property 'id' of null")
Hello Francesc,
Defining the primary key column is currently a requirement in the KO scenario. You could however hide it by adding the "hidden: true" property to the column definition:
{ headerText: 'Product ID', key: 'ProductID', dataType: 'number', hidden: true }
In this way the grid should look like as though the column has not been defined. If you plan on using the Hiding feature you might need to add a column setting for this column with "allowHiding: false" as to disable users from showing it.
I hope this helps!
Best regards,
Stamen Stoychev
Hello Stamen,
We didn't planned to use the Hiding feature.
But the proposed solution doesn't work. Here is the example: http://codepen.io/anon/pen/LwAik
Francesc Baeta
INNES
I mean that if you click on the TEST button, the grid isn't updated. If you don't hide the ID ccolumn, then it works as expected...
Hello Fracesc,I have created this support ticket for you based on your forum post at: http://es.infragistics.com/community/forums/t/83769.aspxAfter successfully reproducing the issue with the sample provided, I have asked our engineers to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 154930.
As a temporary workaround, it should be possible to avoid this issue by defining the hidden column - ProductID last in this case:
columns: [ { headerText: "Product Name", key: "Name", dataType: "string" }, { headerText: "Product Number", key: "ProductNumber", dataType: "string" } , { headerText: "Product ID", key: "ProductID", dataType: "Number", hidden: true } ],
This should hopefully help in avoiding this mismatching issue.
Please let me know if you need more information.
Please do not hesitate to contact me if you continue to experience any issues with this scenario after applying the latest IgniteUI SR.
Thank you for choosing Infragistics !