When building Oracle JET Model/Collection structure to render table, you should be careful defining ID attribute. This attribute must have unique values only, if there will be duplicates in ID, then table rows will be rendered incorrectly.
Take as example below structure for Employees REST endpoint. EmployeId attribute provides unique values and it should be defined as ID for JET model:
Let’s try and see what happens when non-unique DepartmentId attribute is set for a key in JET model:
In this case, during data fetch and UI table rendering (specifically when navigating to the next page of the table) – JET runtime for the table will get confused and will fetch all of the records from the backend (definitely, not what we want): Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.
Blog 
Twitter 
LinkedIn ![image[7][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/image7222.png?w=20&h=20 "image[7][2][2][2]"){kind=small}
Facebook 
Meetups
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic
Developer Community 