We have a grid that is bound to an observable array. When we add a new item through code to the observable array the item is displayed in the grid as expected. The issue we are running into is when we update one of the observable of the newly added item through code that change is not reflected in the newly added grid row.
It seems like the grid is correctly listening to changes to the observable array but is failing to correctly bind it's UI for the new row to the observables of the newly added item.
Please see the attached example.
1) If you click the 'Modify' button the last item in the observable will have it's 'Name' observable modified and the new value is reflected in the grid
2) Refresh page.
When you click the 'Add' button, code will run to insert a new item into an observable array and you can see the new item is reflected in the grid.
If you then click the modify button the name observable of the last item in observablearray is modified, but that value is not reflected in the grid.
Hello Chad,
The fix for this issue has been resolved in IgniteUI 2013 Volume 1 and newer. To take advantage of this fix, please download the latest service release using the instructions found here: http://community.infragistics.com/forums/t/29398.aspx
Please let me know if you have any questions.
Thanks for the update.
To help resolve this issue, I have created case number CAS-124328-N6B1D4 for you. To access the case, simply log into your Infragistics account and click on My Support Activity.
Also, as stated by Martin Pavlov, our engineering staff to examine this further. To ensure that it will receive attention, we have logged this behavior in our internal tracking system with a Development ID of 152021. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
Note, I will post the any solutions for this issue on this forum.
Thanks Martin.
Without yet being linked to the internal item do you have an estimated ETA? We are dependent on this functionality for an upcoming production release. If it hasn't been prioritized into the next release we would need to find a workaround and plan accordingly.
-Chad
We already have this issue logged in our internal bug tracking system with an id 152021. We will create a case for you and link it to the bug, so that you can track its progress in your account in the 'Support Activity' page. You'll be notified by e-mail when the bug is fixed and available for download.
Best regards,Martin PavlovInfragistics, Inc.