field should not affect loading the appointments in any manner. This is a field that is used internally in some specific cases (for example, to distinguish appointments that have the same start date, end date, summary, etc.). In the general case, you do not need to store this field in your database. In our examples this field is mapped to an integer column, but there is some special code that handles storing the ID of the newly added appointments (which have an automatically generated UniqueId
of type GUID). Please check the Adapter_RowUpdated
handler in the source code of the example.
Yes, making the ID column of your data table accept GUIDs will prevent the exception, but I would rather suggest adding another GUID
column to store the UniqueId
because in some cases having an auto-increment key column is vital for database performance.
If you consider the case is not resolved or if there is still anything that is not clear, and if you think that you can invest some time in creating a sample project, I will be glad to investigate it and suggest what should be modified. So please feel free to contact us if you need further support.
the Telerik team