Hi Devi,
I had the very same issue this week. I used the Chrome debugger tools to break at the point in the jqx-all.js file where the widget is looking for the appointment that is under the mouse cursor. There is a method that is trying to find the attached appointment data using the data-key attribute added to the appointment div by the widget. The value of this key is the value of the dataSource field associated with the id field specified in the appointmentDataFields setting.
In my scenario I was using a unique number for each appointment record for the id however it was not the zero-based index. The widget code is expecting to look up the appointment data using a zero-based index. Changing this resolved the issue.
I hope this helps with your scenario.
Steve
